From: Frans Pop <elendil@planet.nl>
To: Wei Chong Tan <weichong78@gmail.com>
Cc: sam@ravnborg.org, max@stro.at, linux-kernel@vger.kernel.org
Subject: Re: PATCH: ARCH in builddeb
Date: Tue, 22 Sep 2009 18:53:38 +0200 [thread overview]
Message-ID: <200909221853.40148.elendil@planet.nl> (raw)
In-Reply-To: <31cb94fa0909220743w6c512075ve69ec292b37a079a@mail.gmail.com>
On Tuesday 22 September 2009, Wei Chong Tan wrote:
> > That still given me an arm instead of an armel package.
>
> dpkg-architecture seems to set a bunch of build-time environment
> variable, could it be there one is not set by default for arm vs
> armel?
dpkg-gencontrol, if left alone, seems to understand about cross-compiling
*and* understand the difference between compiling for arm and armel, while
dpkg-architecture seems to ignore that. But I really don't know enough
about either to be able to say what the exact problem is or what the
correct solution is here.
All I can tell you is that when I cross-compile for armel (on a Debian
amd64/Lenny host system) with very simply the following set in the
environment, it all magically works correctly:
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabi-
I don't think we should lose correct automatic detection for the sake of
fixing your use case.
I would suggest asking for advice on the debian-devel mailing list or,
maybe even better, from the dpkg maintainers.
Cheers,
FJP
next prev parent reply other threads:[~2009-09-22 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 5:25 PATCH: ARCH in builddeb Wei Chong Tan
2009-09-14 21:01 ` Frans Pop
2009-09-16 14:19 ` Frans Pop
2009-09-17 0:12 ` Wei Chong Tan
2009-09-18 3:10 ` Wei Chong Tan
2009-09-20 13:09 ` Frans Pop
2009-09-22 0:38 ` Frans Pop
2009-09-22 14:38 ` Frans Pop
2009-09-22 14:43 ` Wei Chong Tan
2009-09-22 16:53 ` Frans Pop [this message]
2009-09-22 23:07 ` Wei Chong Tan
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=200909221853.40148.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=sam@ravnborg.org \
--cc=weichong78@gmail.com \
/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