[Clfs-support] bin86 install and chroot(ABLE) test: x86_64 build

[Ken Moffat]

On Thu, Jan 17, 2008 at 05:07:08PM +0000, b-vol wrote:
> Greetings
> 
> 
> ###########  7.12. Bin86-0.16.17
> 
> its a good idea to put the following two lines in any update of the book 
> otherwise lilo will not install:
> 
> cd /cross-tools/bin
> ln -s /cross-tools/bin/x86_64-unknown-linux-gnu-as86 /cross-tools/bin/as86
> ln -s /cross-tools/bin/x86_64-unknown-linux-gnu-ld86 /cross-tools/bin/ld86
> 
 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
|
|BCC version 0.16.10 or later is recommended
|bcc is not present
|You will not be able to make floppy2, diag2.img, or lilo.com
|make: *** [test.img] Error 1
|
|#########

 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:
ken at AD5 ~/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

BCC version 0.16.10 or later is recommended
bcc is not present
You will not be able to make floppy2, diag2.img, or lilo.com
make: *** [test.img] Error 1

 So it's clear that you didn't apply the patch.

> clfs:~$ /tools/bin/gcc -v
> /tools/bin/gcc: error while loading shared libraries: libgcc_s.so.1: cannot 
> open shared object file: No such file or directory
> clfs:~$   
> 
> ##and libgcc_S.so.1 was not found
> 
> 
> suggestions of a fix would be welcomed
> 

 My suggestion is that you do what it says in section 8.8, or if you
think you have already done that, make sure all the symlinks are
actually present in the correct directories, and also that the files
they point to are present.

 Perhaps I should point out that very little in the (trunk) books
is optional.  So, make sure that you follow all the instructions,
and take whatever measures will enable you to check that things
worked.

 If you are scripting the build, check the status ($?) of commands.
If you are typing them in, you should be able to see the error
messages when things fail.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce