Your message dated Sat, 26 May 2007 05:36:06 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384694: it would be nice if dpkg-checkbuilddeps could
check for cross build dependencies
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dpkg-dev
Version: 1.13.22
Severity: wishlist
When building debian packages for a different architecture with the help
of dpkg-cross there is no way, that I know of, to easily know if all
necessary crossdependencies are met. I'd love to see a -a option to
dpkg-checkbuilddeps so that for example dpkg-checkbuilddeps -aarm would
give a list of libraries and headers that should be installed using
dpkg-cross. if the output contained all dependencies it was still
extremely useful.
regards, Jonas
--- End Message ---
--- Begin Message ---
On Sat, 2006-08-26 at 02:00:52 +0200, Jonas Meyer wrote:
> Package: dpkg-dev
> Version: 1.13.22
> Severity: wishlist
>
> When building debian packages for a different architecture with the help
> of dpkg-cross there is no way, that I know of, to easily know if all
> necessary crossdependencies are met. I'd love to see a -a option to
> dpkg-checkbuilddeps so that for example dpkg-checkbuilddeps -aarm would
> give a list of libraries and headers that should be installed using
> dpkg-cross. if the output contained all dependencies it was still
> extremely useful.
With standard dpkg-dev you can do something like:
$ DEB_HOST_ARCH=armel dpkg-checkbuilddeps
And that will tell dpkg-architecture to override that specific
variable with the one coming from the environment. One "problem" with
this approach is that if you want a consistent build state you'll have
to set all DEB_HOST_ variables otherwise you may get something like
this:
$ DEB_HOST_ARCH=armel dpkg-architecture
...
DEB_HOST_ARCH=armel
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=i386
DEB_HOST_GNU_CPU=i486
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=i486-linux-gnu
Which is fine for dpkg-checkbuilddeps, but not for a whole build. But
of course you can always do something like:
$ eval `dpkg-architecture -aarmel -s`
before calling debuild or something.
Closing this bug report.
regards,
guillem
--- End Message ---
