trouble with 2.4.2 just released

trouble with 2.4.2 just released

[Heitzso]

I have two boxes that I immediately
tried upgrading the OS on.  In both
cases I use a script to automate the
build with a saved off .config file.
simplified ..
 untar linux tar ball
 cp config.blat linux/.config
 cd linux
 make oldconfig
 make menuconfig
 cp .config ../config.blat
 make bzImage
 make modules
 make modules_install
 ... copy files around ...
 lilo

On one box the build completed but 
with half a dozen C warnings and
a block of assembler warnings (RH7).  
These will always leave a sys admin 
nervous about running a kernel.

On the other box I have yet to get a
successful build (using a .config that
runs 2.4.2-pre4 fine).  ld complains
about a missing binary file.

ld: cannot open binary: no such file or directory

email be directly at xxh1@cdc.gov if
someone has a specific question re how
the kernel broke or if they want a copy
of my .config file

Note I'm running debian unstable/woody
on the system that's failing to build 
2.4.2, but this same system handled 
2.4.2-pre4 albeit with the warnings fine.

Also, feel free to throw the standard
idiot questions at me, I may have made
an idiot mistake.  My /usr partition
that has /usr/src/linux tree has 4G
avail, so I'm not running out of drive
space.  I'm running the script as root.
I tried both bz2 and gz versions of tarball.
... what am I missing ... ?

Heitzso
xxh1@cdc.gov

Re: trouble with 2.4.2 just released

[Keith Owens]

On Thu, 22 Feb 2001 13:55:28 -0500, 
Heitzso <xxh1@cdc.gov> wrote:
>ld: cannot open binary: no such file or directory

Binutils incompatibility.  Linus, please apply.

Index: 2.1/arch/i386/boot/Makefile
--- 2.1/arch/i386/boot/Makefile Fri, 05 Jan 2001 13:42:29 +1100 kaos (linux-2.4/T/c/44_Makefile 1.1 644)
+++ 2.1(w)/arch/i386/boot/Makefile Fri, 23 Feb 2001 06:55:22 +1100 kaos (linux-2.4/T/c/44_Makefile 1.1 644)
@@ -27,7 +27,7 @@ compressed/bvmlinux: $(TOPDIR)/vmlinux
 	@$(MAKE) -C compressed bvmlinux
 
 zdisk: $(BOOTIMAGE)
-	dd bs=8192 if=$(BOOTIMAGE) of=/dev/fd0
+	dd conv=notrunc bs=8192 if=$(BOOTIMAGE) of=/dev/fd0
 
 zlilo: $(CONFIGURE) $(BOOTIMAGE)
 	if [ -f $(INSTALL_PATH)/vmlinuz ]; then mv $(INSTALL_PATH)/vmlinuz $(INSTALL_PATH)/vmlinuz.old; fi
@@ -43,7 +43,7 @@ tools/build: tools/build.c
 	$(HOSTCC) $(HOSTCFLAGS) -o $@ $< -I$(TOPDIR)/include
 
 bootsect: bootsect.o
-	$(LD) -Ttext 0x0 -s -oformat binary -o $@ $<
+	$(LD) -Ttext 0x0 -s --oformat binary -o $@ $<
 
 bootsect.o: bootsect.s
 	$(AS) -o $@ $<
@@ -52,7 +52,7 @@ bootsect.s: bootsect.S Makefile $(BOOT_I
 	$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $< -o $@
 
 bbootsect: bbootsect.o
-	$(LD) -Ttext 0x0 -s -oformat binary $< -o $@
+	$(LD) -Ttext 0x0 -s --oformat binary $< -o $@
 
 bbootsect.o: bbootsect.s
 	$(AS) -o $@ $<
@@ -61,7 +61,7 @@ bbootsect.s: bootsect.S Makefile $(BOOT_
 	$(CPP) $(CPPFLAGS) -D__BIG_KERNEL__ -traditional $(SVGA_MODE) $(RAMDISK) $< -o $@
 
 setup: setup.o
-	$(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $<
+	$(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $<
 
 setup.o: setup.s
 	$(AS) -o $@ $<
@@ -70,7 +70,7 @@ setup.s: setup.S video.S Makefile $(BOOT
 	$(CPP) $(CPPFLAGS) -traditional $(SVGA_MODE) $(RAMDISK) $< -o $@
 
 bsetup: bsetup.o
-	$(LD) -Ttext 0x0 -s -oformat binary -e begtext -o $@ $<
+	$(LD) -Ttext 0x0 -s --oformat binary -e begtext -o $@ $<
 
 bsetup.o: bsetup.s
 	$(AS) -o $@ $<

trouble with 2.4.2 just released

[f5ibh]

Hi Heitzso,

>On the other box I have yet to get a
>successful build (using a .config that
>runs 2.4.2-pre4 fine).  ld complains
>about a missing binary file.

>ld: cannot open binary: no such file or directory

ld is not complaining about a missing file.

The problem is with the version of ld you use. Some versions are using 
ld --oformat and other versions ld -oformat

This is quite a recent issue. So check the version of you linker.

You can solve the problem changing :
./arch/i386/boot/Makefile:      $(LD) -Ttext 0x0 -s -oformat binary -o $@ $<
to                                                  --oformat 

I think you hav not done any mistake, but the latest Debian (unstable) version
of ld seems not to be right.

I think this will works.

---------
Best Regards 

		Jean-Luc

RE: trouble with 2.4.2 just released

[Christopher Chimelis]

> The problem is with the version of ld you use. Some versions 
> are using 
> ld --oformat and other versions ld -oformat
> 
> This is quite a recent issue. So check the version of you linker.
> 
> You can solve the problem changing :
> ./arch/i386/boot/Makefile:      $(LD) -Ttext 0x0 -s -oformat 
> binary -o $@ $<
> to                                                  --oformat 
> 
> I think you hav not done any mistake, but the latest Debian 
> (unstable) version
> of ld seems not to be right.

The latest binutils in Debian potato will take either -oformat or --oformat,
IIRC.
The lastest binutils in Debian unstable (just uploaded yesterday) will only
take --oformat.  So, if you modify arch/i386/boot/Makefile to read:

	$(LD) -Ttext 0x0 -s --oformat binary -o $@ $< ...blah blah blah
you should be fine no matter which you're using...

Chris
(Debian binutils maintainer)