On Monday 13 October 2008, you wrote:
> well, how is this supposed to work? At this point, make-kpkg
> just calls dpkg --build; and dpkg selects the name of the .deb
> (including adding the host architecture the package is being built
> upon.
I'm not sure, but it would be nice if the documentation would at least
document the restriction. Currently the cross-compilation option implies
that it should be possible to build a kernel image for e.g. sparc on
i386, but if it ends up with the wrong arch for the package then that
option is IMO pointless.
I do know that it is possible to create packages for another arch as we
e.g. build kernel udebs for any arch on any arch.
The invocation kernel-wedge uses for that is 'buildpackage -b -a$arch',
with 'buildpackage' defined as:
dpkg-buildpackage -d -us -uc -rfakeroot -tc \
-ICVS -I.svn -I'{arch}' -I.arch-ids $@
(see /usr/share/kernel-wedge/commands/build-arch)
Cheers,
FJP
P.S.
I personally don't really care about this BR anymore as with all the
problems I had I've stopped using kernel-package completely. Instead I
use the 'make deb-pkg' option supplied by the upstream kernel itself
which _does_ allow me to cross-build kernel image packages. I use it
without any problems to build kernel image packages for arm on amd64.
It also saves me huge amounts of build time as it does not clean the
entire tree for each build, which is often unnecessary.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
