🚀 go-pugleaf

In article <1992Aug31.192328.19979@cc.umontreal.ca> duperval@ERE.UMontreal.CA (Duperval Laurent) writes:
>Hi,
>
>I'm trying to compile libg++ on an Iris4d but I have a few problems.  I've
>appended the messages I get during compilation if it may help anyone to see
>what the problem is.
>
>Let me first say that gcc, g++, etc are not installed in /usr/local.  I'm
>trying to make sure everything works properly before I let unsuspecting users
>bombard me with 'It don't work' messages.
OK, but you need to be able to use gcc.  See below...

> As you can see, 'cc' is used to
>compile everything.  I thought gcc or g++ was to be used (Is that what the
>rootme macro is used for?).  Compilation coughs severely as you can see.
Correct; the configure is wrong, at least for sgi.
I think it's also wrong for 386 sysv - I tried it here and had to make
the same fixes; the non-ansi include files (for sysv3) are easier with
fixincludes.

>Is there a way to tell configure where to find gcc?  As in 
>rootme=`dirname `which gcc`` (I know it's illegal but...)
>or something similar?
I just editted the makefiles after configure.
You MUST have run fixincludes and the fixed includes must be in the
include search path (defaults to /usr/local/lib/..../include)
There are a few edits needed to the include files in libg++ package
to make compilation work; they are pretty self-evident from the error
messages you get (you didn't get nearly that far...).
If you compiled gcc assuming standard placement of these things and
they aren't there, you need to do a bunch to the makefiles.  Also
fixincludes won't work without modification in that case.

The error messages come from feeding c++ source xxx.C to cc, which
doesn't recognize the filename extension, so assumes object and passes
the c++ source to the linker (which of course barfs).  libiberty can
use cc but the rest of the source NEEDS gcc.  Better to use gcc for
all.  The fixincludes is more necessary on irix 4.0.x than 3.x but
is needed on either as far as I have seen.

>Or am I seeing everything all wrong?
No.  There is an error in configure for the libg++ (at least 2.1, which
is the latest I've tried.)

>duperval@ere.umontreal.ca
>duperval@jsp.umontreal.ca

-- Pete (Pete@puffin.uucp)