steps in building a toolchain with NPTL: glibc-headers

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

  don't want to sound like i'm beating this to death, but i really
would like to nail the recipe for building a toolchain with NPTL
instead of linuxthreads, if it's even possible for SH3 which is what
i'm trying.

  based on my reading, the first thing to clarify is that the first
two steps in the crosstool process:

  - kernel headers
  - binutils

are entirely independent of the threading to be selected so nothing
changes in either of those two stages.  beyond this step, i'm working
off of the patches found in the contributed patch file:

	contrib/2005b/crosstool-0.38-nptl-schaefer.patch

for the glibc headers step, we have the patch:

+if test '!' -z "${GLIBC_ADDON_NPTL}"; then
+    GLIBC_EXTRA_CONFIG="--with-tls --with-__thread ${GLIBC_EXTRA_CONFIG}"
+    GLIBC_MIN_KERNEL=2.6.4
+else
+    GLIBC_EXTRA_CONFIG="--without-tls --without-__thread ${GLIBC_EXTRA_CONFIG}"
+    GLIBC_MIN_KERNEL=2.4.3
+fi

  so we need to add the configure options:

	--with-tls
	--with-__thread

*however*, as i posted earlier, there is a definite problem if you try
to use the "--enable-kernel" option with 2.6.0, and note above that
it's going to be set to 2.6.4 later in the script.

  i'm not sure what's going to happen when i get there, but i'll just
do this glibc headers step for now and worry about the rest when the
time comes.

  any comments on the above?

rday



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