Re: Fortran libraries on the Blue Gene with mpi

[John R. Cary]

Ralf Wildenhues wrote:
> > login5.intrepid$ ./config.guess
> > ./config.guess: unable to guess system type
> >     
> [...]
>   
> > config.guess timestamp = 2009-02-03
> >
> > uname -m = 4400
> > uname -r = 4.0
> > uname -s = iainfo2
> > uname -v = 3.0
> >     
>
>   
> > /bin/arch              = ppc64
> >     
>
>   
> > UNAME_MACHINE = 4400
> > UNAME_RELEASE = 4.0
> > UNAME_SYSTEM  = iainfo2
> > UNAME_VERSION = 3.0
> >     
>
> This looks pretty weird, as if the system hasn't fully been set up yet.
> Where does that "iainfo2" name come from?
>   

I now see that after I downloaded config-master.tar.gz and untarred,
there was a 'uname' executable in the directory, so that was executed.

I moved that aside, and now I get

login1.intrepid$ uname -m; uname -r; uname -s; uname -v
ppc64
2.6.16.46-0.12-ppc64
Linux
#1 SMP Thu May 17 14:00:09 UTC 2007

and

login1.intrepid$ ./config.guess
powerpc64-unknown-linux-gnu


>   
> Thanks for the experiments.  Results:
> - xlc links shared even without -qnostaticlink,
> - bgxlc requires -qnostaticlink in order to link shared.
> - both understand -R and -Wl,-rpath which is good.
>
> Now can you try, for both xlc and bgxlc, whether a static library will
> be accepted even with -qnostaticlink?  I.e., whether -qnostaticlink only
> is "prefer shared libraries over static ones" or "require shared
> libraries, reject static ones"?
>
> bgxlc -c foo.c
> ar cru libfoo.a foo.o
> bgxlc -c main.c
> bgxlc -o main main.o -qnostaticlink -L. -lfoo
> ./main
> bgxlc -o main main.o -L. -lfoo
> ./main
>   


Looks like it is "prefer"

login1.intrepid$ bgxlc -c foo.c
login1.intrepid$ ar cru libfoo.a foo.o
login1.intrepid$ bgxlc -c main.c
login1.intrepid$ bgxlc -o main main.o -qnostaticlink -L. -lfoo
login1.intrepid$ ./main
login1.intrepid$ bgxlc -o main main.o -L. -lfoo
login1.intrepid$ ./main
login1.intrepid$

John