Re: libstdc++.so.5
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Date: Thu, 31 Aug 2006 17:37:06 +0200
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
-
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: Unable to halt or reboot due to - unregister_netdevice: waiting for eth0.20 to become free. Usage count = 1
- Next by Date: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
- Previous by thread: libstdc++.so.5
- Next by thread: Re: libstdc++.so.5
- Index(es):
Relevant Pages
|
