From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18465 invoked by alias); 17 May 2003 08:56:13 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18036 invoked by uid 71); 17 May 2003 08:56:01 -0000 Date: Sat, 17 May 2003 08:56:00 -0000 Message-ID: <20030517085601.18024.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Deron Meranda Subject: Re: bootstrap/10666: undefined ATTRIBUTE_NULL_PRINTF_3 Reply-To: Deron Meranda X-SW-Source: 2003-05/txt/msg01969.txt.bz2 List-Id: The following reply was made to PR bootstrap/10666; it has been noted by GNATS. From: Deron Meranda To: gcc-prs@gcc.gnu.org, benoit.sibaud@rd.francetelecom.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/10666: undefined ATTRIBUTE_NULL_PRINTF_3 Date: Sat, 17 May 2003 04:49:13 -0400 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10666 Also seen under hppa2.0-hp-hpux11.00 (32-bit) with gcc 3.3 final release. Using binutils 2.13.2.1. 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/2.13.2.1-32/include \ +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.