From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] multilib.conf: Workaround opkg multilib issues
Date: Fri, 12 Apr 2013 19:43:36 +0200 [thread overview]
Message-ID: <20130412174336.GT2477@jama> (raw)
In-Reply-To: <1365785190.16702.65.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Fri, Apr 12, 2013 at 05:46:30PM +0100, Richard Purdie wrote:
> Multilib with opkg hasn't worked since the --force-overwrite option was dropped in
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=88a9f6db3482623c9cb54fb03db1045051cec9f6
>
> Since we merged the libexecdir changes, we also need the --force-maintainer flag
> to avoid conf file conflicts.
>
> Both these changes are suboptimal however the alternative is completely broken and
> these changes only affect people who have multilibs enabled and use opkg.
Can we add --force-overwrite only when MULTILIB is enabled?
> [YOCTO #3453]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf
> index 9a129f1..9ff06cc 100644
> --- a/meta/conf/multilib.conf
> +++ b/meta/conf/multilib.conf
> @@ -14,3 +14,5 @@ INHERIT += "multilib_global"
> BBCLASSEXTEND_append = " ${MULTILIBS}"
>
> MULTILIB_GLOBAL_VARIANTS = "lib32 lib64 libx32"
> +
> +OPKG_ARGS_append = " --force-maintainer --force-overwrite"
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-04-12 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 16:46 [PATCH] multilib.conf: Workaround opkg multilib issues Richard Purdie
2013-04-12 17:43 ` Martin Jansa [this message]
2013-04-12 21:36 ` Richard Purdie
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=20130412174336.GT2477@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox