unwind problem when cross compiling

unwind problem when cross compiling

[Luo Yong]

Hi all

I'm trying to build an cross compiling environment on my i386 PC
following the follow steps:

===>

Binutils
./configure --target=arm-gnu-linux
make
make install

Bootstrap GCC
mkdir _build_
cd _build_
../gcc-4.1.1/configure --host=i686-pc-linux-gnu
--build=i686-pc-linux-gnu --target=arm-gnu-linux --disable-shared
--disable-threads --enable-languages=c --with-newlib --with-gnu-as
--with-gnu-ld --without-headers
make all-gcc
make install-gcc

Glibc
mkdir _build_
cd _build_
CC=arm-gnu-linux-gcc ../glibc-2.3.6/configure --host=arm-gnu-linux
--target=arm-gnu-linux --enable-add-ons
--with-headers=/usr/local/arm-gnu-linux/include
--prefix=/usr/local/arm-gnu-linux --disable-shared --disable-check-abi
--without-tls

<===


But there's  an  error occured:
checking for forced unwind support ... no
configure: error: forced unwind support is required

I only have an bootstrap gcc so I can't build the libunwind library.

How can I solve this problem?

Thanks.

Re: unwind problem when cross compiling

[Kai Ruottu]

Luo Yong wrote:

 > I'm trying to build an cross compiling environment on my i386 PC
 > ../configure --target=arm-gnu-linux
 >  I only have an bootstrap gcc so I can't build the libunwind library.
 > How can I solve this problem?

 Please just check your "attitude problem" and don't start from scratch!

 A GCC build (native or cross) requires an existing ("suitable") C library
for the target, in order to get 'libgcc', 'libiberty', 'libstdc++-v3', 
'libssp'
etc. extra target libraries being built for the target and being in sync 
with
the C library...  Producing glibc may require this kind of "complete"
GCC...  So why to fight against  the windmills when many others don't?

 So please download a prebuilt glibc for Linux/ARM, then produce your
"complete" cross GCC with it, then use it to compile your own glibc
and replace the downloaded "bootstrap" glibc with it.  And if being
suspicious, reproduce the GCC and the extra target libraries to be in sync
with your self-built glibc, and maybe reproduce the glibc and check that
the result is identical with the first build...   Then be happy and continue
with producing your own Linux/ARM system!

 The crosstoolchain build is only the beginning in your job, so why to use
too much time in it?  Or toy with non-working "stripped and non-complete"
tools?