Hello,
I downloaded hlfs and started the build process of the development environment. I made one change to the build process, instead of using /tools and the install point, I am using my own directory /home/hamilton/uclibc-tools. I am building on a slackware-9.0 based ix86 system. I can send you the script I am using to build the tools. It goes as far as I got in the build process.
When I try building gcc for the first time (chapter05/05-gcc-cross.txt), the make fails with the following error:
rm -rf libbackend.a
ar rc libbackend.a alias.o bb-reorder.o bitmap.o builtins.o caller-save.o calls.o cfg.o cfganal.o cfgbuild.o cfgcleanup.o cfglayout.o cfgloop.o cfg
loopanal.o cfgloopmanip.o loop-init.o loop-unswitch.o loop-unroll.o cfgrtl.o combine.o conflict.o convert.o coverage.o cse.o cselib.o dbxout.o debu
g.o df.o diagnostic.o dojump.o doloop.o dominance.o dwarf2asm.o dwarf2out.o emit-rtl.o except.o explow.o expmed.o expr.o final.o flow.o fold-const.
o function.o gcse.o genrtl.o ggc-common.o global.o graph.o gtype-desc.o haifa-sched.o hooks.o ifcvt.o insn-attrtab.o insn-emit.o insn-modes.o insn-
extract.o insn-opinit.o insn-output.o insn-peep.o insn-recog.o integrate.o intl.o jump.o langhooks.o lcm.o lists.o local-alloc.o loop.o optabs.o o
ptions.o opts.o params.o postreload.o predict.o print-rtl.o print-tree.o value-prof.o profile.o ra.o ra-build.o ra-colorize.o ra-debug.o ra-rewrite
.o real.o recog.o reg-stack.o regclass.o regmove.o regrename.o reload.o reload1.o reorg.o resource.o rtl.o rtlanal.o rtl-error.o sbitmap.o sched-de
ps.o sched-ebb.o sched-rgn.o sched-vis.o sdbout.o sibcall.o simplify-rtx.o sreal.o stmt.o stor-layout.o stringpool.o targhooks.o timevar.o toplev.o
tracer.o tree.o tree-dump.o unroll.o varasm.o varray.o version.o vmsdbgout.o xcoffout.o alloc-pool.o et-forest.o cfghooks.o bt-load.o pretty-print
.o ggc-page.o web.o i386.o host-default.o hashtable.o tree-inline.o tree-optimize.o cgraph.o cgraphunit.o
ranlib libbackend.a
gcc -DUSE_UCLIBC -DNOSTDINC -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long
-long -DHAVE_CONFIG_H -o cc1 \
c-parse.o c-lang.o c-pretty-print.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-comm
on.o c-opts.o c-format.o c-semantics.o c-incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-objc-common.o c-dump.o c-pch.o libcpp.a mai
n.o libbackend.a ../libiberty/libiberty.a c-cppbuiltin.o(.text+0xa83): In function `c_cpp_builtins':
/home/hamilton/server_tools/hlfs-0.2/source/gcc_build/gcc/../../gcc-3.4.3/gcc/c-cppbuiltin.c:418: undefined reference to `LINUX_TARGET_OS_CPP_BUILT
INS'
collect2: ld returned 1 exit status
make[1]: *** [cc1] Error 1
make[1]: Leaving directory `/home/hamilton/server_tools/hlfs-0.2/source/gcc_build/gcc'
make: *** [all-gcc] Error 2
/bin/sh ../gcc-3.4.3/mkinstalldirs //home/hamilton//uclibc-tools/ //home/hamilton//uclibc-tools/
make[1]: Entering directory `/home/hamilton/server_tools/hlfs-0.2/source/gcc_build/gcc'
gcc -DUSE_UCLIBC -DNOSTDINC -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long
-long -DHAVE_CONFIG_H -o cc1 \
c-parse.o c-lang.o c-pretty-print.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-comm
on.o c-opts.o c-format.o c-semantics.o c-incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-objc-common.o c-dump.o c-pch.o libcpp.a mai
n.o libbackend.a ../libiberty/libiberty.a c-cppbuiltin.o(.text+0xa83): In function `c_cpp_builtins':
/home/hamilton/server_tools/hlfs-0.2/source/gcc_build/gcc/../../gcc-3.4.3/gcc/c-cppbuiltin.c:418: undefined reference to `LINUX_TARGET_OS_CPP_BUILT
INS'
collect2: ld returned 1 exit status
make[1]: *** [cc1] Error 1
make[1]: Leaving directory `/home/hamilton/server_tools/hlfs-0.2/source/gcc_build/gcc'
make: *** [install-gcc] Error 2



Do you have any suggestions? Kendrick Hamilton

--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to