Re: libstdc++.so.5
- From: Denis Vlasenko <vda.linux@xxxxxxxxxxxxxx>
- Date: Thu, 31 Aug 2006 18:46:18 +0200
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
-
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/
- References:
- libstdc++.so.5
- From: Majumder, Rajib
- libstdc++.so.5
- Prev by Date: Re: - i386-early-fault-handler.patch removed from -mm tree
- Next by Date: Re: one more ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [Re: 2.6.18-rc4-mm3]
- Previous by thread: Re: libstdc++.so.5
- Next by thread: highmem64g vs. swsusp
- Index(es):
Relevant Pages
|
