From owner-freebsd-chat Mon Nov 20 11:41:06 1995 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA00785 for chat-outgoing; Mon, 20 Nov 1995 11:41:06 -0800 Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA00780 for ; Mon, 20 Nov 1995 11:41:01 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA22329; Mon, 20 Nov 1995 12:43:09 -0700 Date: Mon, 20 Nov 1995 12:43:09 -0700 From: Nate Williams Message-Id: <199511201943.MAA22329@rocky.sri.MT.net> To: Ollivier Robert Cc: nate@rocky.sri.MT.net (Nate Williams), chuckr@glue.umd.edu, FreeBSD-chat@FreeBSD.org Subject: Re: Gcc-2.7.1 In-Reply-To: <199511201813.TAA01580@keltia.freenix.fr> References: <199511191621.JAA16061@rocky.sri.MT.net> <199511201813.TAA01580@keltia.freenix.fr> Sender: owner-chat@FreeBSD.org Precedence: bulk > > Nope. Groff is broken with regards to newer c++ releases because it > > relies on an older revision of the standard. You can compile groff by > > telling it to use the older standard with a flag. > > Except that when I compiled groff with the flag, it started to core dump > (Sun Sparc under SunOS 4.1.4)... Anyway, I've reverted to 2.6.3 for the > moment. I saw that as well, but the fix for that was something trivial. It was so long ago I don't remember anymore, but it wasn't too hard to find. (I was using SunOS 4.1.3_U1 if it makes any difference) Nate