On Thu, Dec 15, 2005 at 02:09:47PM +0100, Max Vozeler wrote:
> Hi Christian,
>
> On Thu, Dec 15, 2005 at 08:12:05AM +0100, Christian T. Steigies wrote:
> > On Tue, Dec 06, 2005 at 03:48:40PM +0100, Max Vozeler wrote:
> > > Apparently the binaries in m68k -headers were built for i386.
> >
> > Yes, this may very well be possible, since the m68k linux-* packages
> > were cross-compiled on i386. Since the linux-image-* packages are
> > built in the same run, and they are properly cross-compiled for m68k
> > and actually work (at least) on (my) m68k boxes, this must be a bug in
> > the linux-headers build rules, they should be cross-compiled, too.
>
> Thanks for looking into this.
>
> > > This breaks builds of external modules as they try to execute eg.
> > > scripts/basic/fixdep on m68k.
> >
> > Do you have any external modules for m68k that are not part of the kernel?
> > Who is supplying those?
>
> It's not specific to m68k actually. The module in question is the
> loop-AES extended loopback encryption module maintained by Jari Ruusu
> <[EMAIL PROTECTED]>. I'm trying to build it for all
> archs that have 2.6 -di kernels in the archive.
Are you sure you are using the per-flavour header packages
(linux-headers-2.6.14-2-<flavour> ?
Also, do you know about the external build module plan ? It is as follows :
1) build-depend on linux-headers-2.6.14 or linux-headers-2.6.14-2-all.
2) look at /usr/src/linux-headers-2.6.14-2/flavours for a list of supported
flavours.
3) for f in `cat /usr/src/linux-headers-2.6.14-2/flavours`; do
...
make ... KSRC=/lib/modules/2.6.14-2-$f
...
done
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
