Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Peter Seebach <peter.seebach@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Use alternatives for all of binutils instead of -symlinks
Date: Wed, 16 Oct 2013 09:48:01 -0700	[thread overview]
Message-ID: <525EC341.9080407@linux.intel.com> (raw)
In-Reply-To: <cover.1381435139.git.peter.seebach@windriver.com>


During MUT builds, we saw a failure with the toolchain


| Computing transaction...error: Can't install 
binutils-cross-canadian-arm-2.23.2-r4@i686_nativesdk: no package 
provides update-alternatives-cworth
|

Can be seen all architectures.


Sau!



On 10/10/2013 01:06 PM, Peter Seebach wrote:
> The original complaint that got me started on this was that someone
> was using binutils on a target, and didn't have an ld command, so they
> asked for it. We added binutils-symlinks, and that seemed to work, but
> eventually we ran into a problem because "ar" and "strings" weren't
> showing up.
>
> After some asking about as to why ar and strings might be omitted from
> binutils, we concluded that it was probably because they were using
> the alternatives mechanism. In a local branch, we experimented for a while
> with just using that instead of the -symlinks package, and found that
> it was overall better-behaved; in particular, it produces the desireable
> result that you don't have to know about or add a "-symlinks" package
> to use the utilities in the common case where you just install a package
> and expect its binaries to show up. It also eliminates the odd special
> case difference between ar/strings (which can be provided by busybox)
> and the other utilities.
>
> This is implemented as two patches. The first switches to using the
> alternatives mechanism, but leaves the alternatives in the -symlinks
> package rather than in the base package. The second moves them into
> the base package, and adds an RPROVIDES for the -symlinks name in
> case anyone is using it.
>
> One caveat: This can produce warnings because the "embedspu" and "ld.gold"
> binaries don't always exist, but they sometimes exist. I'm not sure whether
> there's a good way to fix that...
>
> The following changes since commit 1149b1fef8912f77d971242dfec151fff5a3aa51:
>
>    build-appliance: Update SRCREV for release (2013-10-08 16:33:25 +0100)
>
> are available in the git repository at:
>    git://git.yoctoproject.org/poky-contrib seebs/binutils-alternatives
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/binutils-alternatives
>
> Peter Seebach (2):
>    Use alternatives for the binutils-symlinks package.
>    Drop binutils-symlinks
>
>   meta/recipes-devtools/binutils/binutils.inc |   68 ++++++++++++++++-----------
>   1 files changed, 40 insertions(+), 28 deletions(-)
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  parent reply	other threads:[~2013-10-16 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 20:06 [PATCH 0/2] Use alternatives for all of binutils instead of -symlinks Peter Seebach
2013-10-10 20:06 ` [PATCH 1/2] Use alternatives for the binutils-symlinks package Peter Seebach
2013-10-10 20:06 ` [PATCH 2/2] Drop binutils-symlinks Peter Seebach
2013-10-16 16:48 ` Saul Wold [this message]
2013-10-16 19:18   ` [PATCH 0/2] Use alternatives for all of binutils instead of -symlinks Mark Hatle
2013-10-18 23:24   ` [PATCH 0/2] v2: Use alternatives for binutils Peter Seebach
2013-10-18 23:24     ` [PATCH 1/2] Use alternatives for the binutils-symlinks package Peter Seebach
2013-10-19  5:22       ` Saul Wold
2013-10-21  3:46         ` Peter Seebach
2013-11-04 18:40         ` Peter Seebach
2013-10-18 23:24     ` [PATCH 2/2] Drop binutils-symlinks Peter Seebach

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=525EC341.9080407@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.seebach@windriver.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