Re: Problems building dosfstools - include headers wrong?

[Daniel Kegel <dank at kegel dot com>]

Steven Scholz wrote:
> I just built an arm-softfloat-linux-gnu toolchain with crosstool-0.34 using
>
> export TARGET_CFLAGS="-O"
> export GCC_EXTRA_CONFIG="--with-float=soft"
> export GLIBC_EXTRA_CONFIG="--without-fp"
> export BINUTILS_DIR=binutils-2.15
> export GCC_DIR=gcc-3.3.3
> export GLIBC_DIR=glibc-2.3.3
> export LINUX_DIR=linux-2.6.12-rc4
>
> Now I am trying to build mkdosfs from the dosfstool-2.11 package. But I get
>
> # ~> make CC=arm-softfloat-linux-gnu-gcc
> arm-softfloat-linux-gnu-gcc  -c mkdosfs.c -o mkdosfs.o
> In file included from 
> /opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.3-linux-2.6.10/arm-softfloat-linux-gnu/sys-include/linux/fs.h:19, 
>
>                  from mkdosfs.c:54:
> /opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.3-linux-2.6.10/arm-softfloat-linux-gnu/sys-include/linux/prio_tree.h:22: 
> error: parse error before "pgoff_t"

You're not the first to run into this; see
http://mail.gnome.org/archives/garnome-list/2005-February/msg00072.html
which didn't even involve crosstools.

> Passing a kernel header include path
>
> make CC=arm-softfloat-linux-gnu-gcc CFLAGS=-I<PATH_TO_2.6.12-rc4>/include
>
> fixes that.
>
> So could it be that there is a problem with sys-include/linux/fs.h?

Hrm.    My understanding was that sys-include was copied from include
and then 'fixed' by gcc's fixincludes step (http://autogen.sourceforge.net/fixinc.html)
which does things like make C header files includable from C++.
So while there might be problems with it, I don't think we want to give up on it.

How about trying the sanitized kernel headers?  They're there to
solve exactly this kind of problem.  Just add
export LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.11.2
and rebuild crosstool, and let us know what happens.

I haven't tried these with gcc-3.3, nor have I gotten to work yet with arm,
but at most there should be a small amount of futzing needed (e.g. adding
a symlink or two; this will be done eventually in crosstool.sh if needed).
- Dan

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