Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: TheNop <TheNop@gmx.net>
To: "Stephen P. Becker" <geoman@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Cross tool chain based on gcc-3.4.x
Date: Mon, 29 Nov 2004 23:55:30 +0100	[thread overview]
Message-ID: <41ABA8E2.40709@gmx.net> (raw)
In-Reply-To: <41A536A5.5050508@gentoo.org>

Stephen P. Becker wrote:

> TheNop wrote:
>
>> Stephen P. Becker wrote:
>>
>>> TheNop wrote:
>>>
>>>> Hello,
>>>>
>>>> I try to get a cross compiler based on
>>>> gcc-3.4.2
>>>> glibc-2.3.2
>>>> binutils-2.15
>>>> working;  without success.
>>>>
>>>> Is anyone using a cross compiler base on  gcc-3.4.x for a mips big 
>>>> endian target?
>>>>
>>>> Best regarts
>>>> TheNop
>>>>
>>>
>>> I've got a very recent i686->mips-unknown-linux-gnu cross-toolchain 
>>> available 
>>> at:http://dev.gentoo.org/~geoman/mips-glibc-crosstools.tar.bz2 if 
>>> you are too frustrated with building your own.
>>>
>>> It includes gcc-3.4.3, glibc-2.3.4 (20041102), and binutils 
>>> 2.15.91.0.2.
>>>
>>> Steve
>>>
>>>
>> Hi Steve,
>>
>> thanx a lot.
>> This tool chain works perfectly for me. Now I can build 2.6.x kernel.
>> In the past I tried to build a cross tool chain using crosstools. I 
>> don`t get any combination of gcc-3.4.x/glibc-2.x.x working. Only the 
>> gcc-3.4.x-glibc-2.3.3 combination I could compile without errors, but 
>> I couldn't compile a 2.6.x kernel.
>>
>> Could you please tell me, how you compile the tool chain?
>> It would be great, if you can provide me a script or a list of 
>> patches you applied for building.
>>
>> Best regards
>> TheNop
>>
>>
>
> Actually, if you just wanted to build kernels, you don't need glibc at 
> all.  Just build binutils and then a bootstrap gcc compiler, and you 
> are set.  The only reason I messed with a full toolchain at all is so 
> that I can use c++ through distcc.
>
> Steve
>
>
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

  reply	other threads:[~2004-11-29 22:49 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 [this message]
2004-11-29 23:01         ` Stephen P. Becker
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=41ABA8E2.40709@gmx.net \
    --to=thenop@gmx.net \
    --cc=geoman@gentoo.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox