This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: 1.1.2 on Solaris 2.5: bootstrap failure in libio



  In message <19990324091433.B4171@ultra5.wi.leidenuniv.nl>you write:
  > 
  > --7iMSBzlTiPOCCT2k
  > Content-Type: text/plain; charset=us-ascii
  > 
  > On Wed, Mar 24, 1999 at 04:31:23 -0300, Alexandre Oliva wrote:
  > > It's weird; it seems that it's not finding definionts for most
  > > standard types.  What do you get if you run:
  > > 
  > > /local/ray/egcs/egcs-1.1.2/builddir/gcc/xgcc \
  > > -B/local/ray/egcs/egcs-1.1.2/builddir/gcc/ -I. -I../../../libio -E \
  > > dummy.c -DWCHAR=1 -DWCTYPE=1
  > > 
  > > Where dummy.c contains:
  > 
  > Attached.
  > 
  > > What does `type sed' print?  Which version of sed is that, if it happens
  > > to be GNU sed?
  > 
  > $ type sed
  > sed is /usr/local/gnu/bin/sed
  > $ sed --version
  > GNU sed version 3.00
Ding ding ding.

Finally enough bells go off...

gnu sed 3.00 is buggy.  I had numerous problems with libio when I installed
gnu sed 3.00 on my HPPA machines (hoping to work around bugs in hpux10.20's
sed)

Interestingly enough, we recently ran into a similar problem internally at
Cygnus, which, gee, went away when we threw sed 3.00 out the window.

Throw away gnu-sed 3.00 and see what happens.

jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]