I just created a new VM and installed Arch Linux last night. I'll try installing the bcc x86 packages this evening and cross my fingers that this distro does the trick. I wonder what the difference is? On Fri, Mar 5, 2010 at 4:47 PM, Harley Laue <losinggeneration@xxxxxxxxx> wrote: > Sorry, I meant to get back to you sooner. I run into the exact same > thing with Debian, but not Arch Linux. > Here's the last little bit from Make on Arch which seems to work (I > don't have the means to actually test it though) > > as86 -0 -o boot/crt0.o boot/crt0.s > (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 ) > tools/build boot/bootsect boot/setup boot/system > boot/Image > Root device is (3, -128) > Boot sector 512 bytes. > Setup is 1596 bytes. > System is 117788 B (58784 B code, 7728 B data and 51276 B bss) > System is 66544 > make[2]: Leaving directory `/home/harley/Source/elks-project/elks/arch/i86' > > > Obviously the ld86 is failing in Debian/Ubuntu, but like I said, I > haven't looked into why yet other then the fact that it looks like "-t > -M -o arch/i86/boot/system \" isn't in the Debian/Ubuntu's ld86's > command for some reason... -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
