Problem with GCC 4.5.0 and canadian cross compilation
Sebastian Huber
sebastian.huber at embedded-brains.de
Tue Apr 13 13:49:37 UTC 2010
Hi,
I had problems building GCC 4.5.0 under MinGW/MSYS, so I tried to build the
cross compiler for the Windows host with a Linux build machine. The Windows
cross compiler is:
i686-w64-mingw32-gcc (GCC) 4.4.4 20100409 (prerelease)
For the RTEMS tools I use the sources provided by the RPM:
rtems-4.11-arm-rtems4.11-gcc-4.5.0-7.suse11.2.src.rpm
The GCC configure command is:
"$SRCDIR/configure" \
--prefix=/opt/rtems-4.10-custom \
--target=arm-rtems4.10 \
--host=i686-w64-mingw32 \
--verbose \
--with-gnu-as \
--with-gnu-ld \
--with-newlib \
--disable-libstdcxx-pch \
--disable-nls \
--without-included-gettext \
--disable-win32-registry \
--enable-version-specific-runtime-libs \
--enable-threads \
--enable-newlib-io-c99-formats \
--enable-languages="c,c++" \
--enable-cxx-flags='-fno-exceptions'
The build process works fine and I can use the result to some extend under
Windows, but there is a problem with the multilib installation. It seems that
it built all multilib components, e.g.
find -name libc.a
./arm-rtems4.10/thumb/vfp/newlib/libc/libc.a
./arm-rtems4.10/thumb/vfp/newlib/libc.a
./arm-rtems4.10/thumb/newlib/libc/libc.a
./arm-rtems4.10/thumb/newlib/libc.a
./arm-rtems4.10/vfp/newlib/libc/libc.a
./arm-rtems4.10/vfp/newlib/libc.a
./arm-rtems4.10/softfp/vfp/newlib/libc/libc.a
./arm-rtems4.10/softfp/vfp/newlib/libc.a
./arm-rtems4.10/fpu/newlib/libc/libc.a
./arm-rtems4.10/fpu/newlib/libc.a
./arm-rtems4.10/newlib/libc/libc.a
./arm-rtems4.10/newlib/libc.a
find -name libgcc.a
./arm-rtems4.10/thumb/libgcc/libgcc.a
./arm-rtems4.10/thumb/vfp/libgcc/libgcc.a
./arm-rtems4.10/libgcc/libgcc.a
./arm-rtems4.10/vfp/libgcc/libgcc.a
./arm-rtems4.10/softfp/vfp/libgcc/libgcc.a
./arm-rtems4.10/fpu/libgcc/libgcc.a
./gcc/thumb/vfp/libgcc.a
./gcc/thumb/libgcc.a
./gcc/vfp/libgcc.a
./gcc/softfp/vfp/libgcc.a
./gcc/fpu/libgcc.a
./gcc/libgcc.a
But a 'make DESTDIR=XXX install' installs only some of them and some also into
strange directories:
find -name libc.a
./opt/rtems-4.10-custom/arm-rtems4.10/lib/thumb/libc.a
./opt/rtems-4.10-custom/arm-rtems4.10/lib/libc.a
./opt/rtems-4.10-custom/arm-rtems4.10/lib/fpu/libc.a
find -name libgcc.a
./opt/rtems-4.10-custom/lib/gcc/arm-rtems4.10/4.4.3/thumb/libgcc.a
./opt/rtems-4.10-custom/lib/gcc/arm-rtems4.10/4.4.3/fpu/libgcc.a
./opt/rtems-4.10-custom/lib/gcc/arm-rtems4.10/4.4.3/libgcc.a
The standard MinGW tool chain from:
ftp://www.rtems.com/pub/rtems/mingw32/4.11
does not seem to have this problem. Can someone give me a hint? Which cross
compiler for Windows was used for the standard MinGW tool chain?
Have a nice day!
--
Sebastian Huber, embedded brains GmbH
Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone : +49 89 18 90 80 79-6
Fax : +49 89 18 90 80 79-9
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users
mailing list