Actions

icon Post
text/html Subscribe
text/html Unsubscribe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [arm-gnu] Re.[arm-gnu] problem during building of gcc as cross compiler


  • To: <arm-gnu@xxxxxxxxxxxxxxxx>
  • Subject: RE: [arm-gnu] Re.[arm-gnu] problem during building of gcc as cross compiler
  • From: "Pradip Singh" <pradip.singh@xxxxxxxxxxxxxxx>
  • Date: Wed, 29 Sep 2004 11:57:56 +0530

hi paul,

  Thanks for ur sugestion.

  I would like to ask one thing. Does gcc 3.4.0 have support for arm1022e. We are using the kernel version 2.6.8.1 and gcc 3.4.2. I think the linux kernel version which i am using does provide support for arm1022e. but i doubt the gcc version which i am using. So does GCC 3.4.2 provide support for arm1022e.

thanks and regards,
Pradip

-----Original Message-----
From: Paul Brook [mailto:paul@xxxxxxxxxxxxxxxx]
Sent: Tuesday, September 28, 2004 8:31 PM
To: arm-gnu@xxxxxxxxxxxxxxxx
Cc: Pradip Singh
Subject: Re: [arm-gnu] Re.[arm-gnu] problem during building of gcc as
cross compiler


On Tuesday 28 September 2004 04:42, Pradip Singh wrote:
> Hi Paul,
>
>   Thanks for ur prompt reply.
>
>    I understand that gcc depend on glibc to build its support libraries.
> But during building of gcc can we not disable those features which requires
> these support libraries? If we can then what we have to do? Also once the
> gcc is build without those support libraries then we can build glibc and
> get the headers. After glibc is built then we can again build gcc with
> support libraries. So i was looking for a way to disable those support
> libraries for gcc. If at all it is possible plz tell me how?

In theory it's possible to do what you suggest, but in practice it doesn't 
usually work. I have managed to bootstrap an armlinux toolchain this way, but 
it wasn't easy. I think I did "make; make -k install" for gcc, "make 
install-headers; make; make -k install" for glibc, then manually created some 
missing headers, and iterated round a few times until I had something that 
worked.

I highly recommend simply using the target header files from an existing 
arm-linux setup. Either compy these from /usr/include on an arm-linux system, 
or the prebuilt compiler packages from 
http://www.arm.com/linux/prebuilt_download.html include the necessary files.

Once you have the initial compiler built with these header files you can then 
build and install your new glibc, and start using that.

You may also want to look at the the crosstool build scripts:
http://kegel.com/crosstool/

Paul