I did this in order to build gcc, libgcc and libstdc++ independently.

when I do the simple integrated build process (following 
http://gcc.gnu.org/install)  :

cd $(GCC_OBJDIR); CFLAGS="-g -O0" $(GCC_SRCDIR)/configure 
        -quiet 
        --prefix=$(INSTALLDIR) 
        --target=$(TARGET) 
        --enable-languages=c,c++,ada 
        --disable-nls 
        --disable-decimal-float 
        --disable-fixed-point 
        --disable-libmudflap 
        --disable-libffi 
        --disable-libssp 
        --disable-shared 
        --disable-threads 
        --without-headers
        --disable-libada 
        --enable-version-specific-runtime-lib 
        --disable-bootstrap
        --enable-checking=release
make -C $(GCC_OBJDIR)



I encounter a problem on libstdc++v3 :

Configuring in prism/libstdc++-v3
Configuring in prism/libiberty
configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
make[2]: *** [configure-target-libiberty] Error 1
make[2]: *** Waiting for unfinished jobs....
configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
make[2]: *** [configure-target-libstdc++-v3] Error 1
make[1]: *** [all] Error 2
make: *** [gcc_make] Error 2

because stdio.h is not found  (my libc is externally built and --without-header 
prevent gcc from knowing where are these headers)



I tried --with-headers with my own libc header files (incomplete home made 
libc)  but this time I found stuck on libgcc2 requiring unistd.h that I don't 
have (or want) :

In file included from 
/vues_statiques/FPGA/belbachir/prism2/MPUCores/tools/gcc-4.5.2/libgcc/../gcc/libgcc2.c:29:0:
/vues_statiques/FPGA/belbachir/prism2/MPUCores/tools/gcc-4.5.2/libgcc/../gcc/tsystem.h:102:20:
 fatal error: unistd.h: No such file or directory
compilation terminated.



So, to build libgcc I would need --without-header to compensate for my small 
libc, and to build libstdc++ I would have to use --with-header in order to 
provide stdio.h ...


Do you know a better way to solve that than building gcc, libgcc & libstdc++ 
independently ?


Reply via email to