[PPL-devel] Check dependency resolution for 64 bit linking

Roberto Bagnara bagnara at cs.unipr.it
Wed Apr 29 14:15:40 CEST 2009


Markus Elfring wrote:
>> The path usr/local/lib/../lib/libstdc++.so makes me think that
>> you (or someone else) installed GCC from sources.
> 
> Yes, you are right. I built the release 4.3.3 also myself.
> 
> 
>> Please check using file(1).
> 
> elfring at Sonne:~> for X in lib lib64 local/lib local/lib64; do file
> /usr/$X/libstdc++.so.6.0.10; done
> /usr/lib/libstdc++.so.6.0.10: ELF 32-bit LSB shared object, Intel 80386,
> version 1 (SYSV), dynamically linked, stripped
> /usr/lib64/libstdc++.so.6.0.10: ELF 64-bit LSB shared object, x86-64,
> version 1 (SYSV), dynamically linked, stripped
> /usr/local/lib/libstdc++.so.6.0.10: ELF 32-bit LSB shared object, Intel
> 80386, version 1 (SYSV), dynamically linked, not stripped
> /usr/local/lib64/libstdc++.so.6.0.10: ELF 64-bit LSB shared object,
> x86-64, version 1 (SYSV), dynamically linked, not stripped

My guess is that you are compiling the PPL for x86-64 and, for
some reason, /usr/local/lib/libstdc++.so.6.0.10, which is an
80386 object, is in the way.  I do not know why this happens:
the answer is probably contained in config.log.

-- 
Prof. Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy
http://www.cs.unipr.it/~bagnara/
mailto:bagnara at cs.unipr.it



More information about the PPL-devel mailing list