* SPARC tftpboot.img build failure on 64-bit build host
@ 2014-02-17 22:40 Aaro Koskinen
2014-02-18 9:57 ` Aaro Koskinen
2014-02-18 22:32 ` David Miller
0 siblings, 2 replies; 3+ messages in thread
From: Aaro Koskinen @ 2014-02-17 22:40 UTC (permalink / raw)
To: sparclinux
Hi,
Last weekend I upgraded my cross-compilation host from 32-bit to
64-bit box, and probably because of this I'm now seeing the following
build failure with "tftpboot.img" target with current 3.14-rc:
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
kernel: arch/sparc/boot/image is ready
ELFTOAOUT arch/sparc/boot/tftpboot.img
PT 0 Entry: Loadable to 0x400000[0x91bb20] from 0x0[0x4baff8] align 0x100000
PT 1 Entry: Note
PT 2 Entry: unknown
PIGGY arch/sparc/boot/tftpboot.img
lseek: Invalid argument
make[5]: *** [arch/sparc/boot/tftpboot.img] Error 1
Since the tftpboot.img for current kernels is no longer usable anyway on
old SPARCs due to size limitations, I was wondering should we just delete
this code altogether from the kernel tree, or should we try to fix it?
People actually needing TFTP images can still use SILO/TILO...
A.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: SPARC tftpboot.img build failure on 64-bit build host
2014-02-17 22:40 SPARC tftpboot.img build failure on 64-bit build host Aaro Koskinen
@ 2014-02-18 9:57 ` Aaro Koskinen
2014-02-18 22:32 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: Aaro Koskinen @ 2014-02-18 9:57 UTC (permalink / raw)
To: sparclinux
Hi,
On Tue, Feb 18, 2014 at 12:40:01AM +0200, Aaro Koskinen wrote:
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> kernel: arch/sparc/boot/image is ready
> ELFTOAOUT arch/sparc/boot/tftpboot.img
> PT 0 Entry: Loadable to 0x400000[0x91bb20] from 0x0[0x4baff8] align 0x100000
> PT 1 Entry: Note
> PT 2 Entry: unknown
> PIGGY arch/sparc/boot/tftpboot.img
> lseek: Invalid argument
> make[5]: *** [arch/sparc/boot/tftpboot.img] Error 1
This was actually caused by elftoaout (the source for the tool I have used
wrong size data types for a.out header when compiled on x86_64).
A.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: SPARC tftpboot.img build failure on 64-bit build host
2014-02-17 22:40 SPARC tftpboot.img build failure on 64-bit build host Aaro Koskinen
2014-02-18 9:57 ` Aaro Koskinen
@ 2014-02-18 22:32 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: David Miller @ 2014-02-18 22:32 UTC (permalink / raw)
To: sparclinux
From: Aaro Koskinen <aaro.koskinen@iki.fi>
Date: Tue, 18 Feb 2014 00:40:01 +0200
> Last weekend I upgraded my cross-compilation host from 32-bit to
> 64-bit box, and probably because of this I'm now seeing the following
> build failure with "tftpboot.img" target with current 3.14-rc:
>
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> kernel: arch/sparc/boot/image is ready
> ELFTOAOUT arch/sparc/boot/tftpboot.img
> PT 0 Entry: Loadable to 0x400000[0x91bb20] from 0x0[0x4baff8] align 0x100000
> PT 1 Entry: Note
> PT 2 Entry: unknown
> PIGGY arch/sparc/boot/tftpboot.img
> lseek: Invalid argument
> make[5]: *** [arch/sparc/boot/tftpboot.img] Error 1
>
> Since the tftpboot.img for current kernels is no longer usable anyway on
> old SPARCs due to size limitations, I was wondering should we just delete
> this code altogether from the kernel tree, or should we try to fix it?
> People actually needing TFTP images can still use SILO/TILO...
I'd like to try and get it working again.
The trick is figuring out a reliable and clean way to allocate those
larger tables at run time during early boot, which is non-trivial.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-02-18 22:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-17 22:40 SPARC tftpboot.img build failure on 64-bit build host Aaro Koskinen
2014-02-18 9:57 ` Aaro Koskinen
2014-02-18 22:32 ` David Miller
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.