Re: piggy broken in 2.5.24 build

[Kai Germaschewski]

On Sat, 22 Jun 2002, sean darcy wrote:

> At the end of make bzImage I get:
> 
> > make[2]: Entering directory `/opt/kernel/linux-2.5.24/arch/i386/boot/compressed'
> > tmppiggy=_tmp_$$piggy; \
> > rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk; \
> > objcopy -O binary -R .note -R .comment -S /opt/kernel/linux-2.5.24/vmlinux $tmppiggy; \
> > gzip -f -9 < $tmppiggy > $tmppiggy.gz; \
> > echo "SECTIONS { .data : { input_len = .; LONG(input_data_end - input_data) input_data = .; *(.data) input_data_end = .; }}" > $tmppiggy.lnk; \
> > ld -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b elf32-i386 -T $tmppiggy.lnk; \
> > rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk
> > /bin/sh: _tmp_18313piggy: No such file or directory
> > ld: cannot open _tmp_18313piggy.gz: No such file or directory
> > gcc -D__ASSEMBLY__ -D__KERNEL__ -I/opt/kernel/linux-2.5.24/include -traditional -c head.S
> > gcc -D__KERNEL__ -I/opt/kernel/linux-2.5.24/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DKBUILD_BASENAME=misc -c misc.c
> > ld -m elf_i386 -Ttext 0x100000 -e startup_32 -o bvmlinux head.o misc.o piggy.o
> > ld: cannot open piggy.o: No such file or directory
> > make[2]: *** [bvmlinux] Error 1
> > make[2]: Leaving directory `/opt/kernel/linux-2.5.24/arch/i386/boot/compressed'
> > make[1]: *** [compressed/bvmlinux] Error 2
> > make[1]: Leaving directory `/opt/kernel/linux-2.5.24/arch/i386/boot'
> > make: *** [bzImage] Error 2

At least I didn't break it, for a change. For all I can tell, the link of
piggy.o fails, since the _tmp_xx.gz doesn't exist. That again doesn't 
exist since the _tmp_xx does not exist when gzipping it.

So the question is why does the objcopy ... line not generate the tmp_xx
file. I don't see it spitting out any error either, but could you check
the obvious, like remaining free space on that filesystem and /tmp?

BTW: I just rewrote that part so that it would at least properly stop at 
the place where the error occurs, but that still leaves the question as to
what the actual error in your case is.

> Can I boot with just vmlinux?

Not unless you have a bootloader which supports that (i.e.: No.)

--Kai