stdtm@uokmax.ecn.uoknor.edu (Timothy A. Melten) (07/03/90)
Has anyone compiled g++1.37.1 successfully for an i386 machine? I am trying to get groff 0.3 to compile, but I have an old (1.36.1) version of g++. When I tried to build g++ 1.37.1 it died while trying to make ld.c. If anyone has gotten it to work, please drop me a line. If this has been hashed through before, I apologize; I don't usually read this newsgroup. Thanks in advance, Tim -- ////////////////////////////////////////////////////////////////////////////// Timothy A Melton University of Oklahoma Graduate Student Deptartment of Chemical Engineering
brown@vidiot.UUCP (Vidiot) (07/04/90)
In article <1990Jul3.004744.11110@uokmax.uucp> stdtm@uokmax.ecn.uoknor.edu (Timothy A. Melten) writes:
<Has anyone compiled g++1.37.1 successfully for an i386 machine? I am
<trying to get groff 0.3 to compile, but I have an old (1.36.1) version of
<g++. When I tried to build g++ 1.37.1 it died while trying to make ld.c.
<If anyone has gotten it to work, please drop me a line. If this has been
<hashed through before, I apologize; I don't usually read this newsgroup.
Welcome the the GNU g++ installation fustration club. I too want to get
groff running, but can't because of the same ld.c problems. I had others
as well, that wasted about 6 hours of time. I have written to the author
and am awaiting an answer.
I'll make a public suggestion here, like the one that I did to the author.
I would make installation much easier if the GNU team would use the configure
program package, like rn and elm. This program is used to look around the
system to see what is, or isn't, there and set up the required stuff
automatically. We all don't know the internals of the various systems that
we have. Having a program look around for this stuff will be a big plus.
I believe that the GNU team should very seriously consider this installation
aid.
--
harvard\ att!nicmad\ spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot ucbvax!uwvax..........!astroatc!vidiot!brown
rutgers/ decvax!nicmad/ INET:<@spool.cs.wisc.edu,@astroatc:brown@vidiot>pcg@cs.aber.ac.uk (Piercarlo Grandi) (07/05/90)
In article <578@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes:
Welcome the the GNU g++ installation fustration club.
It has never taken me more than a couple of hours to get G++ running;
all I have done has been to compile it with 'cc -O -W2,-y0', link it
with the '-lPW' switch, and use COFF support. I have also found the
time to slightly improve (some releases back) support for shared
libraries, linking with holes, etc... Very few problems even there. My
next project, when I reinstall it (I am waiting 2.0), is to get rid of
the collect pass and put in the COFF .init .fini section support as
already done by others (Grunwald?). Even there I expect very little
sweat.
What's all this fuss about G++ and SysV386, I always ask myself.
I too want to get groff running, but can't because of the same ld.c
problems. I had others as well, that wasted about 6 hours of time.
I have written to the author and am awaiting an answer.
Only because you probably insist on using the dreaded COFF
encapsulation mode. Now that somebody has posted (THANKS!) it, and you
have COFF compatible gas and COFF stabs for gdb (on sequent.kent.edu,
in directory pub/unix386, there is no reason not to use COFF and the
AT&T ld and shared libraries.
I would make installation much easier if the GNU team would use the
configure program package, like rn and elm. [ ... ] I believe that
the GNU team should very seriously consider this installation aid.
They will not, because the GNU team is seriously interested in getting
the GNU OS off the ground, not supporting other OSes. The rely on the
public to care for this, as noted above.
I want however to repeat my plea for the GNU authors to use GNU RCS to
maintain versions, to always release software with a X.Y release number
(and not longer), and to have all GNU RCS headers contain that number,
so that:
* people doing independent modifications can checkin sources at the
X.Y level and put their own mods on branches
* authors can release diff upgrades simply by running rcsdiff -c
* modifications done on the branches can be incorporate din the
mainstream or in later releases of the mainstream by use of patch and
checkin or with rcsmerge.
--
Piercarlo "Peter" Grandi | ARPA: pcg%cs.aber.ac.uk@nsfnet-relay.ac.uk
Dept of CS, UCW Aberystwyth | UUCP: ...!mcsun!ukc!aber-cs!pcg
Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@cs.aber.ac.ukbrown@vidiot.UUCP (Vidiot) (07/07/90)
In article <PCG.90Jul5162042@odin.cs.aber.ac.uk> pcg@cs.aber.ac.uk (Piercarlo Grandi) writes: <In article <578@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes: < < Welcome the the GNU g++ installation fustration club. < <It has never taken me more than a couple of hours to get G++ running; <all I have done has been to compile it with 'cc -O -W2,-y0', link it <with the '-lPW' switch, and use COFF support. I have also found the <time to slightly improve (some releases back) support for shared <libraries, linking with holes, etc... Very few problems even there. My <next project, when I reinstall it (I am waiting 2.0), is to get rid of <the collect pass and put in the COFF .init .fini section support as <already done by others (Grunwald?). Even there I expect very little <sweat. < <What's all this fuss about G++ and SysV386, I always ask myself. So, what OS and machine are you using? < I too want to get groff running, but can't because of the same ld.c < problems. I had others as well, that wasted about 6 hours of time. < I have written to the author and am awaiting an answer. < < I would make installation much easier if the GNU team would use the < configure program package, like rn and elm. [ ... ] I believe that < the GNU team should very seriously consider this installation aid. < <They will not, because the GNU team is seriously interested in getting <the GNU OS off the ground, not supporting other OSes. The rely on the <public to care for this, as noted above. If GNU OS for the 386 is like the GNU compiler stuff, I won't touch it with a ten-foot-pole. BTW, the configure is not OS, related, but obviously it looks around the see what OS stuff is there. I am very gun-shy at the moment. -- harvard\ att!nicmad\ spool.cs.wisc.edu!astroatc!vidiot!brown Vidiot ucbvax!uwvax..........!astroatc!vidiot!brown rutgers/ decvax!nicmad/ INET:<@spool.cs.wisc.edu,@astroatc:brown@vidiot>