Subject: Re: current on vax, problems
To: David Laight <firstname.lastname@example.org>
From: None <email@example.com>
Date: 11/20/2003 10:58:44
> On Wed, Nov 19, 2003 at 09:37:07PM +0100, Johnny Billquist wrote:
> > On Wed, 19 Nov 2003 firstname.lastname@example.org wrote:
> > [...]
> > > > This is the texinfo error that I mentioned. Ragge claims he checked in a
> > > > few a few weeks ago. If this is from a fresh -current, then Ragge must
> > > > have missed it.
> > > >
> > > No, but the _installed_ cpp must be recompiled and replaced with a
> > > fixed one. Libintl uses some gcc-special tricks when compiling the tools.
> > Aha! You found the problem in gcc (or did you do a real hack to fix it)?
> > Good news anyway. That means you fixed it the proper way instead of my
> > hacks...
> Am I being stupid, or shouldn't the tools be buildable with any (reasonable)
> C compiler? So requiring gcc for a tool is a no-no ?
Well, libintl doesn't require gcc, but if configure finds gcc it tries
to use some gcc-special tricks, and if those tricks are broken then
there is nothing to do...