PR 8146

[Daniel Jacobowitz]

On Fri, Nov 01, 2002 at 04:00:21PM -0800, Joe Buck wrote:
> > On Fri, Nov 01, 2002 at 03:45:09PM -0800, Joe Buck wrote:
> > > Well, I tried to duplicate this problem (grabbed 2.95.3, tried to build
> > > with gcc 3.2.1-pre from 20021031 on an i686 Red Hat 7.2 box) and didn't even
> > > get as far as Paul did.
> > > 
> > > The initial link of xgcc fails, with the output
> > > 
> > > /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> > > /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14.
> > > ../libiberty/libiberty.a(choose-temp.o): In function `choose_temp_base':
> > > /u/jbuck/gnu/src/gcc-2.95.3/libiberty/choose-temp.c:138: the use of `mktemp' is dangerous, better use `mkstemp'
> > > collect2: ld returned 1 exit status
> > > 
> > > The binutils version is 2.11.90.0.8.
> > > 
> > > Any clues?
> > 
> > Need a newer linker.
> 
> Well, OK, but gcc 3.2.1-pre successfully bootstraps itself with this
> linker.  What's the difference?
> 
> I suppose I could put in -gstabs or something in the pass 1 flags.

Huh, that's odd.  I'm not sure...

> > I wonder if the bootstrap failure could have something to do with the
> > changed <stdbool.h>...
> 
> Hard to see how this could be the case.

Well, just to show I'm not crazy, we had the opposite problem to the
one I was concerned about: relying on the new semantics, where bool is
_Bool instead of a normal integer and has certain arithmetic properties
because of that.  I believe the fix was:

2002-07-17  Neil Booth  <neil@daikokuya.co.uk>

        * cppexp.c (cpp_interpret_integer, append_digit, parse_defined,
        eval_token): Clarify and correct use of "bool" variables.
        * cpplib.h (struct cpp_options): Similarly.
        * cppmacro.c (parse_params, _cpp_save_parameter): Ditto.
        * cpptrad.c (recursive_macro): Similarly.


But it turns out 2.95.3 never includes <stdbool.h>, so that's not it
after all.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer