Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!enuxha!martin
From: martin@enuxha.eas.asu.edu (Ross D. Martin)
Newsgroups: comp.lang.c++
Subject: Re: Problems with g++ on a Sun 4 running SunOs4.1
Summary: ld.c in g++ distribution is bad!
Message-ID: <1516@enuxha.eas.asu.edu>
Date: 4 Oct 90 23:25:51 GMT
References: <6536@castle.ed.ac.uk> <9010021234.AA04968@zardoz.noname>
Organization: Arizona State Univ, Tempe
Lines: 30

In article <9010021234.AA04968@zardoz.noname>, don@zardoz.coral.com (Don Dewar) writes:
> 
>)From: uunet!mcsun!ukc!edcastle!mfg  (M Gordon)
>)Organization: Edinburgh University Electrical Engineering
>) 
>)I recently posted a message about my problems with g++. Further efforts have
>)revealed that the problem is almost certainly with gcc-ld. With this program 
>)in
>)place programs compiled with gcc give the same results as those compiled with
>)g++, i.e. segmentation fault and core dump in start().
>) 
>) Michael Gordon - mfg@castle.ed.ac.uk OR ee.ed.ac.uk	| |_| |_| |__| |_| |   
> 
> like yours, my
> gcc-ld built on a sparcstation running 4.1 also bombed as soon as I
> attempt to execute the program.  Anyway, I put the program in the
> debugger, and it never gets out of the starting gate.

I also could not get ld in the g++ distribution (1.37.0 or 1.37.1)
to work.  I eventually gave up, and went looking for a different
ld.c file, assuming someone else had already fixed the problem.
I found a file ld.c.Z on labrea.stanford.edu, and when I replaced
ld.c in the g++ distribution with this file, I got a gcc-ld that
seems to run fine with both gcc and g++.  I don't know what the
problem was, but you could certainly narrow it down by looking at
the difference of these two ld.c files...

BTW, my problems come from a Sun 3 running SunOS 4.1.

Ross Martin  martin@enuxha.eas.asu.edu