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

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

 



Not using g++ driver-- just gcc.
I guess you're saying its not a bug, its a feature.
At 02:16 PM 3/28/2003 -0500, Jakub Jelinek wrote:
On Fri, Mar 28, 2003 at 02:08:39PM -0500, John Ketchum wrote:
> 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.


Are you linking using g++ driver (and not using gcc, or even worse ld alone)?
(only g++ adds -lstdc++ automatically).

Jakub



--
Psyche-list mailing list
Psyche-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/psyche-list

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



--
Psyche-list mailing list
Psyche-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux