public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Karel Gardas <kgardas@objectsecurity.com>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: 4.0.1 build failure on powerpc64-linux
Date: Mon, 18 Jul 2005 10:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0507181248151.17136@silence.gardas.net> (raw)


Hello,

I'm trying to build 4.0.1 release on powerpc64-linux, but without success 
so far, since build fails with:

/usr/include/bits/stdio.h:77: undefined reference to `.__overflow'
build/errors.o(.text+0x214): In function `warning':
../../gcc-4.0.1/gcc/errors.c:50: undefined reference to `.fprintf'
build/errors.o(.text+0x228):../../gcc-4.0.1/gcc/errors.c:51: undefined 
reference to `.vfprintf'
build/errors.o(.text+0x274): In function `warning':
/usr/include/bits/stdio.h:77: undefined reference to `.__overflow'
build/errors.o(.text+0x2e4): In function `error':
../../gcc-4.0.1/gcc/errors.c:65: undefined reference to `.fprintf'
build/errors.o(.text+0x2f8):../../gcc-4.0.1/gcc/errors.c:66: undefined 
reference to `.vfprintf'
build/errors.o(.text+0x358): In function `error':
/usr/include/bits/stdio.h:77: undefined reference to `.__overflow'
build/errors.o(.text+0x3c4): In function `fatal':
../../gcc-4.0.1/gcc/errors.c:82: undefined reference to `.fprintf'
build/errors.o(.text+0x3d8):../../gcc-4.0.1/gcc/errors.c:83: undefined 
reference to `.vfprintf'
build/errors.o(.text+0x408):../../gcc-4.0.1/gcc/errors.c:86: undefined 
reference to `.exit'
build/errors.o(.text+0x414): In function `fatal':
/usr/include/bits/stdio.h:77: undefined reference to `.__overflow'
../build-powerpc64-unknown-linux-gnu/libiberty/libiberty.a(xmalloc.o)(.text+0x44): 
In function `xmalloc_set_program_name':
../../../gcc-4.0.1/libiberty/xmalloc.c:106: relocation truncated to fit: 
R_PPC_REL24 sbrk
../build-powerpc64-unknown-linux-gnu/libiberty/libiberty.a(xmalloc.o)(.text+0x7c): 
In function `xmalloc_failed':
../../../gcc-4.0.1/libiberty/xmalloc.c:119: relocation truncated to fit: 
R_PPC_REL24 sbrk
make[2]: *** [build/genmodes] Error 1
make[2]: Leaving directory `/tmp/kgardas/obj/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/tmp/kgardas/obj/gcc'
make: *** [bootstrap-lean] Error 2


I've configured it with:
  ../gcc-4.0.1/configure --prefix=$HOME/usr/local/gcc-4.0.1 --enable-shared 
--enable-threads --enable-languages=c++ --disable-checking 
--enable-__cxa_atexit

and run bootstrap-lean by:

time make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap-lean

Also, http://gcc.gnu.org/install/specific.html#powerpc-x-linux-gnu notes 
that binutils 2.15 are required, which seems to be available on this 
system (Debian 3.1/ppc64):

kgardas@tick:/tmp/kgardas/obj$ as --version
GNU assembler 2.15
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `powerpc-linux'.
kgardas@tick:/tmp/kgardas/obj$

kgardas@tick:/tmp/kgardas/obj$ ld --version
GNU ld version 2.15
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
kgardas@tick:/tmp/kgardas/obj$

Any hint how to solve this?

Thanks,
Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com

             reply	other threads:[~2005-07-18 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 10:53 Karel Gardas [this message]
2005-07-18 18:28 ` Janis Johnson
2005-07-18 19:06   ` Karel Gardas

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=Pine.LNX.4.63.0507181248151.17136@silence.gardas.net \
    --to=kgardas@objectsecurity.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).