From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] musl install conflicts
Date: Wed, 14 Mar 2018 20:59:41 -0400 [thread overview]
Message-ID: <20180315005941.GA20496@waltdnes.org> (raw)
In-Reply-To: <cf26422e-c7e0-05a0-fcaa-fe1218a61f2d@longlandclan.id.au>
On Wed, Mar 14, 2018 at 01:54:54PM +1000, Stuart Longland wrote
>
> By default, stages are built with USE=bindist; and this should be the
> default in make.conf.
>
> OpenSSH requires that it is built with a version of OpenSSL that's built
> with the bindist flag in the same state. So if you enable it on one,
> you need it enabled on the other. Here, you're turning off bindist; so
> you need to turn it off for OpenSSH too.
I unmasked 1 package and keyworded another as per my first message.
USE="bindist" emerge -q layman dev-vcs/git
...still has a ton of conflicts and refuses to do anything.
USE="-bindist" emerge -q layman dev-vcs/git
...wants to emerge 60 packages!!!
Total: 60 packages (1 upgrade, 55 new, 4 reinstalls),
I tried it, and resumed after build failures, but eventually ran into
unresolvable conflicts again. I'm in a chicken-and-egg problem. I
can't reliably run "emerge" without "layman" being present. But I can't
get "layman" without running "emerge". HELP! Maybe it used to be
possible, at one point, to emerge layman against the standard portage
tree under libmusl. But the tree changes over time.
Given how crucial "layman" is to the libmusl distro, why isn't the
libmusl stage 3 tarball shipped with a working "layman"? And while we're
at it, I'd like to see app-portage/cpuid2cpuflags as part of every stage
3. There are often situations where at some point in the early install,
you have to "emerge -e". It may as well be done with the right flags.
--
Walter Dnes <waltdnes@waltdnes.org>
next prev parent reply other threads:[~2018-03-15 0:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 2:32 [gentoo-embedded] musl install conflicts Walter Dnes
2018-03-14 3:54 ` Stuart Longland
2018-03-15 0:59 ` Walter Dnes [this message]
2018-03-18 1:07 ` Walter Dnes
2018-03-18 1:24 ` M. J. Everitt
2018-03-19 5:42 ` Walter Dnes
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=20180315005941.GA20496@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-embedded@lists.gentoo.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