From: Tzafrir Cohen <tzafrir.cohen@xorcom.com>
To: maximilian attems <max@stro.at>
Cc: Michal Marek <mmarek@suse.cz>,
Linux Kbuild <linux-kbuild@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] builddeb: remove unneeded explicit Architecture
Date: Sun, 9 Sep 2012 14:54:44 +0300 [thread overview]
Message-ID: <20120909115444.GP18204@xorcom.com> (raw)
In-Reply-To: <20120907000209.GA5993@stro.at>
On Fri, Sep 07, 2012 at 02:02:09AM +0200, maximilian attems wrote:
> On Thu, 06 Sep 2012, Tzafrir Cohen wrote:
> >
> > Works for the case I presented.
>
> Michal please care to queue previous v2 patch with
> Tested-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>
> to kope with that cross building regression since
> the linux headers got added to deb-pkg target.
>
> > Now I remove the explicit setting of KBUILD_DEBRCH:
>
> and here lies the error.
>
> > $ rm -rf debian
> > $ make ARCH=arm KBUILD_IMAGE=uImage deb-pkg
> >
> > ...
> >
> > dpkg-gencontrol: error: current host architecture 'armhf' does not
> > appear in package's architecture list (armel)
> >
> > My host architecture is amd64. This is actually the build architecture.
> > dpkg-gencontrol uses Dpkg::Arch::get_host_arch().
> >
> > $ perl -MDpkg::Arch -e 'print Dpkg::Arch::get_host_arch()."\n"'
> > amd64
> >
> > $ CC=/usr/bi/narm-linux-gnueabi-gcc perl -MDpkg::Arch -e 'print Dpkg::Arch::get_host_arch()."\n"'
> > armel
> >
> > $ CC=/usr/bin/arm-linux-gnueabihf-gcc perl -MDpkg::Arch -e 'print Dpkg::Arch::get_host_arch()."\n"'
> > armhf
> >
> > $ DEB_HOST_ARCH=whatever perl -MDpkg::Arch -e 'print Dpkg::Arch::get_host_arch()."\n"'
> > whatever
> >
> > Is it OK to use that perl one-liner as the default instead of the
> > architecture guessing case?
>
> In any case that would be a follow up, but I'm not fond of that perl/dpkg
> magic plus supporting DEB_ variables.
This magic is lifted from current dpkg-gencontrol. Is there any better
way to get it?
> I think for linux it is preferable
> to have it based on UTS_MACHINE. Thus I think your testcases aren't valid,
Well, my current build script is:
#!/bin/sh
# YOu need to have one of the following unremmed to avoid a
# dpkg-gencontrol error:
export KBUILD_DEBARCH=armhf # Unrem this for armhf
#export DEB_HOST_ARCH=armel # Or this for armel
exec make ARCH=arm KBUILD_IMAGE=uImage deb-pkg "$@"
Clearly on my build toolchain I must set DEB_HOST_ARCH in some cases. So
DEB_ variables are already in there. Without it it will give me an error
for trying to build
> and also you neglected the following one:
> make KBUILD_DEBARCH=i386 deb-pkg # i386 userland with amd64 linux
I'm not sure I follow. If the packagees are to be installed on a i386
system, they are all to be considered i386, right? The linux-image
package as well. The same as
http://packages.debian.org/sid/linux-image-amd64 (the i386 variant).
Setting KBUILD_DEBARCH does not change the building of the files in any
way. It only changes the package's metadata.
Maybe set DEB_HOST_ARCH from KBUILD_DEBARCH if the latter was set?
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir
prev parent reply other threads:[~2012-09-09 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 10:44 [PATCH] builddeb: remove unneeded explicit Architecture Tzafrir Cohen
2012-08-31 13:50 ` Michal Marek
2012-09-05 13:05 ` Tzafrir Cohen
2012-09-05 13:26 ` Michal Marek
2012-09-05 15:14 ` maximilian attems
2012-09-05 16:40 ` Tzafrir Cohen
2012-09-05 20:26 ` maximilian attems
2012-09-06 14:00 ` maximilian attems
2012-09-06 14:04 ` maximilian attems
2012-09-06 16:21 ` Tzafrir Cohen
2012-09-07 0:02 ` maximilian attems
2012-09-09 11:54 ` Tzafrir Cohen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120909115444.GP18204@xorcom.com \
--to=tzafrir.cohen@xorcom.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=mmarek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).