From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.3.2 - 64bit failled to build?
Date: Wed, 26 Nov 2003 13:19:35 -0500 [thread overview]
Message-ID: <20031126181935.GJ27674@systemhalted> (raw)
In-Reply-To: <3FB2652500007F03@ocpmta2.freegates.net>
On Wed, Nov 26, 2003 at 10:23:45AM +0100, Joel Soete wrote:
> Hi all,
>
> I am trying to rebuild gcc-3.3.2 64bits following Carlos build xc howto.
>
> I am using gcc-3.3.2-4 debian pkg src; after the extraction of src with 'dpkg-source
> -x gcc-3.3_3.3.2ds5-4.dsc', then in src tree apply debian patches (and get
> the actual src by the way).
>
> The build of the tool chain 32bit works fine as well as binutils 64bits but
> the build of the patial gcc 64bit (let say kgcc) with following configure
> options (the same as 32bit but the target 64bits):
> ../src/configure --target=hppa64-linux --host=hppa-linux --prefix=/opt/parisc
> --disable-shared --disable-nls --without-libc --enable-langages=c
>
> failled with messages:
>
> /Develop/parisc-linux/build/gcc/gcc/xgcc -B/Develop/parisc-linux/build/gcc/gcc/
> -B/opt/palinux/hppa64-linux/bin/ -B/opt/palinux/hppa64-linux/lib/ -isystem
> /opt/palinux/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include
> -fPIC -Dpa64=1 -DELF=1 -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
> -Dinhibit_libc -I. -I. -I/Develop/parisc-linux/sources/gcc/gcc -I/Develop/parisc-linux/sources/gcc/gcc/.
> -I/Develop/parisc-linux/sources/gcc/gcc/config -I/Develop/parisc-linux/sources/gcc/gcc/../include
> -fexceptions -c /Develop/parisc-linux/sources/gcc/gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o
> In file included from /Develop/parisc-linux/sources/gcc/gcc/unwind-dw2.c:26:
> /Develop/parisc-linux/sources/gcc/gcc/unwind-pe.h: In function `size_of_encoded_value':
> /Develop/parisc-linux/sources/gcc/gcc/unwind-pe.h:76: warning: implicit declaration
> of function `abort'
> In file included from gthr-default.h:1,
> from /Develop/parisc-linux/sources/gcc/gcc/gthr.h:98,
> from /Develop/parisc-linux/sources/gcc/gcc/unwind-dw2.c:28:
> /Develop/parisc-linux/sources/gcc/gcc/gthr-posix.h:37:21: pthread.h: No such
> file or directory
> /Develop/parisc-linux/sources/gcc/gcc/gthr-posix.h:38:20: unistd.h: No such
> file or directory
> In file included from gthr-default.h:1,
> from /Develop/parisc-linux/sources/gcc/gcc/gthr.h:98,
> from /Develop/parisc-linux/sources/gcc/gcc/unwind-dw2.c:28:
> [blabla]
>
> even thought i use --without-libc it seems to look for glibc header: pthread.h
> & unistd.h?
>
> Any idea?
You need the userspace headers for 64-bits. They don't exist, so I
normally hack them into place. Please try to use Kegel's crosstools and
see if you can get them building our cross-compiler? :)
If you want a quick fix, grab a current debian libc6-dev package, unpack
it using -x and move the /usr/include directory to your
$PREFIX/hppa64-linux directory so that the target headers are there.
c.
next prev parent reply other threads:[~2003-11-26 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 9:23 [parisc-linux] gcc-3.3.2 - 64bit failled to build? Joel Soete
2003-11-26 15:42 ` Randolph Chung
2003-11-26 18:51 ` Joel Soete
2003-11-26 18:19 ` Carlos O'Donell [this message]
2003-11-26 18:46 ` Joel Soete
2003-11-27 18:38 ` Joel Soete
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=20031126181935.GJ27674@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.