Stef Bon wrote: > > So basically, you're saying start all over again! Or only gcc and > binutils (chapters 8.14 and 8.15)? > Yes. You can optionally rebuild /cross-tools and /tools from your host system. Then recompile binutils in your final system. Basically just satisfying the /tools/lib/ld.so dependency to run the ld in your final system. > Well, ok. > But the specs of gcc, with gcc -dumpspecs, shows nothing of /tools or > /cross/tools, the ld-2.5.1.so is located at /lib, and the > startfile_prefix_spec is/are empty. > yea, as expected. The compiler you built in chapter 10 is correct, which is why every package built after it is fine. It's the packages built before that that will have a problem. And in the case of the build in the book. That's just binutils. When the toolchain adjustment is done in chapter 10, the compiler in /tools is told to link to /lib/ld-linux.so.2 instead. > So how come?? Ok, I, already see, it's build again in 8.15. That > explains it. > See explanation above. I don't know why you're looking in chapter 8 for an answer. You wont find it by looking at any of that. Jump 2 forward to 10. > Futher I would like to know is there still some interest in automating > the build. I'm thinking of a system which uses something like pkgtool > and another tool to download the instructions (and packages) from the > clfs website. User has choice to build manually or getting and > following the instructions from the book, and letting the tool do > pieces of the book without userinvention. Not interested in supporting regular users using automation. Use gentoo.
Easiest option, restart from scratch. _______________________________________________ Clfs-support mailing list Clfs-support@lists.cross-lfs.org http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
