Re: Still having a problem building elks kernel (nospam: message 16 of 20)
Dieter Kedrowitsch <[email protected]>
| Newsgroups | gmane.linux.ports.x8086 |
|---|---|
| Message-ID | <[email protected]> |
Ok!
By using Ubuntu 9.10 i386 and applying the following changes to a
fresh download of the elks-0.1.3.tar.gz before doing make config, make
dep, make Image:
edit /arch/i86/boot/setup.S line 588 remove () from around CONFIG_CPU_80386
edit /arch/i86/drivers/char/Keymaps/mkcfg change "sort +1f" to "sort -f"
I was able to get 95% there. It still errors out during linking of the image.
as86 -0 -o boot/crt0.o boot/crt0.s
(cd ../.. ; ld86 -0 -i \
arch/i86/boot/crt0.o arch/i86/boot/crt1.o \
init/main.o kernel/kernel.a fs/fs.a lib/lib.a net/net.a
fs/minix/minixfs.a arch/i86/kernel/akernel.a arch/i86/lib/lib86.a
arch/i86/mm/mm.a arch/i86/drivers/char/chr_drv.a
arch/i86/drivers/block/blk_drv.a \
-t -M -o arch/i86/boot/system > System.tmp ; \
sort -k4 System.tmp > System.map ; rm -f System.tmp )
usage: ld86 [-03NMdimrstz[-]] [-llib_extension] [-o outfile] [-Ccrtfile]
[-Llibdir] [-Olibfile] [-Ttextaddr] [-Ddataaddr] [-Hheapsize] infile...
tools/build boot/bootsect boot/setup boot/system > boot/Image
Root device is (3, -128)
Boot sector 512 bytes.
Setup is 1764 bytes.
Unable to open 'system'
make[1]: *** [Image] Error 1
However, by manually linking using the sample from Harley...
cd ../.. ; ld86 -0 -i \
-t -M -o arch/i86/boot/system \
arch/i86/boot/crt0.o arch/i86/boot/crt1.o \
init/main.o kernel/kernel.a fs/fs.a lib/lib.a net/net.a
fs/minix/minixfs.a arch/i86/kernel/akernel.a arch/i86/lib/lib86.a
arch/i86/mm/mm.a arch/i86/drivers/char/chr_drv.a
arch/i86/drivers/block/blk_drv.a \
> System.tmp ; \
sort -k4 System.tmp > System.map ; rm -f System.tmp
...then allowing make Image to finish, I was successful!
So, why does make Image try to link differently then Harley's example?
Does Arch vs Ubuntu really have anything to do with it?
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html