Hi,
Sorry for the late reply. My comments are inlined.
On Wed, 14 Apr 2004 gburton_at_[hidden] wrote:
>
> I've responded to your questions below. All in all this one appears to
> remain something of a mystery.
>
>
> On Tue, 13 Apr 2004, Amey Dharurkar wrote:
>
> >
> > Hi,
> >
> > Need to clarify couple of things --
> >
> > 1. Did you explicitly set the FLIBS?
>
> Yes, the variable FLIBS was set explicitly. The variable was then
> checked to ensure the actual result was the one intended. Thus
> ~/lamtests-7.0.4$ echo $FLIBS
> -L/opt/ibmcmp/xlf/8.1/lib -libxl -libxlfpmt4 -libxlfpmt4_r -libxlfpmt8_r
> -libxlfpmt8 -libxlfopt -libxlf90 -libxlf90_r -libxlfmath -libxlfpad
> -libxlfpad_r
>
> >
> > 2. You have said that you checked the path of libxl. What is the exact
> > name of the library? Is it libxl.a OR libibxl.a OR libxlf.a? If the
> > name is anything other than libibxl.a then it is clear that linker was
> > not able to locate the file.
> >
> Here again, I checked to ensure both the path was correctly specified
> and that the spelling of the library was correct. To the best of my
> ability it appears that the library "libxl.a"
> is correctly spelled and is located in /opt/ibmcmp/xlf/8.1/lib. Yet the
> configure script in the LAM test suite still appears unable to find it.
If the library is "libxl.a" then you will need to say
-L/opt/ibmcmp/xlf/8.1/lib -lxl (NOT -L/opt/ibmcmp/xlf/8.1/lib -libxl)
You might want to correct the FLIBS according to the above notation .
(-lFOO will get translated to libFOO.a)
Hope this helps.
> I could send the config.log in its entirety or anything else that might
> help diagnose the problem, as I am not able to run any of the configure
> tests until the problem is fixed.
>
> Thanks again!
> Greg Burton
>
>
> > Hope this helps,
> > Amey
> >
> > On Mon, 12 Apr 2004 gburton_at_[hidden] wrote:
> >
> > >
> > > I have been unable to configure the LAM test suite, as the configure
> > > script fails because it is unable to link the Fortran libraries from C.
> > > This is despite the fact that I believe I have set the PATH variable to
> > > include both the libraries from the fortran compiler and from the LAM/MPI
> > > build and install. I include below, separated by rows of "xxxxx" some
> > > relevant info concerning my setup. Any help would be greatly
> > > appreciated!!
> > >
> > >
> > > The FLIBS variable is given by
> > >
> > > ~/lamtests-7.0.4$ echo $FLIBS
> > > -L/opt/ibmcmp/xlf/8.1/lib -libxl -libxlfpmt4 -libxlfpmt4_r -libxlfpmt8_r
> > > -libxlfpmt8 -libxlfopt -libxlf90 -libxlf90_r -libxlfmath -libxlfpad
> > > -libxlfpad_r -L/usr/local/lib -llamf77mpi -lmpi -impi -liblam -liblammpi++
> > > -libfortran -libfortranbegin -libgmp -libiberty
> > > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > >
> > > The ./configure output in the LAM test suite is given by:
> > >
> > > ~/lamtests-7.0.4$ ./configure
> > > Configuring LAM test suite version 7.0.4
> > > checking for a BSD-compatible install... /usr/bin/install -c
> > > checking whether build environment is sane... yes
> > > checking for gawk... no
> > > checking for mawk... no
> > > checking for nawk... no
> > > checking for awk... awk
> > > checking whether make sets $(MAKE)... yes
> > > checking build system type... powerpc-apple-darwin7.3.0
> > > checking host system type... powerpc-apple-darwin7.3.0
> > > checking for mpicc... yes
> > > checking for gcc... mpicc
> > > checking for C compiler default output file name... a.out
> > > checking whether the C compiler works... yes
> > > checking whether we are cross compiling... no
> > > checking for suffix of executables...
> > > checking for suffix of object files... o
> > > checking whether we are using the GNU C compiler... yes
> > > checking whether mpicc accepts -g... yes
> > > checking for mpicc option to accept ANSI C... none needed
> > > checking for style of include used by make... GNU
> > > checking dependency style of mpicc... gcc3
> > > checking for mpic++... yes
> > > checking whether we are using the GNU C++ compiler... yes
> > > checking whether mpic++ accepts -g... yes
> > > checking dependency style of mpic++... gcc3
> > > checking for mpif77... yes
> > > checking whether we are using the GNU Fortran 77 compiler... no
> > > checking whether mpif77 accepts -g... yes
> > > checking for ranlib... ranlib
> > > checking for mpi.h... yes
> > > checking for MPI_Initialized in -lmpi... yes
> > > checking if have Fortran MPI bindings... yes
> > > checking how to get verbose linking output from mpif77... -v
> > > checking for Fortran libraries of mpif77... -L/opt/ibmcmp/xlf/8.1/lib
> > > -libxl -libxlfpmt4 -libxlfpmt4_r -libxlfpmt8_r -libxlfpmt8
> > > -libxlfopt -libxlf90 -libxlf90_r -libxlfmath -libxlfpad -libxlfpad_r
> > > -L/usr/local/lib -llamf77mpi
> > > -lmpi -impi -liblam -liblammpi++ -libfortran -libfortranbegin -libgmp
> > > -libiberty
> > > checking for dummy main to link with Fortran libraries... unknown
> > > configure: error: linking to Fortran libraries from C fails
> > > See `config.log' for more details.
> > >
> > > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > The 'config.log' gives the relevant output that:
> > >
> > > configure:4587: mpicc -o conftest conftest.c -L/opt/ibmcmp/xlf/8.1/lib
> > > -libxl -libxlfpmt4 -libxlfpmt4_r -libxlfpmt8_r -libxlfpmt8
> > > -libxlfopt -libxlf90 -libxlf90_r -libxlfmath -libxlfpad -libxlfpad_r
> > > -L/usr/local/lib -llamf77mpi
> > > -lmpi -impi -liblam -liblammpi++ -libfortran -libfortranbegin -libgmp
> > > -libiberty >&5
> > > ld: can't locate file for: -libxl
> > > mpicc: No such file or directory
> > > configure:4593: $? = 1
> > > configure: failed program was:
> > > | /* confdefs.h. */
> > > |
> > > | #define PACKAGE_NAME ""
> > > | #define PACKAGE_TARNAME ""
> > > | #define PACKAGE_VERSION ""
> > > | #define PACKAGE_STRING ""
> > > | #define PACKAGE_BUGREPORT ""
> > > | #define LAMTEST_MAJOR_VERSION 7
> > > | #define LAMTEST_MINOR_VERSION 0
> > > | #define LAMTEST_RELEASE_VERSION 4
> > > | #define LAMTEST_ALPHA_VERSION 0
> > > | #define LAMTEST_BETA_VERSION 0
> > > | #define LAMTEST_CVS_VERSION 0
> > > | #define LAMTEST_VERSION "7.0.4"
> > > | #define LAMTEST_ARCH "powerpc-apple-darwin7.3.0"
> > > | #ifdef __cplusplus
> > > | extern "C" void std::exit (int) throw (); using std::exit;
> > > | #endif
> > > | /* end confdefs.h. */
> > > | #define F77_DUMMY_MAIN _main
> > > | #ifdef F77_DUMMY_MAIN
> > > |
> > > | # ifdef __cplusplus
> > > | extern "C"
> > > | # endif
> > > | int F77_DUMMY_MAIN() { return 1; }
> > > |
> > > | #endif
> > > | int
> > > | main ()
> > > | {
> > > |
> > > | ;
> > > | return 0;
> > > | }
> > > configure:4627: result: unknown
> > > configure:4647: error: linking to Fortran libraries from C fails
> > > See `config.log' for more details.
> > >
> > >
> > > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > This suggests that the directory containing -libxl is incorrectly
> > > specified, but I have checked the actual path and it appears to be ok. I
> > > also looked at the command "mpicc: No such file or directory", but found
> > > that it too seemed properly given
> > >
> > > %which mpicc
> > > /usr/local/bin/mpicc
> > >
> > > Any help running the ./configure script in the LAM test suite would be
> > > greatly appreciated!!
> > >
> > > Greg Burton
> > >
> > >
> > > ---------------------------------
> > >
> > >
> > > _______________________________________________
> > > This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> > >
> >
> >
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
