Bug 107523

Summary: Trying to build libstdc++ compatibly with rhas 2.1
Product: Red Hat Enterprise Linux 2.1 Reporter: benson margulies <bim2003>
Component: gcc3Assignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12555
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-27 17:29:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description benson margulies 2003-10-19 23:32:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; H010818; .NET 
CLR 1.1.4322)

Description of problem:
Please have a look at the referenced bug db entry for gcc. In it, I supply a 
test case for a problem with C++ exceptions and dlopen.

This problem does NOT occur if I use a Red Hat official compiler RPM. I'm 
submitting this entry in the hopes of learning how RedHat configures gcc 
and/or libstdc++ to achieve compatibility. I have customers who stubbornly 
insist on using things like gcc 3.2 on RHAS 2.1, and I'd like to support them. 



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. See URL
2.
3.
    

Additional info:

Comment 1 Jakub Jelinek 2004-10-27 17:29:29 UTC
Using GCC 3.2 on RHAS 2.1 is a bad idea, you need much more recent
binutils and more recent glibc in order to make things work as they
are supposed to work.
At which point it is better to use RHEL 3 which comes with GCC 3.2.