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

Markus Elfring Markus.Elfring at web.de
Tue Apr 28 20:40:39 CEST 2009


> 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


> Can you actually compile and link any C++ program with that compiler?
> A test with an "hello world" program should suffice.

Yes - The following example works as expected.

#include <iostream>
int main(void) { std::cout << "Test" << std::endl; return 0; }

elfring at Sonne:~/Projekte/GNU/GCC> /usr/local/bin/g++ Test.cpp && ./a.out
Test

The compiler software passed the usual test cases (make check) on my
system, too.

Regards,
Markus



More information about the PPL-devel mailing list