Cross packaging issues with module-assistant
When you work in a chroot, you still are running a amd64 kernel, so the
corresponding headers get downloaded. One way around this is to do all of
this in a virtual machine of the appropriate architecture. That can be
relatively slow, though.
M.
On Thu, Apr 10, 2008 at 11:15 AM, Giorgio Pioda <gfwp at ticino.com> wrote:
> Hi,
>
> I'm triing to compile extra modules inside the lh chroot. Using
> module-assistant leads systematically to wrong linking with wrong
> headers. For example I'm working in a 486 chroot inside a lenny-amd64
> host and I get downloaded the amd64 headers instead of the desired 486.
>
> The same issue I registered working with a i386, linking to 686 headers
> instead of 486...
>
> I have always to rebuild the links manually...., download manually
> correct headers and binaries....
>
> Am I missing somethings important?
>
> cheers
>
> Giorgio Pioda
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFH/dq4wjjmrvf9xjcRAnBmAJ92rRY0emdJUyqBigJrbqXQwLw1egCfeU9s
> qR28Yu8TmLSeV9qjA4rm9Ss=
> =Lq1q
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> debian-live-devel mailing list
> debian-live-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/debian-live-devel/attachments/20080410/5a01d812/attachment.htm
Reply to: