From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glibc: ftbfs for ppcle
Date: Sun, 28 Feb 2021 02:23:19 +0100 [thread overview]
Message-ID: <20210228012319.ZRZJS6b6oTEH7mtAZbmZFYQxIa1FYMcZi9Wxgt8jsik@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/29106#issuecomment-787215893
Comment:
So the `cross-powerpc-linux-gnu` problem seems to be a parallelism issue. I have `XBPS_MAKEJOBS=120` in `etc/conf`. In another try I could now build the pkg with both, my own pkgs and the official ones in a `binary-bootstrap i686`.
However the failure to build `glibc` happens here also with the official binaries, i.e.:
```
./xbps-src zap
./xbps-src binary-bootstrap i686
./xbps-src -a ppcle pkg glibc
```
fails for me just as with my home grown `i686` pkgs. My `etc/conf` is:
```
XBPS_MAKEJOBS=120
XBPS_CCACHE=yes
XBPS_DEBUG_PKGS=yes
XBPS_ALLOW_RESTRICTED=yes
```
Kernel is `linux-5.11.2_2` and I'm going to try on the `5.10` series now.
next prev parent reply other threads:[~2021-02-28 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 22:58 [ISSUE] " pullmoll
2021-02-27 23:32 ` pullmoll
2021-02-27 23:58 ` q66
2021-02-28 1:00 ` pullmoll
2021-02-28 1:23 ` pullmoll [this message]
2021-02-28 1:43 ` pullmoll
2021-02-28 1:45 ` pullmoll
2021-02-28 2:13 ` pullmoll
2021-02-28 2:16 ` pullmoll
2021-04-28 12:14 ` [ISSUE] [CLOSED] " ericonr
2021-04-28 12:14 ` ericonr
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=20210228012319.ZRZJS6b6oTEH7mtAZbmZFYQxIa1FYMcZi9Wxgt8jsik@z \
--to=pullmoll@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).