X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Sat, 08 Dec 2001 13:00:33 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
Message-Id:	<5567-Sat08Dec2001130033+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	pavenis AT latnet DOT lv, djgpp-workers AT delorie DOT com
In-reply-to:	<002301c17fc5$47c9fff0$0102a8c0@acceleron> (acottrel@ihug.com.au)
Subject:	Re: groff-1.16 & GCC 3.02 broken, groff 1.17.2 & GCC 3.02 okay
References:	<002301c17fc5$47c9fff0$0102a8c0 AT acceleron>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
> Date: Sat, 8 Dec 2001 19:49:12 +1100
> 
> Today I updated to the latest CVS LIBC on my XP box which I now use GCC 3.02
> (with Allegro fix). In checking that all the packages build I found that
> groff-1.16 does not build due to C++ issues.
> 
> I downloaded the latest stable release 1.17.2 from the GNU Groff home page
> and it compiles okay,

IMHO, it's not a good idea to use 1.17, since the HTML device driver
there is completely rewritten, and won't work with DJGPP unless
ported.  Porting it is a non-trivial job.  (Volunteers are welcome,
as always.)  That's the only reason I didn't release a port of 1.17
several months ago, when it hit teh GNU FTP site.

So I think it's better to fix whatever C++ problems you saw in 1.16,
and release an updated port.  That way, we can also make sure Groff
will build with older GCC versions as well (I think I tried 2.95
series at the time).

Perhaps posting the error messages you see in 1.16 would be a good
starting point.

- Raw text -