Thanks Jeff.
Im not too familiar with UNIX yet, but getting there.
Hopefuly step 2 solves the problem, is adding -lSystemStubs to my libraries easy to do in a bash shell?
I tried editing .bashrc and adding LDFLAGS = -lSystemStubs
Ben
----- Original Message -----
From: Jeff Squyres <jsquyres_at_[hidden]>
Date: Friday, May 20, 2005 5:31 pm
Subject: Re: LAM: compile error during lam install
> Here's the problem:
>
> -----
> configure:9666: gfortran -O conftestf.f conftest.o -o conftest
> /usr/bin/ld: Undefined symbols:
> _fprintf$LDBLStub
> collect2: ld returned 1 exit status
> -----
>
> We've had this report from other Tiger users as well (just
> yesterday,
> as a matter of fact) -- it seems that gfortran 4.0 neglects to add
> a
> library in the linking process for some functions (like fprintf).
> This
> is from the test in LAM where we're trying to get the size or
> alignment
> of a fortran type -- we have a simple Fortran program as the
> main(),
> and it calls a C function to determine the size of a datatype and
> then
> write its value out into a file where configure can get the
> result. We
> actually use an almost identical test in Open MPI.
>
> Users with gcc 4.1 did not seem to have this problem.
>
> I unfortunately do not have a Tiger / gcc 4.0 machine at my
> disposal to
> test with. :-\
>
> There's a few options here:
>
> 1. re-write the test to not use fprintf. I'm not inclined to do
> this,
> because this test has worked for years and years with many
> compilers on
> many platforms; this is definitely a bug.
> 2. add "-lSystemStubs" to your LIBS before running configure (this
> is
> the missing library)
> 3. configure gfortran to automatically add this library (some
> people
> have had success with this -- I don't know the details of how to
> do
> this)
>
>
> On May 20, 2005, at 3:09 PM, Ben Heaps wrote:
>
> > config.log is attached
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
