RE: Cross-compile package combinations

RE: Cross-compile package combinations

[Silverton Aron-C1710C]

Continuing this top-posting madness:

I am trying to build gcc 3.2.3 for powerpc-linux on i386.  I have binutils
2.14 built already.  I have not done anything with glibc as of yet.  Here is
where I die:

[lots of stuff omitted]
mkdir libgcc
mkdir nof
mkdir libgcc/nof
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/xgcc
-B/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/bin/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/lib/ -isystem
/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/include -O2  -DIN_GCC
-DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-I../../gcc-3.2.3/gcc -I../../gcc-3.2.3/gcc/. -I../../gcc-3.2.3/gcc/config
-I../../gcc-3.2.3/gcc/../include  -fPIC -mstrict-align -DL_muldi3 -c
../../gcc-3.2.3/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from tconfig.h:21,
                 from ../../gcc-3.2.3/gcc/libgcc2.c:36:
../../gcc-3.2.3/gcc/config/rs6000/linux.h:81:20: signal.h: No such file or
directory
../../gcc-3.2.3/gcc/config/rs6000/linux.h:82:26: sys/ucontext.h: No such
file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make: *** [all-gcc] Error 2

I issued the commands:

$ ../gcc-3.2.3/configure --target=$TARGET --prefix=${PREFIX}
--without-headers --with-newlib --enable-langauges=c

$ make all-gcc

I am not using crosstools.  I may trie it if I can figure out how to specify
the paths to put everything where I want it.

Any suggestions?

Thanks,

Aron

owner-linuxppc-embedded@lists.linuxppc.org
<mailto:owner-linuxppc-embedded@lists.linuxppc.org> wrote:
> I have indeed tried a fairly recent version of GCC, the
> aforementioned 3.2.3 with Linux 2.4.23 and it works like a charm
> in our PPC environment. I didn't bother with the 3.3.x release of
> GCC mainly because other toolchains used for other stuff in our
> environment also used 3.2.3, so I wanted to stay in lockstep with
> those versions.
>
> ~Ashwin
>
>
>
>
>> From: "listmember@orkun.us" <listmember@orkun.us>
>> To: linuxppc-embedded@lists.linuxppc.org
>> CC: "Dan Kegel" <dank@kegel.com>
>> Subject: Re: Cross-compile package combinations
>> Date: Thu, 11 Dec 2003 10:06:40 -0600 (CST)
>>
>>
>>>
>>> Silverton Aron-C1710C wrote:
>>>> Hello all,
>>>>
>>>> Can somebody give me a clue as to which versions of binutils,
>>>> gcc, and glibc are compatible with each other?  I'd like to
>>>> use gcc 3.2 or 3.3 and I am developing on i386 targeting
>>>> PowerPC.  I'll be using 2.4 kernels initially and then moving
>>>> to 2.6.
>>>>
>>>> If there is a known reference or recent previous post (I
>>>> didn't see one in my initial search) I'd appreciate a pointer.
>>>
>>> As Ashwin mentioned, http://kegel.com/crosstool might come in
>>> handy. See also the matrix at http://embeddedtux.org.
>>> - Dan
>>
>> Funny, I was just about to ask  very similar question. I will be
>> working an a IBM PPC405G based development board (Cogent CSB272)
>> for an internal project. I would like to use as up-to-date
>> versions of GCC, GLIBC and Linux 2.4 kernel as possible (without
>> sacrificing stability).
>>
>> - Has anyone used recently released 2.4.23 (kernel.org) in any
>> PPC project yet? If it is not good to use for PPC based
>> development? Do I need to get a ppc specific modified kernel or
>> do I need to apply any patches to linus 2.4.23 kernel to get it
>> working in PPC405 embedded environment.
>>
>> - Kernel 2.4.x README still says the official kernel compiler is
>> gcc
>> 2.95.3. Is it still the case or using a more recent GCC compiler
>> is now acceptable? In the last Linux embedded project I was in
>> we had used this one along with a very early build of kernel. I
>> was not the one to set the development environment so bear with
>> me if these sound basic questions to you.
>>
>> - I built a toolchain using crosstools based on gcc 3.3.2, glibc
>> 2.3.2 and binutils 2.14.90.0.5. Crosstools default .dat files
>> pull kernel
>> 2.4.21 but I also got the tools compiled using 2.4.23 sources. I
>> have not tested them yet since I don't have the board yet? Any
>> comments regarding this combination?
>>
>> Looking at some ppc linux distros (not necessarily embedded):
>>
>> YDL 3.0: kernel 2.4.20, gcc ? glibc 2.3.1, binutils ?
>> Mandrake: kernel 2.3.21, gcc 3.2.2, glibc, 2.3.1, binutils ?
>> Gentoo: kernel 2.4.22, gcc ? glibc 2.3.2?, binutils ?
>>
>> Tolunay
>>
>>
>
>
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Beena]

I have observed the same errors when trying to build the bootstrap gcc
3.2.3. I understand that
this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
files. So I first built gcc 2.95.3,
then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
3.2.3) and it compiled fine.

Hope this helps.
Beena

-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of
Silverton Aron-C1710C
Sent: Thursday, December 11, 2003 1:57 PM
To: 'Ashwin Bihari'; 'listmember@orkun.us';
'linuxppc-embedded@lists.linuxppc.org'
Cc: 'dank@kegel.com'
Subject: RE: Cross-compile package combinations



Continuing this top-posting madness:

I am trying to build gcc 3.2.3 for powerpc-linux on i386.  I have binutils
2.14 built already.  I have not done anything with glibc as of yet.  Here is
where I die:

[lots of stuff omitted]
mkdir libgcc
mkdir nof
mkdir libgcc/nof
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/xgcc
-B/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/bin/
-B/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/lib/ -isystem
/usr/proj/ssr/linux_bsp/mcip805/tools/powerpc-linux/include -O2  -DIN_GCC
-DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-I../../gcc-3.2.3/gcc -I../../gcc-3.2.3/gcc/. -I../../gcc-3.2.3/gcc/config
-I../../gcc-3.2.3/gcc/../include  -fPIC -mstrict-align -DL_muldi3 -c
../../gcc-3.2.3/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from tconfig.h:21,
                 from ../../gcc-3.2.3/gcc/libgcc2.c:36:
../../gcc-3.2.3/gcc/config/rs6000/linux.h:81:20: signal.h: No such file or
directory
../../gcc-3.2.3/gcc/config/rs6000/linux.h:82:26: sys/ucontext.h: No such
file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory
`/usr/proj/ssr/linux_bsp/mcip805/build-tools/build-boot-gcc/gcc'
make: *** [all-gcc] Error 2

I issued the commands:

$ ../gcc-3.2.3/configure --target=$TARGET --prefix=${PREFIX}
--without-headers --with-newlib --enable-langauges=c

$ make all-gcc

I am not using crosstools.  I may trie it if I can figure out how to specify
the paths to put everything where I want it.

Any suggestions?

Thanks,

Aron


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Cross-compile package combinations

[Dan Kegel]

Beena wrote:
> I have observed the same errors when trying to build the bootstrap gcc
> 3.2.3. I understand that
> this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
> files. So I first built gcc 2.95.3,
> then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
> 3.2.3) and it compiled fine.

One of the reasons I did crosstool was to avoid that kind of
hackery.  With crosstool, you don't need to build gcc 2.95.3
just to build gcc 3.2.3.  Crosstool does clean builds from pristine,
minimally patched source.
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Beena]

I used crosstool and was able to effortlessly install gcc 3.3.2, glibc 2.3.2
for powerpc. Thanks a lot for your suggestion.

-Beena

-----Original Message-----
From: Dan Kegel [mailto:dank@kegel.com]
Sent: Thursday, December 11, 2003 8:26 PM
To: Beena
Cc: Silverton Aron-C1710C; 'Ashwin Bihari'; listmember@orkun.us;
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross-compile package combinations


Beena wrote:
> I have observed the same errors when trying to build the bootstrap gcc
> 3.2.3. I understand that
> this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
> files. So I first built gcc 2.95.3,
> then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
> 3.2.3) and it compiled fine.

One of the reasons I did crosstool was to avoid that kind of
hackery.  With crosstool, you don't need to build gcc 2.95.3
just to build gcc 3.2.3.  Crosstool does clean builds from pristine,
minimally patched source.
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Ashwin Bihari]

>I was referring to the kernel headers used to build the tools as opposed to
>the building of the actual kernel.  I'll have to look through the crosstool
>scripts, but I'd guess that if the file already exists, it won't download
>it.  I'll probably bump up the version on my kernel to match what crosstool
>wants to see and then put it in the location that I specified in my
>crosstool configuration.
>
>Thanks,
>
>Aron

Aron,

Ahh my bad! :) There is a kernel header define that you can set. On the
version of crosstool I used, they were on top of that file. I just manually
pointed it to the kernel source/headers I had and it was happy.

~Ashwin

_________________________________________________________________
Get holiday tips for festive fun.
http://special.msn.com/network/happyholidays.armx


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Silverton Aron-C1710C]

Ashwin Bihari <mailto:raz0redge@hotmail.com> wrote:
>> I do have a another question, though.  Let's say that I want to
>> use my own kernel instead of having crosstool download it.  What
>> would be the proper set of steps to take to specify a local
>> kernel?  My current kernel is
>> 2.4.20 and I know that the combination of gcc and glibc that I
>> want to use with crosstool specifies 2.4.21.  I'll probably work
>> on bumping my kernel up.
>>
>> Aron
>
> The way I did this was to use crosstool to just create the
> cross-compiler for me. From there I took it upon myself to
> install it in the appropriate directory and then compile the
> kernel I wanted. That proved to be easy enough for me.
>
> ~Ashwin
>

Ashwin

I was referring to the kernel headers used to build the tools as opposed to the building of the actual kernel.  I'll have to look through the crosstool scripts, but I'd guess that if the file already exists, it won't download it.  I'll probably bump up the version on my kernel to match what crosstool wants to see and then put it in the location that I specified in my crosstool configuration.

Thanks,

Aron


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Ashwin Bihari]

>I do have a another question, though.  Let's say that I want to use my own
>kernel instead of having crosstool download it.  What would be the proper
>set of steps to take to specify a local kernel?  My current kernel is
>2.4.20 and I know that the combination of gcc and glibc that I want to use
>with crosstool specifies 2.4.21.  I'll probably work on bumping my kernel
>up.
>
>Aron

The way I did this was to use crosstool to just create the cross-compiler
for me. From there I took it upon myself to install it in the appropriate
directory and then compile the kernel I wanted. That proved to be easy
enough for me.

~Ashwin




>From: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
>To: "'Beena'" <beena@gdatech.com>, "'Dan Kegel'" <dank@kegel.com>
>CC: "'Ashwin Bihari'" <raz0redge@hotmail.com>,
>"'listmember@orkun.us'" <listmember@orkun.us>,
>"'linuxppc-embedded@lists.linuxppc.org'"
><linuxppc-embedded@lists.linuxppc.org>
>Subject: RE: Cross-compile package combinations
>Date: Tue, 16 Dec 2003 12:53:40 -0600
>
>
>I also had success using crosstool.  Thanks to all those who gave me tips
>both on the list and via email.
>
>
>Beena <mailto:beena@gdatech.com> wrote:
> > I used crosstool and was able to effortlessly install gcc 3.3.2,
> > glibc 2.3.2 for powerpc. Thanks a lot for your suggestion.
> >
> > -Beena
> >
> > -----Original Message-----
> > From: Dan Kegel [mailto:dank@kegel.com]
> > Sent: Thursday, December 11, 2003 8:26 PM
> > To: Beena
> > Cc: Silverton Aron-C1710C; 'Ashwin Bihari'; listmember@orkun.us;
> > linuxppc-embedded@lists.linuxppc.org Subject: Re: Cross-compile
> > package combinations
> >
> >
> > Beena wrote:
> >> I have observed the same errors when trying to build the
> >> bootstrap gcc
> >> 3.2.3. I understand that this is because gcc 3.2.3 build (in
> >> case of powerpc) looks for some glibc files. So I first built
> >> gcc 2.95.3, then glibc 2.2.1 and then built bootstrap gcc
> >> 3.2.2(you could try with
> >> 3.2.3) and it compiled fine.
> >
> > One of the reasons I did crosstool was to avoid that kind of
> > hackery.  With crosstool, you don't need to build gcc 2.95.3 just
> > to build gcc 3.2.3.  Crosstool does clean builds from pristine,
> > minimally patched source.
> > - Dan
>
>

_________________________________________________________________
Cell phone ‘switch’ rules are taking effect — find out more here.
http://special.msn.com/msnbc/consumeradvocate.armx


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Silverton Aron-C1710C]

I also had success using crosstool.  Thanks to all those who gave me tips both on the list and via email.

I do have a another question, though.  Let's say that I want to use my own kernel instead of having crosstool download it.  What would be the proper set of steps to take to specify a local kernel?  My current kernel is 2.4.20 and I know that the combination of gcc and glibc that I want to use with crosstool specifies 2.4.21.  I'll probably work on bumping my kernel up.

Aron

Beena <mailto:beena@gdatech.com> wrote:
> I used crosstool and was able to effortlessly install gcc 3.3.2,
> glibc 2.3.2 for powerpc. Thanks a lot for your suggestion.
>
> -Beena
>
> -----Original Message-----
> From: Dan Kegel [mailto:dank@kegel.com]
> Sent: Thursday, December 11, 2003 8:26 PM
> To: Beena
> Cc: Silverton Aron-C1710C; 'Ashwin Bihari'; listmember@orkun.us;
> linuxppc-embedded@lists.linuxppc.org Subject: Re: Cross-compile
> package combinations
>
>
> Beena wrote:
>> I have observed the same errors when trying to build the
>> bootstrap gcc
>> 3.2.3. I understand that this is because gcc 3.2.3 build (in
>> case of powerpc) looks for some glibc files. So I first built
>> gcc 2.95.3, then glibc 2.2.1 and then built bootstrap gcc
>> 3.2.2(you could try with
>> 3.2.3) and it compiled fine.
>
> One of the reasons I did crosstool was to avoid that kind of
> hackery.  With crosstool, you don't need to build gcc 2.95.3 just
> to build gcc 3.2.3.  Crosstool does clean builds from pristine,
> minimally patched source.
> - Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Cross-compile package combinations

[Wolfgang Denk]

In message <6F8DFFA2C996D711945800065BFC9E4A03B9910C@il02exm11> you wrote:
>
> I do have a another question, though.  Let's say that I want to use my own kernel instead of having crosstool download it.  What would be the proper set of steps to take to specify a local kernel?  My current kernel is 2.4.20 and I know that the combina

The steps are: download a kernel, unpack it, configure it, compile it, boot it.

Kernel and tools are more or less unrelated to each other.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I will also, for an appropriate fee, certify that  your  keyboard  is
object-oriented,  and  that  the bits on your hard disk are template-
compatible.            - Jeffrey S. Haemer in <411akr$3ga@cygnus.com>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Cross-compile package combinations

[Ashwin Bihari]

I have indeed tried a fairly recent version of GCC, the aforementioned 3.2.3
with Linux 2.4.23 and it works like a charm in our PPC environment. I didn't
bother with the 3.3.x release of GCC mainly because other toolchains used
for other stuff in our environment also used 3.2.3, so I wanted to stay in
lockstep with those versions.

~Ashwin




>From: "listmember@orkun.us" <listmember@orkun.us>
>To: linuxppc-embedded@lists.linuxppc.org
>CC: "Dan Kegel" <dank@kegel.com>
>Subject: Re: Cross-compile package combinations
>Date: Thu, 11 Dec 2003 10:06:40 -0600 (CST)
>
>
> >
> > Silverton Aron-C1710C wrote:
> >> Hello all,
> >>
> >> Can somebody give me a clue as to which versions of binutils, gcc, and
> >> glibc are compatible with each other?  I'd like to use gcc 3.2 or 3.3
> >> and I am developing on i386 targeting PowerPC.  I'll be using 2.4
> >> kernels initially and then moving to 2.6.
> >>
> >> If there is a known reference or recent previous post (I didn't see one
> >> in my initial search) I'd appreciate a pointer.
> >
> > As Ashwin mentioned, http://kegel.com/crosstool might come in handy.
> > See also the matrix at http://embeddedtux.org.
> > - Dan
>
>Funny, I was just about to ask  very similar question. I will be working
>an a IBM PPC405G based development board (Cogent CSB272) for an internal
>project. I would like to use as up-to-date versions of GCC, GLIBC and
>Linux 2.4 kernel as possible (without sacrificing stability).
>
>- Has anyone used recently released 2.4.23 (kernel.org) in any PPC project
>yet? If it is not good to use for PPC based development? Do I need to get
>a ppc specific modified kernel or do I need to apply any patches to linus
>2.4.23 kernel to get it working in PPC405 embedded environment.
>
>- Kernel 2.4.x README still says the official kernel compiler is gcc
>2.95.3. Is it still the case or using a more recent GCC compiler is now
>acceptable? In the last Linux embedded project I was in we had used this
>one along with a very early build of kernel. I was not the one to set the
>development environment so bear with me if these sound basic questions to
>you.
>
>- I built a toolchain using crosstools based on gcc 3.3.2, glibc 2.3.2 and
>binutils 2.14.90.0.5. Crosstools default .dat files pull kernel 2.4.21 but
>I also got the tools compiled using 2.4.23 sources. I have not tested them
>yet since I don't have the board yet? Any comments regarding this
>combination?
>
>Looking at some ppc linux distros (not necessarily embedded):
>
>YDL 3.0: kernel 2.4.20, gcc ? glibc 2.3.1, binutils ?
>Mandrake: kernel 2.3.21, gcc 3.2.2, glibc, 2.3.1, binutils ?
>Gentoo: kernel 2.4.22, gcc ? glibc 2.3.2?, binutils ?
>
>Tolunay
>
>

_________________________________________________________________
Tired of slow downloads and busy signals?  Get a high-speed Internet
connection! Comparison-shop your local high-speed providers here.
https://broadband.msn.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Silverton Aron-C1710C]

Ashwin Bihari <mailto:raz0redge@hotmail.com> wrote:
> Aron,
>
> I've recently done just this, same host and target. I used GCC
> 3.2.3 with GLIBC 2.3.2 w/ Linuxthreads and Binutils 2.14. This
> worked fine.
>
> Check out a package called "crosstools". It's a nice tool that
> will tell you about working combinations, actaully download these
> tarballs off the web, find any applicable patches, apply them,
> configure the tools for your host and target, build them and
> finally install it at your deisred location. All this from
> running a single SHELL file. This is what I did and it worked
> like a charm.
>
> I've currently used this toolchain to compile 2.4.x kernels,
> haven't tried
> 2.6.x.
>
> Contact me if you want any more details.
>
> ~Ashwin
>

Thank you, I will take a look.

Aron

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Cross-compile package combinations

[Ashwin Bihari]

Aron,

I've recently done just this, same host and target. I used GCC 3.2.3 with
GLIBC 2.3.2 w/ Linuxthreads and Binutils 2.14. This worked fine.

Check out a package called "crosstools". It's a nice tool that will tell you
about working combinations, actaully download these tarballs off the web,
find any applicable patches, apply them, configure the tools for your host
and target, build them and finally install it at your deisred location. All
this from running a single SHELL file. This is what I did and it worked like
a charm.

I've currently used this toolchain to compile 2.4.x kernels, haven't tried
2.6.x.

Contact me if you want any more details.

~Ashwin

_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Cross-compile package combinations

[Silverton Aron-C1710C]

Hello all,

Can somebody give me a clue as to which versions of binutils, gcc, and glibc are compatible with each other?  I'd like to use gcc 3.2 or 3.3 and I am developing on i386 targeting PowerPC.  I'll be using 2.4 kernels initially and then moving to 2.6.

If there is a known reference or recent previous post (I didn't see one in my initial search) I'd appreciate a pointer.

TIA,

Aron

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Cross-compile package combinations

[Dan Kegel]

Silverton Aron-C1710C wrote:
> Hello all,
>
> Can somebody give me a clue as to which versions of binutils, gcc, and glibc are compatible with each other?  I'd like to use gcc 3.2 or 3.3 and I am developing on i386 targeting PowerPC.  I'll be using 2.4 kernels initially and then moving to 2.6.
>
> If there is a known reference or recent previous post (I didn't see one in my initial search) I'd appreciate a pointer.

As Ashwin mentioned, http://kegel.com/crosstool might come in handy.
See also the matrix at http://embeddedtux.org.
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Cross-compile package combinations

[listmember]

>
> Silverton Aron-C1710C wrote:
>> Hello all,
>>
>> Can somebody give me a clue as to which versions of binutils, gcc, and
>> glibc are compatible with each other?  I'd like to use gcc 3.2 or 3.3
>> and I am developing on i386 targeting PowerPC.  I'll be using 2.4
>> kernels initially and then moving to 2.6.
>>
>> If there is a known reference or recent previous post (I didn't see one
>> in my initial search) I'd appreciate a pointer.
>
> As Ashwin mentioned, http://kegel.com/crosstool might come in handy.
> See also the matrix at http://embeddedtux.org.
> - Dan

Funny, I was just about to ask  very similar question. I will be working
an a IBM PPC405G based development board (Cogent CSB272) for an internal
project. I would like to use as up-to-date versions of GCC, GLIBC and
Linux 2.4 kernel as possible (without sacrificing stability).

- Has anyone used recently released 2.4.23 (kernel.org) in any PPC project
yet? If it is not good to use for PPC based development? Do I need to get
a ppc specific modified kernel or do I need to apply any patches to linus
2.4.23 kernel to get it working in PPC405 embedded environment.

- Kernel 2.4.x README still says the official kernel compiler is gcc
2.95.3. Is it still the case or using a more recent GCC compiler is now
acceptable? In the last Linux embedded project I was in we had used this
one along with a very early build of kernel. I was not the one to set the
development environment so bear with me if these sound basic questions to
you.

- I built a toolchain using crosstools based on gcc 3.3.2, glibc 2.3.2 and
binutils 2.14.90.0.5. Crosstools default .dat files pull kernel 2.4.21 but
I also got the tools compiled using 2.4.23 sources. I have not tested them
yet since I don't have the board yet? Any comments regarding this
combination?

Looking at some ppc linux distros (not necessarily embedded):

YDL 3.0: kernel 2.4.20, gcc ? glibc 2.3.1, binutils ?
Mandrake: kernel 2.3.21, gcc 3.2.2, glibc, 2.3.1, binutils ?
Gentoo: kernel 2.4.22, gcc ? glibc 2.3.2?, binutils ?

Tolunay

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/