Article View: gnu.gcc.help
Article #823Help needed building GCC-2.3.3 on ISC 3.0
From: Shumate Jason
Date: Thu, 07 Jan 1993 15:07
Date: Thu, 07 Jan 1993 15:07
39 lines
2954 bytes
2954 bytes
We have the Interactive UNIX Workstation Developer Kit 3.0 (we're waiting
for the software to come in to update to 3.0.1) and want to build GCC for it.
I have several questions and if some kind person who has built GCC under ISC
could help me, I would be VERY grateful. I should add that we are running
ISC on a 486 box.
1) Is it necessary to build GAS? I got it built, but it barfed on one
of the files in GCC-2.3.3, so I rebuilt GCC with the native AT&T assembler.
Are there any special defines you need to build GAS that maybe I overlooked?
I used the following in CFLAGS : -g -I. -DUSG -DNO_VARARGS -DNON_BROKEN_WORDS
and I linked in the malloc and PW libraries as the Makefile seemed to
indicate I should.
2) When I built GCC, I did not use ld.c from binutils or collect. It
apparently can use the native linker under SysVR3. Is this OK?
3) The instructions for building GCC in the file INSTALL indicate in
step 6 that you need to convert libgcc.a to a GNU-format library before
going on to stage2. I got binutils-1.9 and tried this and had all kinds
of problems. Leaving libgcc.a alone did enable me to finish building GCC.
I can't find anything to indicate if Interactive uses COFF or not, so can
someone please tell me if I need to convert libgcc.a or not? If you have
to build the programs in binutils-1.9, which defines do you need? I used
-DUSG -DCOFF_ENCAPSULATE -DPORTAR -DNON_NATIVE -DSYS_SIGLIST_MISSING -Di386.
I also used the AT&T library libPW.a for alloca - was this wise or should I
have used the GNU version?
4) Are there any special defines you need when building GCC for ISC 3.0
that aren't automagically setup up by configure?
5) My attempt at building libg++-2.3 failed, perhaps because GCC wasn't
built properly in the first place. Is there anything I need to watch out
for in building this?
6) I got 4 warnings when enquire ran, all related to the precision of
a double. Is this normal under ISC? I don't know how accurate Intel's
chip is, so I wondered if this might be normal.
Again, any assistance I can be given would be greatly appreciated. If
you post, please direct follow-ups to gnu.gcc.help.
--
CUL8R, Jason Shumate | "He says there aren't any easy
Ex-Sys. Admin. on another machine, | answers. I say, he's not looking
just another punk user on this one | hard enough!" Bart Simpson, when
jshumate@wrdis01.robins.af.mil | running for class president
Technical Details
Message-ID:
<2938@wrdis01.af.mil>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!howland.reston.ans.net!wupost!spool.mu.edu!sgiblab!news.cs.indiana.edu!wrdis01!jshumateShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!howland.reston.ans.net!wupost!spool.mu.edu!sgiblab!news.cs.indiana.edu!wrdis01!jshumate From: jshumate@wrdis01.af.mil ( Shumate Jason) Newsgroups: gnu.gcc.help,gnu.g++.help Subject: Help needed building GCC-2.3.3 on ISC 3.0 Keywords: ISC,Interactive Message-ID: <2938@wrdis01.af.mil> Date: 7 Jan 93 15:07:34 GMT Followup-To: gnu.gcc.help Organization: 1926CCSG Robins AFB Lines: 39