Hi Stephen,
> > You go ahead :-) Last time I tried, I could not even build a kernel image
> > from
> > the Debian release source kit.
>
> http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
> http://svn.debian.org/viewsvn/kernel/dists/sid/linux-2.6/debian/config/m68k/README.build?rev=12852&view=markup
>
> * build cross compiler
I'm using my old 3.3.6
> * fetch orig debian source
> * add debian directory from svn (sid)
apt-get source linux-2.6 does install the debian/ directory, so why should I
pull stuff from SVN?
> * DEB_HOST_ARCH=m68k debuild -B -am68k
Yep, that's even described debian/config/m68k/README.build. What I've ended up
doing is patch debian/config/m68k/defines and debian/config/defines to add
gcc-3.3 - that still gives me this:
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/sched.h:52,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/kernel.h:10:20: stdarg.h: No such file or directory
In file included from include/linux/sched.h:52,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/kernel.h:165: error: syntax error before "va_list"
include/linux/kernel.h:166: warning: function declaration isn't a prototype
include/linux/kernel.h:169: error: syntax error before "va_list"
include/linux/kernel.h:170: warning: function declaration isn't a prototype
include/linux/kernel.h:173: error: syntax error before "va_list"
include/linux/kernel.h:174: warning: function declaration isn't a prototype
include/linux/kernel.h:177: error: syntax error before "va_list"
include/linux/kernel.h:177: warning: function declaration isn't a prototype
include/linux/kernel.h:181: error: syntax error before "va_list"
include/linux/kernel.h:182: warning: function declaration isn't a prototype
include/linux/kernel.h:219: error: syntax error before "va_list"
include/linux/kernel.h:220: warning: function declaration isn't a prototype
make[4]: *** [arch/m68k/kernel/asm-offsets.s] Error 1
Some way or other, the include path gets messed up so stdarg.h isn't found in
the cross compilers' gcc-lib path.
> > It may be worth tracking Geert's git tree and work from that one. Geert's
> > tree
> > should allow you to check out Linus' release 2.6.28 as a branch, and import
> > all
>
> Unfortunately debian's source is sometimes sufficiently different to
> be troublesome because they pull out what they consider non-free, then
> start patching.
That should not affect m68k related areas at all.
> > of Debians patches into that branch one by one, committing as you go. A
> > diff
> > between that branch and Geert's HEAD should show all changes that are still
> > missing. How to generate one diff for each commit into Geerts tree?
> > git-cherry
> > might help there if the Debian patches match existing commits, I haven't
> > actually tried that. I'll see if I can make that work...
>
> I used git-format-patch.
Good, I'll just have to check that git-cherry works on the imported Debian
source.
Michael
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
