[gentoo-user] ABI change in gcc 3.4 -> gcc 4.1 transition

[gentoo-user] ABI change in gcc 3.4 -> gcc 4.1 transition

[Paweł Kamiński]

Hi All,

I'm obliged in my work to use closed source LabView 8.0 commercial
binary package. It's very important for me to know if after upgrade
gcc from my current 3.4.6 version to 4.1.1 LabView will run. There is
ABI change betwen gcc 3.4.6 <-> 4.1.1 versions and it's not clear for
me if gcc upgrade not damage LabView.

Thanks,
Pawel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] ABI change in gcc 3.4 -> gcc 4.1 transition

[Richard Fish]

On 10/21/06, Paweł Kamiński <Pawel.Kaminski@poczta.fm> wrote:
> Hi All,
>
> I'm obliged in my work to use closed source LabView 8.0 commercial
> binary package. It's very important for me to know if after upgrade
> gcc from my current 3.4.6 version to 4.1.1 LabView will run. There is
> ABI change betwen gcc 3.4.6 <-> 4.1.1 versions and it's not clear for
> me if gcc upgrade not damage LabView.

It's possible, run ldd against the  LabView binaries to see what, if
any, version of libstdc++ they link against.  But the worst case is
that you would need to keep 3.4.6 installed and do an LD_LIBRARY_PATH
trick when running LabView to force it to use the old libstdc++.

-Richard

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: ABI change in gcc 3.4 -> gcc 4.1 transition

[Paweł Kamiński]

Richard Fish wrote:

> On 10/21/06, Paweł Kamiński <Pawel.Kaminski@poczta.fm> wrote:
>> Hi All,
>>
>> I'm obliged in my work to use closed source LabView 8.0 commercial
>> binary package. It's very important for me to know if after upgrade
>> gcc from my current 3.4.6 version to 4.1.1 LabView will run. There
is
>> ABI change betwen gcc 3.4.6 <-> 4.1.1 versions and it's not clear
for
>> me if gcc upgrade not damage LabView.
> 
> It's possible, run ldd against the  LabView binaries to see what, if
> any, version of libstdc++ they link against.  But the worst case is
> that you would need to keep 3.4.6 installed and do an
LD_LIBRARY_PATH
> trick when running LabView to force it to use the old libstdc++.
> 
> -Richard
 
Thanks Richard for your fast respond. I send ldd result below:

#ldd /opt/NI/LabVIEW/8.0/usr/local/natinst/LabVIEW-8.0/labview
        linux-gate.so.1 =>  (0xffffe000)
        libOSMesa.so.4 => /opt/Mesa3d/6.4.2/lib/libOSMesa.so.4
(0xb7fc2000)
        libGL.so.1 => /opt/Mesa3d/6.4.2/lib/libGL.so.1 (0xb7d2e000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xb7c28000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xb7c16000)
        libm.so.6 => /lib/libm.so.6 (0xb7bc9000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7bc4000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7bb0000)
        libc.so.6 => /lib/libc.so.6 (0xb7a77000)
        libXau.so.6 => /usr/X11R6/lib/libXau.so.6 (0xb7a74000)
        libXdmcp.so.6 => /usr/X11R6/lib/libXdmcp.so.6 (0xb7a6f000)
        /lib/ld-linux.so.2 (0xb7fcc000)

As I understand from the ldd log above LabView doesn't use libstdc++,
but I'm not sure if ABI change concerns only libstdc++. As somebody
may see, I have to use LD_LIBRARY_PATH trick to solve absence of
libOSMesa.

Regards,
Pawel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: ABI change in gcc 3.4 -> gcc 4.1 transition

[Richard Fish]

On 10/21/06, Paweł Kamiński <Pawel.Kaminski@poczta.fm> wrote:
> As I understand from the ldd log above LabView doesn't use libstdc++,
> but I'm not sure if ABI change concerns only libstdc++.

The C ABI has been stable for years, only the C++ ABI is being broken
with each new gcc release.

http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html

Basically, as long as it isn't linking to anything under
/usr/lib/gcc/..., you should be safe.

-Richard

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Re: ABI change in gcc 3.4 -> gcc 4.1 transition

[Paweł Kamiński]

Richard Fish wrote:

> The C ABI has been stable for years, only the C++ ABI is being
broken
> with each new gcc release.
> 
> http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html
> 
> Basically, as long as it isn't linking to anything under
> /usr/lib/gcc/..., you should be safe.
> 
> -Richard
 
Many thanks Richard. It's now some more clear form me.

Regards,
Pawel

-- 
gentoo-user@gentoo.org mailing list