From: "Stephen P. Becker" <geoman@gentoo.org>
To: TheNop <TheNop@gmx.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Cross tool chain based on gcc-3.4.x
Date: Mon, 29 Nov 2004 18:01:35 -0500 [thread overview]
Message-ID: <41ABAA4F.6030403@gentoo.org> (raw)
In-Reply-To: <41ABA8E2.40709@gmx.net>
> Hi Steve,
>
> I also want to build a root file system for the target.
> I tried to build the tool chain you described above.
> I used crossdev on gentoo: "crossdev --arch=mips --vbinutils=2.15.91.0.2
> --vheaders=2.4.25 --vgcc=3.4.3 --vglibc=2.3.4.20041102"
> But it fails.
>
> mips/mips-unknown-linux-gnu/sys-include -O2 -DIN_GCC -DCROSS_COMPILE
> -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -isystem ./include -fPIC -DHAVE_SYSLOG -g
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -D_LIBC_PROVIDES_SSP_ -I. -I.
> -I../../gcc -I../../gcc/. -I../../gcc/../include -DL_eprintf -c
> ../../gcc/libgcc2.c -o libgcc/./_eprintf.o
> /var/tmp/portage/crossdevbuild/gcc-3.4.3/buildboothere-mips/gcc/xgcc
> -B/var/tmp/portage/crossdevbuild/gcc-3.4.3/buildboothere-mips/gcc/
> -B/home/crossdev/mips/mips-unknown-linux-gnu/bin/
> -B/home/crossdev/mips/mips-unknown-linux-gnu/lib/ -isystem
> /home/crossdev/mips/mips-unknown-linux-gnu/include -isystem
> /home/crossdev/mips/mips-unknown-linux-gnu/sys-include -O2 -DIN_GCC
> -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC
> -DHAVE_SYSLOG -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
> -D_LIBC_PROVIDES_SSP_ -I. -I. -I../../gcc -I../../gcc/.
> -I../../gcc/../include -DL__gcc_bcmp -c ../../gcc/libgcc2.c -o
> libgcc/./__gcc_bcmp.o
> ../../gcc/unwind-dw2.c: In function `uw_frame_state_for':
> ../../gcc/unwind-dw2.c:1027: error: structure has no member named `sc_regs'
> ../../gcc/unwind-dw2.c:1027: error: structure has no member named `sc_pc'
> make[2]: *** [libgcc/./unwind-dw2.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory
> `/var/tmp/portage/crossdevbuild/gcc-3.4.3/buildboothere-mips/gcc'
> make[1]: *** [libgcc.a] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/crossdevbuild/gcc-3.4.3/buildboothere-mips/gcc'
> make: *** [all-gcc] Error 2
>
> How did you build the tool chain?
> What kernel headers did you use?
> If I use kernel headers 2.6.8.1 (I realy need 2.6 heraders!) the
> installation of the headers fails!
>
> It would be great If you can tell me which paramerter I have to use with
> crossdev to get a working tool chain.
>
> Best regards
> TheNop
Well, this really is more of a question for the gentoo-mips mailing
list. But anyway, 2.4 headers newer than our 2.4.22-r1 ebuild are
broken (I can't remember exactly how at the moment), and we *really*
don't support 2.6 headers at all. In fact, building against them breaks
glibc on o32 userland. The only reason we have them in portage at all
right now is for our n32 userland (which is broken in other ways because
of the headers). Eventually we'll have a sanitized 2.6 headers package
that should work, but it may not be anytime soon.
Anyway to answer your question, I used crossdev to build a bootstrap C
compiler (crossdev -k), then I did the rest by hand. You might also
need to get kumba's latest version of the crossdev script from gentoo's
viewcvs under gentoo/users/kumba/crossdev/ just to get past the first part.
Why do you *need* 2.6 headers anyhow? You can still run a 2.6 kernel
with a userland compiled with 2.4 headers.
Steve
next prev parent reply other threads:[~2004-11-29 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 23:56 Cross tool chain based on gcc-3.4.x TheNop
2004-11-24 1:29 ` Stephen P. Becker
2004-11-24 22:53 ` TheNop
2004-11-24 23:05 ` TheNop
2004-11-25 1:34 ` Stephen P. Becker
2004-11-29 22:55 ` TheNop
2004-11-29 23:01 ` Stephen P. Becker [this message]
2004-11-29 23:17 ` TheNop
2004-11-24 11:13 ` Thomas Petazzoni
2004-11-24 23:00 ` TheNop
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=41ABAA4F.6030403@gentoo.org \
--to=geoman@gentoo.org \
--cc=TheNop@gmx.net \
--cc=linux-mips@linux-mips.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 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.