[Debian-coldfire-devel] Re: Creation of #debian-68k on irc.debian.org (OFTC)

[Finn Thain]

On Wed, 21 Jun 2006, Christian T. Steigies wrote:

> On Wed, Jun 21, 2006 at 04:06:12PM +1000, Finn Thain wrote:
> > 
> > 
> > On Mon, 19 Jun 2006, Ingo Juergensmann wrote:
> > 
> > > On Mon, Jun 19, 2006 at 10:00:32AM +0200, Christian T. Steigies 
> > > wrote:
> > > 
> > > > BTW the kernel team(?) decided that we use gcc-4.0 now for all 
> > > > arches, I am not sure if that works for m68k, did anybody build a 
> > > > kernel with gcc-4 already?
> > > 
> > > Why gcc-4.0 when 4.1 is now the default? Maybe someone of the m68k 
> > > users would like to compile a kernel with gcc-4.0 and with gcc-4.1 
> > > and report how that works out? Anyone?
> > 
> > With some work, I've rev'd my cross-compilers, and yes, the 2.6.16 
> > m68k CVS kernel does build with gcc 4.0.3 and 4.1.1... except I've 
> > only tested with debian's Mac .config and it didn't build without a 
> > small patch to pmu68k.c, which I'll post to the linux-m68k list. I 
> > haven't tried booting the results.
> > 
> > As for the tool chain itself, gcc-4.0.3 won't build glibc-2.3.6 
> > without patching both packages. In particular, for gcc-4.0.3, the fix 
> > for PR 20583 which can be found in gcc-4.1 is required. I'm using 
> > upstream sources, not debian sources, so YMMV.
> 
> Can you tell some details? I tried to build a gcc-4.0 cross-compiler, 
> but it failed.

Yes, it is lots of "fun". What was the failure? What versions of binutils, 
gcc, glibc and kernel headers did you use?

I used binutils-2.17.50.0.2, but it fails to assemble the 
arch/m68k/math-emu code so you are probably better off with 2.16.1, 
although Al Viro posted some patches to fix this:

http://marc.theaimsgroup.com/?t=113633283200008&r=1&w=2
http://marc.theaimsgroup.com/?t=113522810800004&r=1&w=2

> Then I tried to build 2.6.17 with my old gcc-3.3.6, and it failed also.

When I did a "cvs up" on my linux-m68k work area, I got some strange diffs 
with mainline 2.6.17. The solution was a fresh checkout. I've no idea why 
it happened, but its not the first time.

Then, with gcc-4.1.1/binutils-2.17.50.0.2, I got this link failure:

  LD      .tmp_vmlinux1
arch/m68k/kernel/built-in.o: In function `dma_alloc_coherent':
(.text+0x1eea): undefined reference to `set_page_count'
arch/m68k/kernel/built-in.o: In function `dma_alloc_coherent':
(.text+0x1f2c): undefined reference to `set_page_count'
make: *** [.tmp_vmlinux1] Error 1

With gcc-3.3.6/binutils-2.17.50.0.2, it failed earlier:

  CC      drivers/video/fbmem.o
{standard input}: Assembler messages:
{standard input}:2113: Error: operands mismatch -- statement `moveq.l #8,%a4' ignored
make[2]: *** [drivers/video/fbmem.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2

The same thing happens with old binutils. Is this the same failure you 
saw? If so, we should probably move this thread to the linux-m68k list. 
If you have a different failure, I'd like to try your .config.

-f


> Christian
>