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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200608311846.18332.vda.linux@googlemail.com>
Date:	Thu, 31 Aug 2006 18:46:18 +0200
From:	Denis Vlasenko <vda.linux@...glemail.com>
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 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/