From: Martin Jansa <martin.jansa@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
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 22:09:16 +0200 [thread overview]
Message-ID: <20190522200916.GA1421@jama> (raw)
In-Reply-To: <20190522141825.GA7379@localhost>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
On Wed, May 22, 2019 at 05:18:25PM +0300, Adrian Bunk wrote:
> 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
It's not disabled in my defconfig like it is in
meta/recipes-core/busybox/busybox/defconfig, maybe it got auto enabled.
In log.do_configure I see:
...
*
* Miscellaneous Utilities
*
adjtimex (4.7 kb) (ADJTIMEX) [N/y/?] n
bbconfig (9.7 kb) (BBCONFIG) [N/y/?] n
bc (45 kb) (BC) [Y/n/?] (NEW) dc (36 kb) (DC) [Y/n/?] y
Use bc code base for dc (larger, more features) (FEATURE_DC_BIG) [Y] (NEW) y
Interactive mode (+4kb) (FEATURE_BC_INTERACTIVE) [Y/n/?] (NEW) Enable bc/dc long options (FEATURE_BC_LONG_OPTIONS) [Y/n] (NEW) beep (2.4 kb) (BEEP) [N/y/?] n
chat (6.3 kb) (CHAT) [N/y/?] n
conspy (10 kb) (CONSPY) [N/y/?] n
...
> > 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.
Thanks I've never noticed dc before.
I see both dc and bc in 1.06 version from meta-gplv2 which was released
on 2000-11-15
bc/1.06-r3/image/usr/bin/bc
As there is already u-a for dc, I will sent u-a for bc as well.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2019-05-22 20:09 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
2019-05-22 20:09 ` Martin Jansa [this message]
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=20190522200916.GA1421@jama \
--to=martin.jansa@gmail.com \
--cc=bunk@stusta.de \
--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