From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] musl install conflicts
Date: Sat, 17 Mar 2018 21:07:45 -0400 [thread overview]
Message-ID: <20180318010745.GA16222@waltdnes.org> (raw)
In-Reply-To: <20180314023231.GA3617@waltdnes.org>
On Tue, Mar 13, 2018 at 10:32:31PM -0400, Walter Dnes wrote
> I'm trying to install musl (x86) on an old laptop.
...and getting nowhere. Can I have some guidance on filing a bug report
on bugzilla? Is the 32-bit libmusl distro a "hosted project"? Using...
http://distfiles.gentoo.org/experimental/x86/musl/stage3-i686-musl-vanilla-20180304.tar.bz2
...I run into a "chicken-and-egg-problem". According to the HOWTO
http://distfiles.gentoo.org/experimental/x86/musl/HOWTO step 5...
5) Okay now we can update. ***IF WE TRY TO UPDATE WITHOUT THE OVERLAY,
WE GET A BUNCH OF DOWNGRADES TO EBUILDS THAT ARE SLIGHTLY BROKEN ON MUSL
AND WILL NOT BUILD.***
But to get the overlay we first have to do step 3...
3) We need to get git in order to add the overlay. Unfortunately, right
now we can't build git with gnupg support so do the following:
echo "dev-vcs/git -gpg" >> /etc/portage/package.use
emerge -q layman dev-vcs/git
So I can't do an "emerge" without first setting up the overlay, but I
can't set up the overlay without first running "emerge" to build layman
and git. Do you see the problem? As per the comment on step 5 I get
several "ebuilds that are slightly broken on musl and will not build".
The main symptom is that some ebuilds have a dependancy that requires
"bindist" USE flag and some ebuilds require USE="-bindist" for the same
dependancy. See this thread, which is archived at...
https://archives.gentoo.org/gentoo-embedded/message/38e4498aedc2817e96c57b13bc584030
Attempting to build with either all "bindist" or all "-bindist"
results in breakages.
Proposed "Patch"
================
Please ship the stage-3 tarball complete with functional "layman" and
"git" pre-built. It may have been possible to emerge layman and git
against the standard portage tree in the past, but the portage tree is
dynamic, and that does not seem to work for me now. Given how crucial
"layman" and "git" are to the musl distro, they should be shipped with
the stage-3 tarball.
--
Walter Dnes <waltdnes@waltdnes.org>
next prev parent reply other threads:[~2018-03-18 1:07 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
2018-03-18 1:07 ` Walter Dnes [this message]
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=20180318010745.GA16222@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