Sender:	root AT eduserv1 DOT rug DOT ac DOT be
Message-ID:	<36F58159.632922CB@rug.ac.be>
Date:	Mon, 22 Mar 1999 00:31:37 +0100
From:	Marc Palmans <marc DOT palmans AT rug DOT ac DOT be>
X-Mailer:	Mozilla 4.07 [en] (X11; I; Linux 2.2.2 i686)
MIME-Version:	1.0
To:	pgcc AT delorie DOT com
Subject:	Re: Problems compiling pgcc from CVS
References:	<19990316200314 DOT A4892 AT physik DOT fu-berlin DOT de> <36EF9AFA DOT 9D07F421 AT rug DOT ac DOT be> <36EFDAF4 DOT 1CA6C6FD AT mr DOT telia DOT no> <36F07964 DOT 55B1BD7D AT rug DOT ac DOT be> <36F0EECC DOT E1B7601 AT mr DOT telia DOT no>
Reply-To:	pgcc AT delorie DOT com

Knut Arne Storeide wrote:
> 
> Marc Palmans wrote:
> >
> > Knut Arne Storeide wrote:
> > >
> > *snip*
> > > _fixtfdi
> > > ./libgcc2.c:809: parse error before `a'
> > > ./libgcc2.c: In function `__fixtfdi':
> > > ./libgcc2.c:811: `a' undeclared (first use in this function)
> > > ./libgcc2.c:811: (Each undeclared identifier is reported only once
> > > ./libgcc2.c:811: for each function it appears in.
> > > make[1]: *** [libgcc2.a] Error 1
> > > make[1]: Leaving directory `/root/build/pgcc/gcc'
> > > make: *** [all-gcc] Error 2
> > > [root AT sartre pgcc]#
> > >
> > > I am not capable of determining what goes worng, but then I prefer Lisp
> > > :-)
> > > Anybody
> > It shouldn't compile even those lines because the double type size of an
> > i386 is
> > 96 not 128. Maybe you configured for another target? (tm.h should
> > contain
> > i386/linux.h) Try running ./configure to see which target system type it
> > chooses.
>
> Well this is bizarre. I have configured pgcc for the i686-pc-linux-gnu
> host/target, and tm.h _does_ include i386/linux.h

The only thing I can come up with is that the file itself got screwed
up. It 
should contain these lines :

#if defined(L_fixtfdi) && (LIBGCC2_LONG_DOUBLE_TYPE_SIZE == 128)
  blabla
#endif

If you can't see any difference mail me libgcc2.c and the complete
output of 
"make libgcc2.a" (You might need to remove libgcc2.ready). Please don't
mail
them to the list... 
In the mean time you could backup the file and delete or comment out
those lines
They shouldn't be compiled in anyway.  

Greets,
Marc Palmans

- Raw text -