public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Barada <peter@baradas.org>
To: gcc@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Tue, 20 May 2003 06:12:00 -0000	[thread overview]
Message-ID: <20030520053204.ADDB298982@baradas.org> (raw)


I'm trying to build gcc-3.3 configured with:
/home/peter/work/cvs-local/xgcc/gcc-3.3/configure \
--with-gcc-version-trigger=/home/peter/work/cvs-local/xgcc/gcc-3.3/gcc/version.c \
--host=i686-pc-linux-gnu --target=m68k-elf --prefix=/tmp/m68k-elf \
--enable-languages=c,c++ --with-local-prefix=/tmp/m68k-elf/m68k-elf \
--with-headers=/tmp/m68k-elf/m68k-elf/include --norecursion 

and 'make all' bombs with:

/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/gcc/xgcc -B/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/gcc/ -B/tmp/m68k-elf/m68k-elf/bin/ -B/tmp/m68k-elf/m68k-elf/lib/ -isystem /tmp/m68k-elf/m68k-elf/include -c -DHAVE_CONFIG_H -O2 -g -O2 -I. -I/home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/../include  -W -Wall -Wtraditional -pedantic /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/vsprintf.c -o vsprintf.o
In file included from /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/vsprintf.c:29:
/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/gcc/include/varargs.h:4:2: #error "GCC no longer implements <varargs.h>."
/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/gcc/include/varargs.h:5:2: #error "Revise your code to use <stdarg.h>."
make[2]: *** [vsprintf.o] Error 1
make[2]: Leaving directory `/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/m68k-elf/libiberty'

gcc-3.3/lbiberty/vsprintf.c, indeed includes <varargs.h> (which gcc
supplise), so if gcc-3.3 has killed support for varargs,h, why is
libiberty/vsprintf.c trying to include it.  In fact, why is gcc-3.3
trying to build libiberty with the *target* compiler anyway?

Any suggestions?

-- 
Peter Barada
peter@baradas.org

             reply	other threads:[~2003-05-20  5:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  6:12 Peter Barada [this message]
2003-05-20  6:53 ` Erik Christiansen
2003-05-20 10:53   ` Kai Ruottu
2003-05-20 10:44 ` Kai Ruottu
2003-05-21  4:55   ` Peter Barada
2003-05-21  7:13     ` Peter Barada
2003-05-21 15:05       ` Randy Rude
2003-05-21 15:38         ` Peter Barada
2003-05-21 16:56           ` Randy Rude
2003-05-21 17:28             ` Joe Buck
2003-05-21 17:39           ` DJ Delorie
2003-05-22 14:59             ` Randy Rude
2003-05-22 17:36               ` DJ Delorie
2003-05-23 19:40                 ` Randy Rude
2003-05-22  3:14           ` Peter Barada
2003-05-22 12:17             ` Kai Ruottu
2003-05-22 13:33               ` Peter Barada
2003-05-23  3:25               ` Peter Barada
2003-05-20 16:19 ` DJ Delorie
2003-05-20 21:06   ` Kaveh R. Ghazi
2003-05-20 21:44     ` DJ Delorie
2003-05-23 15:30       ` Kaveh R. Ghazi
2003-05-23 17:49         ` Joe Buck
2003-05-23 18:17           ` Peter Barada
2003-05-23 18:17             ` Joe Buck
2003-05-23 18:39               ` Peter Barada

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20030520053204.ADDB298982@baradas.org \
    --to=peter@baradas.org \
    --cc=crossgcc@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).