X-pop3-spooler: POP3MAIL 2.1.0 b 3 961213 -bs-
Delivered-To: pcg AT goof DOT com
From: johan19 AT idt DOT net
Message-ID: <19980201142736.22334@sophia.idt.net>
Date: Sun, 1 Feb 1998 14:27:36 -0800
To: beastium-list AT Desk DOT nl
Subject: Re: pgcc-980129 compile problem
References: <Pine DOT LNX DOT 3 DOT 96 DOT 980201094903 DOT 12787A-100000 AT nuklear DOT steelcity DOT net> <19980201202316 DOT 44348 AT cerebro DOT laendle>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85e
In-Reply-To: <19980201202316.44348@cerebro.laendle>; from Marc Lehmann on Sun, Feb 01, 1998 at 08:23:16PM +0100
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
X-Status: A
Content-Length: 1543
Lines: 39

On Sun, Feb 01, 1998 at 08:23:16PM +0100, Marc Lehmann wrote:
> On Sun, Feb 01, 1998 at 09:52:28AM +0000, nuke AT bayside DOT net wrote:
> > i get this compiling the latest pgcc:
> 
> I guess it is a redhat 5.0 system? (and may I guess this hapens with egcs
> also?)
> 
> I once tried to track it down (on the phone) with a friend, but couldn't
> find out what it was. (help appreciated ;)
> 
> > -lang-c -I. -I. -I./config -undef -D__GNUC__=2 -D__GNUC_MINOR__=7
> > -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix
> > -D__linux -Asystem(posix) -D__OPTIMIZE__ -Di386 -Di586 -Asystem(unix)
> > -Acpu(i386) -Amachine(i386) -D__i386__ -D__i586__ -Asystem(unix)__
> > -Acpu(i386)__ -Amachine(i386)__ __ __ __ __ __ __
> > __ __ __ __ __ __ __ __ -DIN_LIBGCC1 -DL_mulsi3 ./libgcc1.c
> > /tmp/cca13517.i
>
> since your _installed_ gcc calls cpp with illegal args, this is most
> probably a bug in the gcc you already have installed.. it might be that gcc
> is searching for the wrong files (but I can only imagine the specs file)
> 
> is it 2.7.2.3 from redhat?
> 
> > those __'s aren't valid cpp options, and they're messing things up
> > i really have no idea why it's doing this.
> 
> Bad, I don't have either, although I would reaaly like to find
> out why gcc is doing sth. that dumb, but I can't reproduce it!

i got that when i tried using a 2.7.2 spec file with pgcc.  the spec
file syntaxs differ slightly (don't ask me why) and that produces all
those spurious `__' marks.

hope this helps.

-- 
Johan Kullstam
johan19 AT idt DOT net