[ale] Problems...

[Dunlap, Randy]

copied from lkml archives:
> Riding the bleeding edge of debian leaves some interesting tastes.
> The line 'ld: cannot open binary: No such file or directory' is puzzling.
> The Makefile only has one dash. Changing -oformat to --oformat in
> arch/i386/boot/Makefile builds the kernel just fine.

Correct fix. (Already in 2.4.2-ac, and 2.4.3-pre)
<end copy>

HTH.

~Randy________________________503-677-5408_____
-----------------------------------------------

> -----Original Message-----
> From: Trey Darley [mailto:tdarley at net-hopper.com]
> 
> At any rate, I've been trying unsuccessfully to make a build work of a
> 2.4.2 kernel, patched with the 802.1 VLAN trunking support from
> <http://scry.wanfear.com/~greear/vlan.html>. So far, so good. But my
> 'make bzImage' keeps failing. I've patched everything up. The 
> error that
> I get is:
> 
> make[1]: Entering directory `/usr/src/linux/arch/i386/boot'
> gcc -E -D__KERNEL__ -I/usr/src/linux/include -D__BIG_KERNEL__
> -traditional -DSVGA_MODE=NORMAL_VGA  bootsect.S -o bbootsect.s
> as -o bbootsect.o bbootsect.s
> bbootsect.s: Assembler messages:
> bbootsect.s:253: Warning: indirect lcall without `*'
> ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
> ld: cannot open binary: No such file or directory
> make[1]: *** [bbootsect] Error 1
> make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
> make: *** [bzImage] Error
> 
> I'm using 2.11.90.0.8 version of 'ld' and the specification 
> is a minimum
> of 2.9.1.0.25. Is it likely, do you think, that I might have too new a
> version? I'm running out of darts to throw, so any assistance would be
> much appreciated. I maybe should try removing the patches and seeing
> what that does. Something tells me that this isn't what's 
> generating the
> error. The bbootsect.o and bbootsect.h both exist in their proper
> directory.
> -- Trey

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.