#11187: Problem running gcc4 app in a gcc2 hybrid. -------------------------+---------------------------- Reporter: modeenf | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -------------------------+---------------------------- Comment (by modeenf): From a mail from Ingo Please verify * that libstdc++.so.6 is in /system/lib/x86 (and isn't just a dead symlink), * that /system/lib (or /boot/system/lib) is in LIBRARY_PATH, * that the application you are launching is indeed marked with gcc 2 ABI. The latter can be done with objdump. Enter objdump -D /path/to/app (pipe to less or a file, if you like) and find the definition of symbol _gSharedObjectHaikuABI (there's probably only one occurrence anyway). It should look like: 00068028 <_gSharedObjectHaikuABI>: 68028: 00 00 add %al,(%eax) 6802a: 04 00 add $0x0,%al The addresses (first column) may differ. The disassembly in the right column is irrelevant (it's a data symbol, not code). The hex dump in the middle column is the interesting info. "00 00 04 00" means it's gcc 4 ABI, "02 00 02 00" would be gcc 2. It's 04 00 so that looks ok. If the symbol value is correct, the runtime loader should be able to correctly identify the executable's ABI. If LIBRARY_PATH is correct, it should search the libraries in the correct subdirectories. And if the library is in the correct directory, it should be found. If everything looks good and the application still cannot be started, please run it with "strace -l" and put the output someplace we can look at it. CU, Ingo -- Ticket URL: <https://dev.haiku-os.org/ticket/11187#comment:2> Haiku <https://dev.haiku-os.org> Haiku - the operating system.