From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] wpa-supplicant-0.7.3: use MACHINE_ARCH
Date: Wed, 16 Feb 2011 20:41:14 +0100 [thread overview]
Message-ID: <4D5C285A.8020203@opendreambox.org> (raw)
In-Reply-To: <201102161030.43048.marcin@juszkiewicz.com.pl>
On 02/16/2011 10:30 AM, Marcin Juszkiewicz wrote:
> Dnia środa, 16 lutego 2011 o 04:03:24 Andreas Oberritter napisał(a):
>> * Because of madwifi, wpa-supplicant depends on COMBINED_FEATURES.
>> Thus, PACKAGE_ARCH must be set to MACHINE_ARCH.
>> * Use INC_PR and bump it.
>
> What about setting PACKAGE_ARCH=MACHINE_ARCH only for machines with madwifi?
> Most of out targets does not support madwifi.
Does opkg always prefer machine packages over arch packages, if you have
shared deploy directories for multiple machines? Would other package
managers like dpkg be able to handle that correctly, too? Hm, I'm not
sure whether dpkg supports multi-machine builds at all.
Regards,
Andreas
prev parent reply other threads:[~2011-02-16 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 3:03 [PATCH] wpa-supplicant-0.7.3: use MACHINE_ARCH Andreas Oberritter
2011-02-16 7:09 ` Stefan Schmidt
2011-02-16 9:30 ` Marcin Juszkiewicz
2011-02-16 10:33 ` Otavio Salvador
2011-02-16 19:41 ` Andreas Oberritter [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=4D5C285A.8020203@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.