X-pop3-spooler:	POP3MAIL 2.1.0 b 3 961213 -bs-
Delivered-To:	pcg AT goof DOT com
Message-ID:	<19980202211336.30140@prtr-13.gandalf.edu>
Date:	Mon, 2 Feb 1998 21:13:36 -0800
From:	Toshio Kuratomi <badger AT prtr-13 DOT ucsc DOT edu>
To:	beastium <beastium-list AT Desk DOT nl>
Cc:	nuke AT bayside DOT net
Subject:	Re: pgcc-980129 compile problem
References:	<19980201202316 DOT 44348 AT cerebro DOT laendle> <Pine DOT LNX DOT 3 DOT 96 DOT 980203021202 DOT 1617A-100000 AT nuklear DOT steelcity DOT net> <19980203033429 DOT 63395 AT cerebro DOT laendle>
Mime-Version:	1.0
X-Mailer:	Mutt 0.85e
In-Reply-To:	<19980203033429.63395@cerebro.laendle>; from Marc Lehmann on Tue, Feb 03, 1998 at 03:34:29AM +0100
Sender:	Marc Lehmann <pcg AT goof DOT com>
Status:	RO
X-Status:	A
Lines:	41

On Tue, Feb 03, 1998 at 03:34:29AM +0100, Marc Lehmann set free these words:
> On Tue, Feb 03, 1998 at 02:14:35AM +0000, nuke AT bayside DOT net wrote:
> > > I guess it is a redhat 5.0 system? (and may I guess this hapens with egcs
> > > also?)
> > 
> > nope, debian-hamm system.. based on glibc2 like redhat 5.0
> 
> inetresting.. it's quiite interesting, strange, weird, ...
> 
> > Reading specs from
> > /usr/local/lib/gcc-lib/i586-pc-linux-gnu/pgcc-2.90.21/specs
> > gcc version pgcc-2.90.21 971202 (egcs-1.00 release)
> 
> hm.
> 
> > is there any place i should look for that? i'm guessing that it has
> > something to do with this being a glibc2 system, and that not being
> > detected right
> 
> unless you configure'd sth. else than i586-pc-linux-gnu, this should
> not be the case. anyway, what makes this so strange is that your
> _installed_ compiler is calling _it's_ cpp with wrong parameters,
> and the only cause I could imagine is that either thw wrong gcc is called,
> or the wrong specs file is read. Nothing happened here (I think).
> 
> A friend of mine has exactly this problem on a redhat-5.0 with egcs-1.0.1,
> when compiling with gcc-2.7.2.3, so I made a quick but wrong guess.
> 
> I still haven't the slightest idea.. I guess you have binutils-2.8.1.0.15?
> (not that this would cure the problems).
> 
> 
Do your cpp and gcc match up?  ie is the cpp that gcc is invoking the same
version or is it possible that you've got a mix'n match going on that's
confusing your tools?

-Toshio Kuratomi
-- 
badger  \"The Difference between today and yesterday is not so much what has
@prtr-13 \ changed between then and now as what I hope to change by tomorrow."
..ucsc.edu  \~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

- Raw text -