[Llvm-bgq-discuss] llvm-bgq

[Hal Finkel]

----- Original Message -----
> From: "Christopher Samuel" <samuel at unimelb.edu.au>
> To: llvm-bgq-discuss at lists.alcf.anl.gov
> Sent: Wednesday, April 2, 2014 10:53:22 PM
> Subject: Re: [Llvm-bgq-discuss] llvm-bgq
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 03/04/14 13:15, Christopher Samuel wrote:
> 
> > Interesting, I'll check out what our on-site IBMers did in those
> > xCAT
> > postscripts.   Certainly the XL and GCC toolchains don't seem to
> > mind.
> > 
> > I wonder if there's a symlink that's missing here?
> 
> Fixed it - strace showed me that the compiler was looking for those
> libraries in /V1R2M0-efix23 which is the symptom of the relative
> symlink.
> 
> A quick grep and sure enough there was a readlink in the bgclang
> script.
> 
> Adding the -f flag to that readlink fixed it, I can now compile with
> only some (apparently innocent) warnings.
> 
> [samuel at avoca Test]$ mpicc -O3 -o hello-bgclang hello.c
> /usr/local/llvm/r203443-20140309/bin/clang: /lib64/libz.so.1: no
> version information available (required by
> /usr/local/llvm/r203443-20140309/bin/../lib/libLLVM-3.5.0svn.so)
> /usr/local/llvm/r203443-20140309/bin/clang: /lib64/libz.so.1: no
> version information available (required by
> /usr/local/llvm/r203443-20140309/bin/../lib/libLLVM-3.5.0svn.so)
> /usr/local/llvm/r203443-20140309/binutils/bin/as: /lib64/libz.so.1:
> no version information available (required by
> /usr/local/llvm/r203443-20140309/binutils/bin/as)
> /usr/local/llvm/r203443-20140309/binutils/bin/ld: /lib64/libz.so.1:
> no version information available (required by
> /usr/local/llvm/r203443-20140309/binutils/bin/ld)
> 
> [samuel at avoca Test]$ bgclang -O3 -o hello-bgclang hello.c
> /usr/local/llvm/r203443-20140309/bin/clang: /lib64/libz.so.1: no
> version information available (required by
> /usr/local/llvm/r203443-20140309/bin/../lib/libLLVM-3.5.0svn.so)
> /usr/local/llvm/r203443-20140309/bin/clang: /lib64/libz.so.1: no
> version information available (required by
> /usr/local/llvm/r203443-20140309/bin/../lib/libLLVM-3.5.0svn.so)
> /usr/local/llvm/r203443-20140309/binutils/bin/as: /lib64/libz.so.1:
> no version information available (required by
> /usr/local/llvm/r203443-20140309/binutils/bin/as)
> /usr/local/llvm/r203443-20140309/binutils/bin/ld: /lib64/libz.so.1:
> no version information available (required by
> /usr/local/llvm/r203443-20140309/binutils/bin/ld)

Yea, those are just because I compiled the binaries on vesta (which is running a more-recent REL version) -- I can send you the libz.so that it really wants to silence the warnings if you'd like. I may start shipping it in the rpms, just because it certainly can get annoying.

 -Hal

> 
> Now for testing!
> 
> All the best,
> Chris
> - --
>  Christopher Samuel        Senior Systems Administrator
>  VLSCI - Victorian Life Sciences Computation Initiative
>  Email: samuel at unimelb.edu.au Phone: +61 (0)3 903 55545
>  http://www.vlsci.org.au/      http://twitter.com/vlsci
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iEYEARECAAYFAlM82zIACgkQO2KABBYQAh+8zwCeJjaXOo7M49mWy0PeVMBTl6PD
> WZUAnibwbdFbQrUhZgqmTr+xn3N7lX86
> =93Zb
> -----END PGP SIGNATURE-----
> _______________________________________________
> llvm-bgq-discuss mailing list
> llvm-bgq-discuss at lists.alcf.anl.gov
> https://lists.alcf.anl.gov/mailman/listinfo/llvm-bgq-discuss
> 

-- 
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory