This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
here's one example of what i've found related to the necessity of having to install the glibc header files, at least for a specific architecture. if i try to build a toolchain for sh3 *without* installing the glibc header files, the build of the bootstrap gcc fails with: /home/rpjday/results/sh3/build/build-gcc-core/./gcc/xgcc -B/home/rpjday/results/sh3/build/build-gcc-core/./gcc/ -B/home/rpjday/results/sh3/build/gcc-core-prefix/sh3-unknown-linux-gnu/bin/ -B/home/rpjday/results/sh3/build/gcc-core-prefix/sh3-unknown-linux-gnu/lib/ -isystem /home/rpjday/results/sh3/build/gcc-core-prefix/sh3-unknown-linux-gnu/include -isystem /home/rpjday/results/sh3/build/gcc-core-prefix/sh3-unknown-linux-gnu/sys-include -O2 -O2 -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -DNO_FPSCR_VALUES -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I/home/rpjday/unpack/gcc-4.1-20051029/gcc -I/home/rpjday/unpack/gcc-4.1-20051029/gcc/. -I/home/rpjday/unpack/gcc-4.1-20051029/gcc/../include -I/home/rpjday/unpack/gcc-4.1-20051029/gcc/../libcpp/include -fexceptions -c /home/rpjday/unpack/gcc-4.1-20051029/gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o In file included from /home/rpjday/unpack/gcc-4.1-20051029/gcc/unwind-dw2.c:256: /home/rpjday/unpack/gcc-4.1-20051029/gcc/config/sh/linux-unwind.h:32:20: error: signal.h: No such file or directory /home/rpjday/unpack/gcc-4.1-20051029/gcc/config/sh/linux-unwind.h:33:26: error: sys/ucontext.h: No such file or directory sure enough, the file gcc-4.1-.../gcc/config/sh/linux-unwind.h contains the include directive: #include <sys/ucontext.h> if i do a "find" for files named "ucontext.h" under the sys-root directory, all i find is: ./sys-root/usr/include/asm/ucontext.h so it's not surprising that that header file can't be found. if, however, i install the glibc header files under sys-root, that would fix the problem as the sys-root directory would now contain: ./sys-root/usr/include/sys/ucontext.h ./sys-root/usr/include/ucontext.h ./sys-root/usr/include/asm/ucontext.h is this what bill was talking about when he meant whether gcc was "bootstrappable"? clearly, at least in this instance, i *need* to install the glibc header files. or am i misunderstanding something here? rday p.s. a better question to ask might be, in a perfect world, where would a build of the bootstrap gcc need to look to find all of its header files? ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |