public inbox for
help / color / mirror / Atom feed
From: Deron Meranda <>
Subject: Re: bootstrap/10666: undefined ATTRIBUTE_NULL_PRINTF_3
Date: Sat, 17 May 2003 08:56:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR bootstrap/10666; it has been noted by GNATS.

From: Deron Meranda <>
Subject: Re: bootstrap/10666: undefined ATTRIBUTE_NULL_PRINTF_3
Date: Sat, 17 May 2003 04:49:13 -0400
 Also seen under hppa2.0-hp-hpux11.00 (32-bit) with
 gcc 3.3 final release.   Using binutils
 As mentioned, it is picking up the ansidecl.h under binutils
 rather than gcc/include.  Since the only diffs seem to be
 these ATTRIBUTE_ macros, you can temporarily work around the
 bootstrap problem by replacing the ansidecl.h header in
 binutils with the one from gcc 3.3.  This is obviously not a
 correct fix, but will allow the stage1 compiler to be built.
 For the record, here's the compile line in my setup which
 ends up including the wrong ansidecl.h...
 /usr/bin/cc -Ae -z +ESlit +DA2.0 \
     -I/opt/gnu/binutils/ \
     +Z -c   -g  -DIN_GCC     -DHAVE_CONFIG_H \
     -I. -I. -I/opt2/gnu/src/gcc/gcc-3.3/gcc \
     -I/opt2/gnu/src/gcc/gcc-3.3/gcc/. \
     -I/opt2/gnu/src/gcc/gcc-3.3/gcc/config \
     -I/opt2/gnu/src/gcc/gcc-3.3/gcc/../include \
     /opt2/gnu/src/gcc/gcc-3.3/gcc/dwarf2asm.c \
     -o dwarf2asm.o
 The first -I directory was a direct result of me specifying
 it in $CC/$CFLAGS during the configure phase (needed because I
 have many different compilers and several different binutils
 versions on the system).  So this may be "user error" on my
 part.  But it seems like an easy error to make, so it may be
 worth a mention in the install notes until binutils catches
 up with gcc.

             reply	other threads:[~2003-05-17  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  8:56 Deron Meranda [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16 11:46 Benoît SIBAUD
2003-05-12 20:06 Benoît SIBAUD
2003-05-07 16:16 benoit.sibaud

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).