Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] util-linux: Add missing ptest dependencies
Date: Wed, 22 May 2019 17:18:25 +0300	[thread overview]
Message-ID: <20190522141825.GA7379@localhost> (raw)
In-Reply-To: <CA+chaQdu3hKa6ogM=9_iG1GS67YdrwoF=J2YWdh6RX3V1r7qbA@mail.gmail.com>

On Wed, May 22, 2019 at 01:03:37PM +0200, Martin Jansa wrote:
> This pulls bc to many images with busybox, causing busybox postinst to fail
> with:
> 
> update-alternatives: Error: not linking /usr/bin/bc to /bin/busybox.nosuid
> since /usr/bin/bc exists and is not a link

Are you enabling CONFIG_BC in your busybox config?
It is not enabled in meta/recipes-core/busybox/busybox/defconfig

> I'll check which busybox defconfig entry enables BC and send patch to use
> u-a for bc in ./meta/recipes-extended/bc/bc_1.07.1.bb
> 
> There already is:
> ALTERNATIVE_${PN} = "dc"
> ALTERNATIVE_PRIORITY = "100"
> but maybe dc is a typo.

bc and dc are two different binaries built from bc.

busybox used to only have dc, bc was added 6 months ago.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-05-22 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1558300553.git.just.another.mariano@gmail.com>
2019-05-19 21:21 ` [PATCH 1/1] util-linux: Add missing ptest dependencies Mariano López
2019-05-22 11:03   ` Martin Jansa
2019-05-22 14:18     ` Adrian Bunk [this message]
2019-05-22 20:09       ` Martin Jansa
2019-05-22 20:48         ` Martin Jansa

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=20190522141825.GA7379@localhost \
    --to=bunk@stusta.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox