Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!rpi!rpi.edu!tale From: tale@pawl.rpi.edu (David C Lawrence) Newsgroups: gnu.g++.lib.bug Subject: Re: libg++ 1.35.0 prerelease available Message-ID: Date: 10 May 89 07:27:28 GMT References: <8905081600.AA11895@rocky> Sender: usenet@rpi.edu Reply-To: tale@pawl.rpi.edu Distribution: gnu Lines: 61 In-reply-to: dl@ROCKY.OSWEGO.EDU's message of 8 May 89 16:00:08 GMT In article <8905081600.AA11895@rocky> dl@ROCKY.OSWEGO.EDU (Doug Lea) writes: Doug> Please let me know if there are any other problems. Yep. --------problems----------- Script started on Wed May 10 03:11:53 1989 ault has logged on ttyp4. /appl/imagine2/emacs/libg++ imagine:gnu (1) make libg++.a (cd src; make GXX="g++" CC="gcc") g++ -v -g -O -fchar-charconst -I../g++-include -I.. -fstrength-reduce -fsave-memoized -mgnu -c builtin.cc g++ version 1.35.0- /appl/life1/gnu/lib/gcc-cpp -+ -v -I../g++-include -I.. -undef -D__GNU__ -D__GNUG__ -Dmc68000 -Dsun -Dunix -D__mc68000__ -D__sun__ -D__unix__ -D__OPTIMIZE__ -D__HAVE_68881__ -Dmc68020 builtin.cc /tmp/cca09633.cpp GNU CPP version 1.35 /appl/life1/gnu/lib/gcc-cc1plus /tmp/cca09633.cpp -quiet -dumpbase builtin.cc -mgnu -fchar-charconst -fstrength-reduce -fsave-memoized -opt -version -G -o /tmp/cca09633.s c++: Invalid option `gnu' GNU C++ version 1.35.0- (68k, MIT syntax) compiled by GNU C version 1.35. *** Error code 1 make: Fatal error: Command failed for target `builtin.o' Current working directory /appl/imagine2/emacs/libg++/src *** Error code 1 make: Fatal error: Command failed for target `libg++.a' Exit 1 /appl/imagine2/emacs/libg++ imagine:gnu (2) exit script done on Wed May 10 03:12:20 1989 -------problems----------- This could very well be that I do not have a working g++, I really would like to know. After fighting with the highest version (1.34.2) of g++ on prep for hours, I checked the newsgroups and found out that my problem was that I was using GCC 1.35 with 1.34 g++. So I got the g++.xtar.Z and libg++.xtar.Z from Stanford. Things went much smoother (although still quite slow) on the G++ build, but I am confused about some of the different message regarding Suns. My two primary lack-of-understanding items are a) in the Makefile should I add -DNO_GNU_LD? (I know it says "could", but _should_ I?) and b) what do I have to do about crt0+.o? Here is the way it is all mapped out: Sun 3's, OS 4.0.1. GNU sources go into /appl/life1/gnu/{bison,gcc,g++,grep,...}. GNU binaries are in /appl/life1/gnu/bin. All references to install things in /usr/local/lib get changed to put them in /appl/life1/gnu/lib. A recent message to gnu.g++.bug suggests that on Suns you have to change tm.h, but doesn't say how to change it (if indeed I need to). The HINTS file also says something about Mrt0.o and says I should change standard_starfile_prefix ... should I? Or are things right the way they are as long as I have declared all the paths properly in the Makfiles? I don't know why this has been so hard for me. Maybe I'm just tired. Maybe I'm just stupid. I sure would appreciate a better recipe for getting this thing working on our pretty standard architecture/os here though. Dave -- tale@rpitsmts.bitnet, tale%mts@itsgw.rpi.edu, tale@pawl.rpi.edu