From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] README.md: update instructions of building for other libc
Date: Sat, 26 Sep 2020 17:09:09 +0200 [thread overview]
Message-ID: <20200926150909.yIG6VOULU7oq9VfZA0D38cZeNf7BZGc_6xLSj8-Qjg4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25100@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
There is an updated pull request by Chocimier against master on the void-packages repository
https://github.com/Chocimier/void-packages-org readme-native-musl
https://github.com/void-linux/void-packages/pull/25100
README.md: update instructions of building for other libc
base-chroot-musl is irrelevant since some time.
@pullmoll: Do new instruction miss anything?
A patch file from https://github.com/void-linux/void-packages/pull/25100.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-readme-native-musl-25100.patch --]
[-- Type: text/x-diff, Size: 1769 bytes --]
From d8bfe538958df7b48998ed817947abfaa9e0012c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Piotr=20W=C3=B3jcik?= <chocimier@tlen.pl>
Date: Fri, 25 Sep 2020 21:27:48 +0200
Subject: [PATCH] README.md: update instructions of building for other libc
---
README.md | 18 ++++--------------
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/README.md b/README.md
index fe85e3f20eb..9238b1918ef 100644
--- a/README.md
+++ b/README.md
@@ -484,24 +484,14 @@ The second mode (native) needs a new x86 `masterdir`:
<a name="building-for-musl"></a>
### Building packages natively for the musl C library
-A native build environment is required to be able to cross compile the bootstrap packages for the musl C library; this is accomplished by installing them via `binary-bootstrap`:
-
- $ ./xbps-src binary-bootstrap
-
-Now cross compile `base-chroot-musl` for your native architecture:
-
- $ ./xbps-src -a x86_64-musl pkg base-chroot-musl
-
-Wait until all packages are built and when ready, prepare a new masterdir with the musl packages:
+Canonical way of building packages for same architecture but different C library is through dedicated masterdir.
+To build for x86_64-musl on glibc x86_64 system, prepare a new masterdir with the musl packages:
$ ./xbps-src -m masterdir-x86_64-musl binary-bootstrap x86_64-musl
-Your new masterdir is now ready to build packages natively for the musl C library. Try:
-
- $ ./xbps-src -m masterdir-x86_64-musl chroot
- $ ldd
+Your new masterdir is now ready to build packages natively for the musl C library:
-To see if the musl C dynamic linker is working as expected.
+ $ ./xbps-src -m masterdir-x86_64-musl pkg ...
<a name="building-base-system"></a>
### Building void base-system from scratch
next prev parent reply other threads:[~2020-09-26 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 19:30 [PR PATCH] " Chocimier
2020-09-26 15:09 ` Chocimier [this message]
2020-09-26 15:10 ` Chocimier
2020-09-26 19:58 ` [PR PATCH] [Merged]: " Chocimier
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=20200926150909.yIG6VOULU7oq9VfZA0D38cZeNf7BZGc_6xLSj8-Qjg4@z \
--to=chocimier@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).