Markus Elfring wrote:
- otherwise, download an official ppl-0.10.2 tarball and try with
that one.
I get the same unexpected error message.
... mv -f .deps/ppl-config.Tpo .deps/ppl-config.Po /usr/local/lib/../lib/libstdc++.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[3]: *** [libppl.la] Fehler 1 make[3]: Leaving directory `/home/elfring/Projekte/PPL/0.10.2/src' ...
Hi Markus,
I believe there is something wrong with your installation of GCC. The path usr/local/lib/../lib/libstdc++.so makes me think that you (or someone else) installed GCC from sources. What you observe could be explained if you are compiling for Intel 80386 and /usr/local/lib/../lib/libstdc++.so is (a symbolic link to) an x86-64 library or the other way around. Please check using file(1). Here is, e.g., what happens on my system:
$ cd /usr/lib $ file libstdc++.so.6.0.10 libstdc++.so.6.0.10: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped $ cd ../lib64 $ file libstdc++.so.6.0.10 libstdc++.so.6.0.10: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
Can you actually compile and link any C++ program with that compiler? A test with an "hello world" program should suffice.
Will any fine-tuning be needed in the configuration script? http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=blob;f=configure.ac;h=...
Not that I know. All the best,
Roberto