libstdc++.so.5

libstdc++.so.5

[Majumder, Rajib]

Hi,

I have 2 Linux boxes. 1 running RHEL 3,  2.4.21 kernel. Other SLSE 9, 2.6.5 kernel. 

While porting an C++ application from RHEL to SLES we faced some issue and it was resolved when we imported libstdc++.so.5 from RHEL and forced the app to reference this on SLES, rather than glibc (which was different ) in /usr/lib. We only ported 1 library.

In RHEL, gcc was 3.2.3, in SLES it was 3.3.2. 

Is there any risk associated with this?  

Any input is appreciated. 

Thanks

Rajib



==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

Re: libstdc++.so.5

[Arjan van de Ven]

On Thu, 2006-08-31 at 23:09 +0800, Majumder, Rajib wrote:
> Hi,
> 
> I have 2 Linux boxes. 1 running RHEL 3,  2.4.21 kernel. Other SLSE 9, 2.6.5 kernel. 
> 
> While porting an C++ application from RHEL to SLES we faced some issue and it was resolved when we imported libstdc++.so.5 from RHEL and forced the app to reference this on SLES, rather than glibc (which was different ) in /usr/lib. We only ported 1 library.
> 
> In RHEL, gcc was 3.2.3, in SLES it was 3.3.2. 
> 
> Is there any risk associated with this?  

Hi,

this is clearly not a kernel question so you're asking on the wrong
list. A RHEL or SLES user list (as they are hosted by Novell / Red Hat)
would be a more appropriate venue, one also where it's more likely to
get a good answer..

Greetings,
   Arjan van de Ven

Re: libstdc++.so.5

[Denis Vlasenko]

On Thursday 31 August 2006 17:09, Majumder, Rajib wrote:
> I have 2 Linux boxes. 1 running RHEL 3,  2.4.21 kernel. Other SLSE 9, 2.6.5 kernel. 
> 
> While porting an C++ application from RHEL to SLES we faced some issue

Wrong maininlg list, but anyway

> and it was resolved when we imported libstdc++.so.5 from RHEL
> and forced the app to reference this on SLES,
> rather than glibc (which was different ) in /usr/lib. We only ported 1 library.

libstdc++ is coming from gcc.

I suggest building and installing gcc from source
on the system where you need libstdc++.
I think latest 3.x.x gcc would be ok.

> In RHEL, gcc was 3.2.3, in SLES it was 3.3.2. 
> 
> Is there any risk associated with this?  
--
vda