linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <F444CAE5E62A714C9F45AA292785BED30EB974E0@esng11p33001.sg.csfb.com>
Date:	Thu, 31 Aug 2006 23:09:26 +0800
From:	"Majumder, Rajib" <rajib.majumder@...dit-suisse.com>
To:	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/