linux-kernel - Re: libstdc++.so.5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1157038626.2715.129.camel@laptopd505.fenrus.org>
Date:	Thu, 31 Aug 2006 17:37:06 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Majumder, Rajib" <rajib.majumder@...dit-suisse.com>
Cc:	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: Re: libstdc++.so.5

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/