2001-03-01 18:36:26

by Florian Nykrin

[permalink] [raw]
Subject: ld-error on 2.4.2 and on 2.4.1

Hello,

Because I don't know which maintainer to write I write to this list.

When I try to compile 2.4.2 or 2.4.1 I get the error:

arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o
mm/mm.o fs/fs.o ipc/ipc.o \
drivers/block/block.o drivers/char/char.o drivers/misc/misc.o
drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o
drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/cdrom/driver.o
drivers/pci/driver.o drivers/pcmcia/pcmcia.o drivers/pnp/pnp.o
drivers/video/video.o drivers/usb/usbdrv.o \
net/network.o \
/usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aUw]
\)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
make[1]: Entering directory `/usr/src/linux-2.4.2/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-2.4.2/arch/i386/boot'

I also tried it on another Machine, but I got the same result.

I am using a Toshiba Satellite 2800 Notebook.

The output of lspci is:

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host
bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03)
00:05.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:05.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:05.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:05.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
00:08.0 Communication controller: Lucent Microelectronics: Unknown
device 0420
00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to
Cardbus Bridge with ZV Support (rev 20)
00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to
Cardbus Bridge with ZV Support (rev 20)
00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-754 [DS-1E
Audio Controller]
01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/MX-/IX
(rev 13)

I am using Debian Sid:
gcc version: 2.95.3-5
binutils version: 2.10.91.0.2-2
ldso version: 1.9.11-14

The config-file is attached.

Please also reply to my mail-adress because I am not reading the
kernel-mailing-list.

Regards, Florian.


Attachments:
(No filename) (2.54 kB)
.config (17.59 kB)
Download all attachments

2001-03-01 18:41:26

by Caleb Epstein

[permalink] [raw]
Subject: Re: ld-error on 2.4.2 and on 2.4.1

On Thu, Mar 01, 2001 at 07:35:58PM +0100, Florian Nykrin wrote:

> Hello, Because I don't know which maintainer to write I write to
> this list. When I try to compile 2.4.2 or 2.4.1 I get the error: 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-2.4.2/arch/i386/boot'

perl -pi -e 's/-oformat/--oformat/' arch/i386/boot/Makefile

--
cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg.

2001-03-01 18:43:47

by Alan

[permalink] [raw]
Subject: Re: ld-error on 2.4.2 and on 2.4.1

> 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

Debian Sid currently includes a binutils that drops the option the kernel
uses. If you look through the archive you'll find a patch to do deal with
this, or you can just go back to a slightly older binutils

Also gcc 2.95.3 cvs snapshots aren't yet a recommended build tool for the
kernel. They are probably ok though. I've had no evidence to suggest they
miscompile anything.

Alan