Re: crosstool-0.41 released; gcc-4.1.0-rc2 support, tls support, ld performance

[Matthew J Fletcher <mfletcher at serck-controls dot co dot uk>]

Hi

Noticing gcc 4.1.0 final hitting the mirrors, i tried to use my 'crossgcc 
based but using newlib' script to build 4.1.0. I currently use the same 
script for 3.4.x and 4.0.x builds successfully.

-- output snip --
checking for ISO C99 support in <stdio.h>... yes
checking for ISO C99 support in <stdlib.h>... no
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for ISO C99 support in <wchar.h>... no
checking for fully enabled ISO C99 support... no
checking for enabled long long specializations... yes
checking for enabled wchar_t specializations... yes
configure: Debug build flags set to -g3 -O0
checking for additional debug build... no
checking for extra compiler flags for building...
checking for thread model used by GCC... rtems
checking for shared libgcc... configure: error: Link tests are not allowed 
after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
-- snip --

and got this error,.. in the final gcc build (not the one that builds to build 
newlib),  i looked in the libstdc++ configure file and noticed that 
GCC_NO_EXECUTABLES was being set when a non-native (i.e cross) toolchain was 
being built.

what i don't understand is why libstdc++ is not honouring this flag, indeed i 
issue '--disable-shared' to my 'final' gcc build, so i would expect the check 
for a shared libgcc to return fairly quickly.

-- my script - snip --
    ${GCC_DIR}/configure --target=$TARGET --host=$HOST --prefix=$PREFIX \
        ${GCC_EXTRA_CONFIG} \
	--with-headers=${PREFIX}/${TARGET}/include \
	--disable-nls \
	--with-newlib \
	--enable-symvers=gnu \
	--enable-languages=c,c++ \
	--disable-shared \
	--enable-long-long \
	--enable-c99 \
	--enable-threads=rtems \
	--enable-libstdcxx-pch=no \
	--with-gnu-as \
	--with-gnu-ld
-- snip --

the libstdc++ configure says

-- snip --
  # Check to see if libgcc_s exists, indicating that shared libgcc is 
possible.
  echo "$as_me:$LINENO: checking for shared libgcc" >&5
echo $ECHO_N "checking for shared libgcc... $ECHO_C" >&6
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=' -lgcc_s'
  if test x$gcc_no_link = xyes; then
  { { echo "$as_me:$LINENO: error: Link tests are not allowed after 
GCC_NO_EXECUTABLES." >&5
echo "$as_me: error: Link tests are not allowed after GCC_NO_EXECUTABLES." 
>&2;}
   { (exit 1); exit 1; }; }
-- end --

a quick grep reveals that no 'libgcc_s' file exits in my build or install 
directory's.

any ideas ?


regards
---
Matthew J Fletcher
Embedded Software
Serck Controls Ltd
---
**********************************************************************
Serck Controls Ltd, Rowley Drive, Coventry, CV3 4FH, UK
Tel: +44 (0) 24 7630 5050   Fax: +44 (0) 24 7630 2437
Web: www.serck-controls.com  Admin: post@serck-controls.co.uk
A subsidiary of Serck Controls Pty. Ltd. Reg. in England No. 4353634
**********************************************************************
This email and files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they 
are addressed. If you have received this email in error please notify 
the above. Any views or opinions presented are those of the author 
and do not necessarily represent those of Serck Controls Ltd. 


This message has been checked by MessageLabs
******************************************************************

--
For unsubscribe information see http://sourceware.org/lists.html#faq