🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: gnu.g++.lib.bug
1 messages
1 total messages Started by howell/G=simon/S=guest/O=DEVELOP... Tue, 26 Jan 1993 02:01
libg++-2.2 problem (maybe bug?)
#456
Author: howell/G=simon/S=guest/O=DEVELOP...
Date: Tue, 26 Jan 1993 02:01
37 lines
1708 bytes
Hi,

I'm trying to build libg++-2.2 using gcc-2.2.2.

My machine is a Unisys/6035 running Unix SVR4.  I used configure i386-sysv4.

Everything proceeds fine until the make gets to libg++/src, and tries
to build AllocRing.cc.  At this stage, I get a this fatal error:

----------------------------------------------------------------------------
gcc -g -nostdinc++ -I.. -I. -I./../iostream -I./../g++-include  -c AllocRing.cc
(EOF):undefined name: .L_B5_e
(EOF):undefined name: .L_B5
*** Error code 1 (bu21)

make: fatal error.
*** Error code 1 (bu21)
----------------------------------------------------------------------------

Now, I'm not familiar with C++, but this rather looks like gcc is
having some problems compiling a C++ construct, which it handles using
some auto-generated name like L_B5_e or some such.

But the net result is that I can't build libg++-2.2.   I have no other
version of the library;  I need it so I can build groff-1.05.
Otherwise, I'm stuck.

So, is this a bug in libg++ or gcc, or what can I do about it?

If there's anything else you need to know about my environment, I'll
supply it on request.


Cheers,
Simon Guest.

PS: If I should have RTFM'd (which I tried), please tell me which M to R.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads