X-pop3-spooler: POP3MAIL 2.1.0 b 3 961213 -bs- Delivered-To: pcg AT goof DOT com Message-ID: <19980202001443.25513@cerebro.laendle> Date: Mon, 2 Feb 1998 00:14:43 +0100 From: Marc Lehmann To: beastium Subject: Re: pgcc-980129 compile problem References: <19980201202316 DOT 44348 AT cerebro DOT laendle> <19980201142736 DOT 22334 AT sophia DOT idt DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980201142736.22334@sophia.idt.net>; from johan19@idt.net on Sun, Feb 01, 1998 at 02:27:36PM -0800 X-Operating-System: Linux version 2.1.82 (root AT cerebro) (gcc version pgcc-2.91.05 980122 (gcc-2.8.0 release)) Status: RO Content-Length: 1261 Lines: 27 On Sun, Feb 01, 1998 at 02:27:36PM -0800, johan19 AT idt DOT net wrote: > 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: > > > > 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. Interesting.. I thought maybe gcc-2.7.2 would mistakenly read the specs file from egcs/pgcc (which is in the same directory), but a strace of gcc didn't show anything abnormal (although I didn't see the strace outpout myself..) > hope this helps. It's a good hint, yes. -----==- | ----==-- _ | ---==---(_)__ __ ____ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / pcg AT goof DOT com |e| -=====/_/_//_/\_,_/ /_/\_\ --+ The choice of a GNU generation | |