Actions

icon Post
text/html Subscribe
text/html Unsubscribe

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

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


  • To: <arm-gnu@xxxxxxxxxxxxxxxx>
  • Subject: Re.[arm-gnu] problem during building of gcc as cross compiler
  • From: "Pradip Singh" <pradip.singh@xxxxxxxxxxxxxxx>
  • Date: Tue, 28 Sep 2004 09:12:54 +0530

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?

thanks and regards,
Pradip


On Monday 27 September 2004 14:21, Pradip Singh wrote:
> Hi all,
>
>   I am building the gcc 3.4.0 as a cross compiler for arm target. i am
> giving the target as arm-linux during configuring the compiler.
>
>   i,e ./configure --target=arm-linux --prefix=/usr/arm_tools
> --with-headers=/usr/arm_tools/linux/include --enable-languages=c
> --disable-threads
>
>
>   when i am giving a make command i am getting the following compilation
> error
>
>
>  In file include from ./crtstuff.c:62:
>
>  ./tsystem.h:79:19  stdio.h No such file or directory
>  ./tsystem.h:82:23  sys/types.h No such file or directory
>  ./tsystem.h:85:19  errno.h No such file or directory
>  ./tsystem.h:92:20  string.h No such file or directory
>  ./tsystem.h:93:19  stdlib.h No such file or directory
>  ./tsystem.h:94:19  unistd.h No such file or directory
>  ./tsystem.h:100:18  time.h No such file or directory
>
> This is the first time I am building this cross compiler.
>
> Also I have build and installed the binutils at appropriate place.

You need arm-linux userspace/glibc headers so that gcc can build it's support 
libraries.

The easiest way to get these is to copy them from an existing arm-linux 
system, and configure gcc with --with-sysroot=.

In theory you can get these by building glibc. However this depends on having 
a working compiler, which in turn depends on having glibc ... It usually 
takes some manual intervention and judicious installation of half-built 
packages to get this to work.

Paul