On Fri, Jan 18, 2008 at 02:10:28PM +0000, b-vol wrote: > On Thursday 17 January 2008 06:27:41 pm Ken Moffat wrote: > > > > If I can quote from your posting yesterday: > > |############7.13. Lilo-22.8 install > > | > > |AS86 version 0.16.10 or later is required > > |as86 is not present > > | > > |LD86 version 0.16.10 or later is required > > |ld86 is not present > > | > > > > You made me start to question whether this version of the book had > > become broken, so I looked at the patch for lilo, and it hardcodes > > the prefix as x86_64-unknown-linux-gnu which matches the value shown > > in section 5.4. > > > > If I try to build lilo on he ppc I'm currently using, > > unsurprisingly it fails to boot, but my messages are a little > > different from yours: > > [EMAIL PROTECTED] ~/lilo-22.8 $make lilo.static > > ./checkit > > GCC version 2.91 or later is required > > gcc version 4.2.2 > > OKAY > > > > AS86 version 0.16.10 or later is required > > x86_64-unknown-linux-gnu-as86 is not present > > > > LD86 version 0.16.10 or later is required > > x86_64-unknown-linux-gnu-ld86 is not present > > [...] > > So it's clear that you didn't apply the patch. > > root:/home/clfs# cd '/mnt/clfs/cross-tools/bin' > root:/mnt/clfs/cross-tools/bin# > root:/mnt/clfs/cross-tools/bin# > root:/mnt/clfs/cross-tools/bin# rm as86 > rm: remove symbolic link `as86'? yes > root:/mnt/clfs/cross-tools/bin# > root:/mnt/clfs/cross-tools/bin# rm ld86 > rm: remove symbolic link `ld86'? yes > root:/mnt/clfs/cross-tools/bin# > root:/mnt/clfs/cross-tools/bin# > root:/mnt/clfs/cross-tools/bin# cd '/mnt/clfs/sources-clfsX64Jn08' > root:/mnt/clfs/sources-clfsX64Jn08# tar xzvf lilo-22.8.src.tar.gz > lilo-22.8/README > lilo-22.8/README.bitmaps > lilo-22.8/README.common.problems > lilo-22.8/README.disk > lilo-22.8/README.nokeyboard > lilo-22.8/README.pseudo > lilo-22.8/README.raid1 > lilo-22.8/README.volumeID > lilo-22.8/INCOMPAT > lilo-22.8/CHANGES > lilo-22.8/COPYING > lilo-22.8/COPYRIGHT > lilo-22.8/QuickInst > lilo-22.8/lilo.lsm > lilo-22.8/checkit > lilo-22.8/Makefile > lilo-22.8/bdata.h > lilo-22.8/bitmap.h > lilo-22.8/boot.h > lilo-22.8/bsect.h > lilo-22.8/cfg.h > lilo-22.8/common.h > lilo-22.8/config.h > lilo-22.8/device.h > lilo-22.8/edit.h > lilo-22.8/geometry.h > lilo-22.8/identify.h > lilo-22.8/lilo.h > lilo-22.8/loader.h > lilo-22.8/map.h > lilo-22.8/md-int.h > lilo-22.8/partition.h > lilo-22.8/probe.h > lilo-22.8/raid.h > lilo-22.8/shs2.h > lilo-22.8/temp.h > lilo-22.8/version.h > lilo-22.8/vesainfo.h > lilo-22.8/activate.c > lilo-22.8/boot.c > lilo-22.8/bsect.c > lilo-22.8/cfg.c > lilo-22.8/common.c > lilo-22.8/device.c > lilo-22.8/edit.c > lilo-22.8/geometry.c > lilo-22.8/identify.c > lilo-22.8/lilo.c > lilo-22.8/map.c > lilo-22.8/partition.c > lilo-22.8/probe.c > lilo-22.8/raid.c > lilo-22.8/shs2.c > lilo-22.8/temp.c > lilo-22.8/biosdata.S > lilo-22.8/bitmap.S > lilo-22.8/bootsect.S > lilo-22.8/chain.S > lilo-22.8/crt.S > lilo-22.8/disk.S > lilo-22.8/display4.S > lilo-22.8/dparam.S > lilo-22.8/dump.S > lilo-22.8/first.S > lilo-22.8/graph.S > lilo-22.8/mapper.S > lilo-22.8/mbr.S > lilo-22.8/menu.S > lilo-22.8/pseudo.S > lilo-22.8/read.S > lilo-22.8/second.S > lilo-22.8/shs3.S > lilo-22.8/strlen.S > lilo-22.8/volume.S > lilo-22.8/mkbdist > lilo-22.8/mksdist > lilo-22.8/mkrescue > lilo-22.8/keytab-lilo.pl > lilo-22.8/sample/ins64a.bmp > lilo-22.8/sample/ins64a.dat > lilo-22.8/sample/logo64a.bmp > lilo-22.8/sample/logo64a.dat > lilo-22.8/sample/lilo.raid.conf > lilo-22.8/sample/lilo.sample.conf > lilo-22.8/sample/blue.bmp > lilo-22.8/sample/blue.dat > lilo-22.8/sample/README > lilo-22.8/diagnose/bios.c > lilo-22.8/diagnose/cprintf.c > lilo-22.8/diagnose/test4.c > lilo-22.8/diagnose/test5.c > lilo-22.8/diagnose/sector.S > lilo-22.8/diagnose/GPLicence > lilo-22.8/diagnose/LGPLicence > lilo-22.8/diagnose/README > lilo-22.8/diagnose/README.diagnostic > lilo-22.8/diagnose/Makefile > lilo-22.8/manPages/lilo.8 > lilo-22.8/manPages/lilo.conf.5 > lilo-22.8/manPages/mkrescue.8 > lilo-22.8/dos/README > lilo-22.8/dos/Makefile > lilo-22.8/doc/README > lilo-22.8/doc/Makefile > lilo-22.8/doc/bootloader.tex > lilo-22.8/doc/image.tex > lilo-22.8/doc/map.tex > lilo-22.8/doc/other.tex > lilo-22.8/doc/parameter.tex > lilo-22.8/doc/tech.tex > lilo-22.8/doc/user.tex > lilo-22.8/doc/bootloader.fig > lilo-22.8/doc/image.fig > lilo-22.8/doc/map.fig > lilo-22.8/doc/other.fig > lilo-22.8/doc/parameter.fig > lilo-22.8/doc/fullpage.sty > lilo-22.8/doc/rlatex > lilo-22.8/doc/t2a.pl > root:/mnt/clfs/sources-clfsX64Jn08# cd lilo-22.8 > root:/mnt/clfs/sources-clfsX64Jn08/lilo-22.8# > root:/mnt/clfs/sources-clfsX64Jn08# cd lilo-22.8 > root:/mnt/clfs/sources-clfsX64Jn08/lilo-22.8# > patch -Np1 -i ../patches-clfsX64Jn08/lilo-22.8-cross_compile_x86_64-1.patch > patching file Makefile > Hunk #1 succeeded at 109 with fuzz 2 (offset 15 lines). > Hunk #2 succeeded at 456 (offset 32 lines). Very odd, for me it applies without any messages about hunks or offsets. I suppose that's just a difference between the versions of patch in fedora and clfs. What I didn't immediately spot is that your version doesn't do anything to 'checkit'. Mine says
ppc64 [EMAIL PROTECTED] ~/lilo-22.8 $patch -Np1 -i /sources/lilo-22.8-cross_compile_x86_64-2.patch patching file checkit patching file Makefile ppc64 [EMAIL PROTECTED] ~/lilo-22.8 $ (My sources are in /sources, this is just a test run in ~/.) So, something weird has happened to your patch. Please open the book's patch in a browser, and compare it to the version you have already downloaded. It sounds as if your first version is damaged. Might be useful to move your existing patch to a new name, download it again, and diff them. If they still look identical, what does head -n 12 say ? (it should show the heading, and the start of the changes to 'checkit'). I accept that you have been following the book for this, but your results are not what I expected. > root:/mnt/clfs/sources-clfsX64Jn08/lilo-22.8# make lilo.static > ./checkit > GCC version 2.91 or later is required > gcc version 4.1.2 > OKAY Is 4.1.2 a typo in copying this ? > > Please note also that after manually placing the links for as86 and > ld86 and installing lilo; a running lilo looked for /etc/lilo.conf not > $CLFS/etc/lilo.conf. This may be helpful in any update of the patch. > Possible. I remember that getting it to compile the first time (on ppc64, to make sure it wasn't using anything from the host) was an interesting experience. I'm fairly sure I tested the commands which made it in to the 1.1 book, and they haven't changed since then. Maybe I chrooted into the 'boot' system I had copied over so that I could run lilo.static. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
