On 11/02/2015 06:06 AM, Jeff McWilliams wrote:
I'm a developer for Altair, working on a large CAE program that we support on Linux. We've been building our tools with gcc/g++ 4.7.2 provided by the Red Hat Developer Toolset 1.1 for some time now. We build on RHEL 5.10 or 5.11 Recently I began looking on updating our tools to gcc/g++ 4.8.2 via the Red Hat Developer Toolset 2.1 I'm compiling all our our code using the specified compiler, though there are some "third party" .so's that we link haven't changed. Our runtime directory contains 151 .so's and one executable. After building everything, there is ONE .so, and one executable that is being created with OS/ABI set to "GNU/Linux" instead of "SYSV". Because of the "GNU/Linux" tag on these two files, the .so and the executable won't load or run on RHEL 5, including the machine that I'm compiling/linking on. I've tried using readelf to examine all the other .so's, as well as .o's and any .a libs that get linked into these two files. So far as I can tell, they all have "SYSV" as the OS/ABI. I can't find any symbols with "IFUNC" set as the type. The only glibc that we link against is the one that comes on the system and/or whatever was installed as part of Red Hat's Developer Toolset. So far as I can understand from researching online, I shouldn't be getting "GNU/Linux" OS/ABI binaries. I haven't mixed newer glibc runtimes on my Linux box, and I am not using libraries that were built on newer platforms. Can someone provide some additional tips or help about how I can determine WHY the linker is setting the OS/ABI field to "GNU/Linux", and what I can do to fix it?
Jeff, I was asked to pass on to you the following response on behalf of the Red Hat Developer Toolset team. Thanks for using the Red Hat Developer Toolset. As your question relates to a Red Hat product rather than the upstream gcc project, we recommend visiting the Red Hat Customer Portal (<https://access.redhat.com/support/cases/#/case/new>) and opening a new case so our customer support team can help you further, if you still suspect there's a bug. Martin
