[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Broken gcc 3.2 in RH8.0 with glibc-2.3.2

On further investigation, it turns out that this problem is specific to C++ programs. When compiling with gcc 3.2, the linker can't find libstdc++, or has unresolved symbols for some other reason, without explicitly referring to -lstdc++ in the link step. When using gcc 2.95.3, the explicit reference to -lstdc++ isn't necessary. I will enter this in Bugzilla.
Is this a bug or a "feature"?
At 12:53 PM 3/28/2003 -0500, Jakub Jelinek wrote:
On Fri, Mar 28, 2003 at 11:28:54AM -0500, John Ketchum wrote:
> I'm having a problem with gcc/glibc comaptibility on systems that I have
> upgraded to RH 8.0
> On systems that had the standard gcc that came with 7.3, when upgraded to
> 8.0, then I installed the new glibc-2.3.2 rpms, no problems building things
> with gcc 3.2.
> On systems on which I have previously installed gcc 2.95.3 from tarball
> sources, in /usr/local/bin, when I upgrade to 8.0 and install the new
> glibc-2.3.2 rpms, gcc 3.2 is broken--there are numerous unresolved
> references in the link step---, but I can still build things with gcc 2.95.3.
> Can anyone help me fix this-- i.e. make gcc 3.2 work?

Please file a bugzilla bug with exact details what are you doing and
what errors do you get.


Psyche-list mailing list
Psyche-list redhat com

John Ketchum Qualcomm Inc. 9 Damonmill Square Suite 2A Concord, MA 01742

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]