On Wed, 19 Nov 2003, John Klos wrote:

> > > I thought, that if I take a fresh install of 1.6 or 1.6.1, I could
> > > update my system to -current, simply using the "./build.sh" script.
> >
> > That's the general idea.
> >
> > In this case it's not true because the cpp in both 1.6 and 1.6.1 is
> > actually broken. And from a broken tool, you'll get problems.
> > I just posted the solution a few minutes ago.
> 
> What's the solution for those of us running release? I don't suppose the
> fix has been pulled up, yet, has it? Could it make it for 1.6.2?

I have no idea. Officially I'm not among the developers. I just fool
around in the shadows of the vax-port.

> I gather that you're recommending to build and install gcc from current
> over release?

The only program I know of where this bites you is texinfo built
natively. If you happen to find the same problem somewhere else, then
yes - gcc in current is what you need.

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol