From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/systemd: needs glibc
Date: Fri, 23 Nov 2018 08:45:15 +0100 [thread overview]
Message-ID: <20181123084515.39866127@windsurf> (raw)
In-Reply-To: <CANQCQpYaqKY+tT6E8S0VHDKdGmiAg9nDg2N6oGk32kkcQz=dZw@mail.gmail.com>
Hello,
On Thu, 22 Nov 2018 20:30:21 -0600, Matthew Weber wrote:
> It looks like the utils/genrandconfig is generating the right cfg
> combinations for uclibc and systemd. It did however look like the way
> the random selection of init options +"BR2_STATIC_LIBS" selection
> (systemd depends on !BR2_STATIC_LIBS), may lower the number of builds
> considerably. (guessing ~0.15% chance of a build if my math is
> correct --> 100% / 2 / 16 / 20)
BR2_STATIC_LIBS is added only on one out of 20 configurations, so the
math here is not correct I believe: the last "divide by 20" would mean
that BR2_STATIC_LIBS disabled is one every 20 builds, but it's the
opposite.
Or is my math failing ?
> Additionally, it looks like at least one (maybe more) of our prebuilt
> uclibc toolchains don't include BR2_USE_WCHAR which is required for
> systemd.
Most of them have BR2_USE_WCHAR.
> Maybe we should move the conditionals for BR2_STATIC_LIBS and
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV inside the busybox condition.
> Plus toolchain updates for BR2_USE_WCHAR (if that matters now that
> uclibc is gone).....
The BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV condition is already
mutually exclusive with BR2_INIT_SYSTEMD, due to the "elif". However,
it is also mutually exclusive with Busybox, which is a bit silly.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-23 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 21:05 [Buildroot] [PATCH] package/systemd: needs glibc Yann E. MORIN
2018-11-22 2:53 ` Matthew Weber
2018-11-22 16:19 ` Peter Korsgaard
2018-11-22 16:44 ` Thomas Petazzoni
2018-11-22 17:12 ` Yann E. MORIN
2018-11-23 2:30 ` Matthew Weber
2018-11-23 7:45 ` Thomas Petazzoni [this message]
2018-11-23 8:27 ` Thomas Petazzoni
2018-11-27 21:20 ` Arnout Vandecappelle
2018-12-04 8:28 ` Thomas Petazzoni
2018-12-04 10:32 ` Nicolas Cavallari
2018-12-04 11:02 ` Arnout Vandecappelle
2018-12-04 11:17 ` Nicolas Cavallari
2018-11-26 16:54 ` Peter Korsgaard
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=20181123084515.39866127@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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