From owner-freebsd-current Sat Aug 22 20:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12868 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:18:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12859 for ; Sat, 22 Aug 1998 20:18:19 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA00092; Sun, 23 Aug 1998 12:47:35 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA31192; Sun, 23 Aug 1998 12:47:34 +0930 Date: Sun, 23 Aug 1998 12:47:34 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221959.TAA21095@dingo.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Aug 1998, Mike Smith wrote: > > 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? Unfortunately I'm not a very experienced C/C++ coder; I doubt I would have the skills to identify how to fix these problems, but I'll see if I can narrow anything down. I am sure that someone else with more experience would be able to do better, though. lpr (one of the bits which fails due to warnings being treated as errors) is probably an easy target for someone who has a good understanding of C semantics and standards; there's probably some nonconformity in the source which egcs is picking up on. I can however investigate whether I can get a newer gnu groff to compile with egcs. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message