libstdc++.so.5

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
==============================================================================

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: libstdc++.so.5
    ... While porting an C++ application from RHEL to SLES we faced some issue ... I suggest building and installing gcc from source ...
    (Linux-Kernel)
  • Re: [PATCH] video: limit stack usage of ir-kbd-i2c.c
    ... However there is a risk that gcc will inline these functions (that's ... Not sure how to prevent gcc from inlining. ... I didn't know about noinline, ...
    (Linux-Kernel)
  • Re: libstdc++.so.5
    ... Is there any risk associated with this? ... this is clearly not a kernel question so you're asking on the wrong ... A RHEL or SLES user list ...
    (Linux-Kernel)