From owner-freebsd-current Sat Aug 22 20:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10264 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:01:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d6.dialup.hilink.com.au [203.2.144.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10213 for ; Sat, 22 Aug 1998 20:01:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA21095; Sat, 22 Aug 1998 19:59:23 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808221959.TAA21095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-reply-to: Your message of "Sun, 23 Aug 1998 12:16:38 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Aug 1998 19:59:21 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Aug 1998, Mike Smith wrote: > > > > I'm using egcs from their anon cvs > > > repository, and after building ELF libs and X (and all other X related > > > goodies), egcs works wonderfully. I don't have any major cli C++ > > > programs, so I didn't bother with building an ELF world. gdb seems to be > > > the only stumbling block for me. > > > > Try building the rest of the world, and run with it for a few weeks. > > For what it's worth, I've been using egcs (-O2 -mpentium -march=pentium) > to compile my kernel and all the compilable parts of the world for some > time now (there are about 10 things which egcs can't compile at present). > I haven't experienced any problems whatsoever with things misbehaving or > crashing randomly; in fact at the moment my system is about the most > stable it's been all year. This is a useful datapoint, thanks. > For the record, most of the C++ stuff in the source tree is not compilable > with egcs..from memory the other parts which I have to compile with gcc > are due to extra compiler warnings which cause compilation to fail (i.e. > warnings treated as errors), the lkms (egcs doesnt have -aout) and the > biosboot stuff (exceeds maximum length). All of these are interesting. - Why won't it compile the C++ code (ie. groff)? is there a newer groff that does build? - Can you submit fixes to these build killers as PRs? - Which parts of the biosboot code grow with egcs? By how much? Thanks for your input; this sort of monitoring and evaluation is where the real answers come from. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message