From: Randy Rude <randy.rude@gdcanada.com>
To: Peter Barada <peter@baradas.org>
Cc: kai.ruottu@luukku.com, gcc@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Wed, 21 May 2003 15:05:00 -0000 [thread overview]
Message-ID: <1053527958.14557.1.camel@d1d6k111.bowman.gdcanada.com> (raw)
In-Reply-To: <20030521063417.3C30B98982@baradas.org>
On Wed, 2003-05-21 at 00:34, Peter Barada wrote:
>
> Now I'm scratching my head. After blowing away the installed
> components and the objects for the bootstrap, newlib, gcc, installed
> binutils, rebuild and installed the bootstrap and newlib, 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 \
> --with-newlib --enable-languages=c,c++ \
> --with-local-prefix=/tmp/m68k-elf/m68k-elf --norecursion
>
> Blows up with:
>
> make[2]: Entering directory `/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/m68k-elf/libiberty'
> if [ x"" != x ]; then \
> /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/hashtab.c -o pic/hashtab.o; \
> else true; fi
> /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/hashtab.c -o hashtab.o
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c: In function `higher_prime_number':
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:133: warning: implicit declaration of function `abort'
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c: In function `htab_create':
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:204: error: `free' undeclared (first use in this function)
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:204: error: (Each undeclared identifier is reported only once
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:204: error: for each function it appears in.)
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c: In function `htab_try_create':
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:214: error: `calloc' undeclared (first use in this function)
> /home/peter/work/cvs-local/xgcc/gcc-3.3/libiberty/hashtab.c:214: error: `free' undeclared (first use in this function)
> make[2]: *** [hashtab.o] Error 1
> make[2]: Leaving directory `/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc/m68k-elf/libiberty'
> make[1]: *** [install-target-libiberty] Error 2
> make[1]: Leaving directory `/home/peter/work/cvs-local/xgcc/obj/m68k-elf/m68k-elf-gcc'
> make: *** [install-gcc] Error 2
>
> I don't have a clue why its failing, especially when it built
> before(ok, on top of a previously failed misconfigured build). Any
> suggestions on what to look for?
>
> --
> Peter Barada
> peter@baradas.org
>
This looks familiar. Try applying the hashtab.c portion of this patch:
http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00726.html
Randy
next prev parent reply other threads:[~2003-05-21 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 6:12 Peter Barada
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 [this message]
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=1053527958.14557.1.camel@d1d6k111.bowman.gdcanada.com \
--to=randy.rude@gdcanada.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kai.ruottu@luukku.com \
--cc=peter@baradas.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).