Hi Geert,
I remember seeing this as well a long time ago, due to some
bug/misconfiguration. But that
got fixed.
I'll dig through the mailbox ...
BTW, IIRC there were also some issues with some version of binutils,
but I never saw that problem.
gcc version 4.1.2 20061115 (prerelease) (Ubuntu 4.1.1-21)
GNU assembler (GNU Binutils) 2.18.0.20080103
The 4.1.0 I built does not get past the compiler test now (miscompiles __weak).
My copy of crosstool (0.43) combines 4.1.0 and 4.1.1 (the latest supported) with
binutils 2.16.1 ... I'll give 2.18 a try.
3.3.6 is built with 2.15 - the m68k crosstool 0.38 build script of Christian did
use 2.16.
Probably no matter though - building 2.6.33 with my old cross compiler once I
had revived that from the failing disk (3.3.6/2.16) results in the same double
fault.
My binutils is 2.18.1~cvs20080103-7 according to dpkg.
2.18.1~cvs20080103-0ubuntu1 ... what is the host binutils even used for?
Can you send that kernel and the defconfig by PM please?
Done.
Thanks, testing ... yours does in fact boot on my ARAnyM setup. Compiling with
your .config results in the same error.
I tested one of the failing kernels on the real Falcon and it did spontaenously
reboot there (with no output) as well.
Strange.
Yep - I'll try to compile the last kernel version that worked for me to see what
the various cross compilers generate for that. 2.6.30-rc6 (botched git pull so
I'm not too positive it isn't 2.6.29-something) does in fact compile fine with
my old 3.3.6 cross-gcc as well as my newly built one.
I'll verify that on the new tree, and start bisecting. Sigh.
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
