Subject: Re: current on vax, problems
To: David Laight <firstname.lastname@example.org>
From: Johnny Billquist <email@example.com>
Date: 11/20/2003 16:10:07
On Thu, 20 Nov 2003, David Laight wrote:
> On Wed, Nov 19, 2003 at 09:37:07PM +0100, Johnny Billquist wrote:
> > 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 ?
I would say so, yes. But from what I gather, texinfo is just imported into
the build system, and not exactly totally under our control.
But I'm not sure this requires gcc. The problem here is that gcc on the
VAX is inconsistent. The problem stems from the fact that gcc on the VAX
don't add an "_" before user symbols. gcc also have a macro, called
USER_LABEL_PREFIX, which should be set to the symbol prefixed to user
symbols. On the VAX, this should then be "", but if you check, you'll
discover that this symbol is set to "_". So symbols don't get an "_", but
if you use USER_LABEL_PREFIX to try to figure out how the symbols look,
you'll errenously prefix them with a "_", which is what happens in
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: firstname.lastname@example.org || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol