should i be *able* to build a non-thread toolchain?

["Robert P. J. Day" <rpjday at mindspring dot com>]

  as part of testing my toolchain build script, i wanted to see if i
could build a toolchain with no thread support at all -- you'd think
this should be possible.  so at each step during the toolchain
construction, i had configure and build options saying things like no
threads, disable threads, no tls, threads can just bite me and so on
and so on.

  everything went well until the step of configuring and building
glibc (after the bootstrap gcc phase), where the configure step choked
as follows:

====================================================================
...
make  -C assert subdir_lib
make[2]: Entering directory `/home/rpjday/unpack/glibc-2.3.6/assert'
.././scripts/mkinstalldirs
/home/rpjday/results/sh3eb/build/build-glibc/assert
mkdir /home/rpjday/results/sh3eb/build/build-glibc/assert
sh3eb-unknown-linux-gnu-gcc  assert.c -c -std=gnu99 -O -Wall -Winline
-Wstrict-prototypes -Wwrite-strings -m3 -mb
-DFATAL_PREPARE_INCLUDE='<fatal-prepare.h>'   -I../include -I.
-I/home/rpjday/results/sh3eb/build/build-glibc/assert -I.. -I../libio
-I/home/rpjday/results/sh3eb/build/build-glibc -I../sysdeps/sh/elf
-I../sysdeps/unix/sysv/linux/sh/sh3 -I../sysdeps/unix/sysv/linux/sh
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/sh -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/sh/sh3 -I../sysdeps/sh -I../sysdeps/wordsize-32
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64
-I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic
-nostdinc -isystem
/home/rpjday/results/sh3eb/build/gcc-core-prefix/lib/gcc/sh3eb-unknown-linux-gnu/4.0.2/include
-isystem
/home/rpjday/results/sh3eb/tools/sh3eb-unknown-linux-gnu/sys-root/usr/include
-include ../include/libc-symbols.h       -o
/home/rpjday/results/sh3eb/build/build-glibc/assert/assert.o -MD -MP
-MF /home/rpjday/results/sh3eb/build/build-glibc/assert/assert.o.dt
-MT /home/rpjday/results/sh3eb/build/build-glibc/assert/assert.o
In file included from ../sysdeps/unix/sysv/linux/fatal-prepare.h:19,
                 from assert.c:42:
../include/pthread.h:1:26: error: pthread.h: No such file or directory
assert.c: In function '__assert_fail':
assert.c:53: error: 'pthread_setcancelstate' undeclared (first use in
this function)
assert.c:53: error: (Each undeclared identifier is reported only once
assert.c:53: error: for each function it appears in.)
assert.c:53: warning: implicit declaration of function
'pthread_setcancelstate'
assert.c:53: error: 'PTHREAD_CANCEL_DISABLE' undeclared (first use in
this function)
make[2]: ***
[/home/rpjday/results/sh3eb/build/build-glibc/assert/assert.o] Error 1
make[2]: Leaving directory `/home/rpjday/unpack/glibc-2.3.6/assert'
make[1]: *** [assert/subdir_lib] Error 2
make[1]: Leaving directory `/home/rpjday/unpack/glibc-2.3.6'
make: *** [lib] Error 2
...
======================================================================

  shouldn't i be allowed to configure a toolchain with no thread
support at all?


rday




------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com