Re: Compilation problems with 2.0.34pre13??

Anthony Barbachan (
Thu, 14 May 1998 01:11:45 -0400

I looks to me that you upgrade your binutils using one from GNU's ftp site.
>From what I can tell the Linux patched ones at have options
not availible in the generic GNU binutils.

-----Original Message-----
From: <>
To: <>
Date: Wednesday, May 13, 1998 7:16 PM
Subject: Compilation problems with 2.0.34pre13??

>This may strike as a stupid or dumb question to some of you, but i'm
>experiencing serious problems compiling the 34pre13 kernel.
>What i'm trying to do is to step back from 2.1.99 to the 34pre13 kernel,
>but i don't seem to be able to compile it right. The problem lies
>somewhere in the final stage of compilation, in the
>arch/i386/boot/Makefile and arch/i386/boot/compressed/Makefile. I tried to
>modify these Makefiles so that they would look like the 2.1.99 ones (which
>compiles perfectly) as a last resort, but then the compilation process
>reports the system to be 0 Kb.
>I suspect there's a problem with objdump, but i haven't had any probs with
>it before.
>What follows is a log of console output when i don't change anything. I
>hope someone can help.
>ld -m elf_i386 -Ttext 0x100000 -e stext arch/i386/kernel/head.o init/main.o
init/version.o \
> arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o
fs/fs.o ipc/ipc.o net/network.a \
> fs/filesystems.a \
> drivers/block/block.a drivers/char/char.a drivers/net/net.a
drivers/pci/pci.a \
> /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/i386/lib/lib.a -o vmlinux
>nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( a \)' | sort >
>make[1]: Entering directory `/usr/src/linux/arch/i386/boot'
>make[2]: Entering directory `/usr/src/linux/arch/i386/boot/compressed'
>tmppiggy=/tmp/$$piggy; \
>rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk; \
>if hash encaps 2> /dev/null; then \
> objdump -k -q -o 0x100000 /usr/src/linux/vmlinux > $tmppiggy; \
>else \
> objcopy -O binary -R .note -R .comment -R .stab -R .stabstr
/usr/src/linux/vmlinux $tmppiggy; \
>fi; \
>objdump: invalid option -- k
>Usage: objdump [-ahifCdDprRtTxsSlw] [-b bfdname] [-m machine] [-j
> [--archive-headers] [--target=bfdname] [--debugging] [--disassemble]
> [--disassemble-all] [--disassemble-zeroes] [--file-headers]
> [--section-headers] [--headers]
> [--info] [--section=section-name] [--line-numbers] [--source]
> [--architecture=machine] [--reloc] [--full-contents] [--stabs]
> [--syms] [--all-headers] [--dynamic-syms] [--dynamic-reloc]
> [--wide] [--version] [--help] [--private-headers]
> [--start-address=addr] [--stop-address=addr]
> [--prefix-addresses] [--[no-]show-raw-insn] [--demangle]
> [--adjust-vma=offset] [-EB|-EL] [--endian={big|little}] objfile...
>at least one option besides -l (--line-numbers) must be given
>objdump: supported targets: elf32-i386 a.out-i386-linux coff-i386 srec
symbolsrec tekhex binary ihex trad-core
>gzip -f -9 < $tmppiggy > $tmppiggy.gz; \
>if hash encaps 2> /dev/null; then \
> encaps --target elf32-i386 piggy.o $tmppiggy.gz input_data input_len; \
>else \
> echo "SECTIONS { .data : { input_len = .; LONG(input_data_end -
input_data) input_data = .; *(.data) input_data_end = .; }}" >
$tmppiggy.lnk; \
> ld -m elf_i386 -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b
elf32-i386 -T $tmppiggy.lnk; \
>fi; \
>rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk
>ld -m elf_i386 -Ttext 0x1000 -e startup_32 -o vmlinux head.o misc.o
>make[2]: Leaving directory `/usr/src/linux/arch/i386/boot/compressed'
>if hash encaps 2> /dev/null; then \
> objdump -k -q -o 0x1000 compressed/vmlinux > compressed/vmlinux.out; \
>else \
> objcopy -O binary -R .note -R .comment -R .stab -R .stabstr
compressed/vmlinux compressed/vmlinux.out; \
>make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
>-- Nico Galoppo scratch at edge dot eu dot org
>-- Sysadmin Leuven, Belgium
>-------- NT *is* secure, unless you remove the shrink-wrap ---------
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to