From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [wip/rfc] perl: change config
Date: Sat, 25 Sep 2021 11:05:05 +0200 [thread overview]
Message-ID: <20210925090505.qeSTt0R9GyzAFDhA8Tz4PQCXs-ExRO_pi7QRg6XbpSY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33089@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/33089#issuecomment-927091957
Comment:
I think that using `perl-cross` for everything means sacrificing too much in favor of cross-compiling.
This is what gentoo does, similar to what I proposed:
```
if tc-is-cross-compiler; then
./configure \
--target="${CHOST}" \
--build="${CBUILD}" \
-Dinstallprefix='' \
-Dinstallusrbinperl='undef' \
-Dusevendorprefix='define' \
"${myconf[@]}" \
|| die "Unable to configure"
else
sh Configure \
-des \
-Dinstallprefix="${EPREFIX}"'/usr' \
-Dinstallusrbinperl='n' \
"${myconf[@]}" \
|| die "Unable to configure"
fi
```
I can investigate the only remaining failure (a very minor one)
```
Failed 1 test out of 2534, 99.96% okay.
porting/checkcase.t
```
if we decide to go that way. If you prefer to keep the status quo, that's also fine, in which case just close this PR :)
next prev parent reply other threads:[~2021-09-25 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 14:51 [PR PATCH] " dkwo
2021-09-24 15:01 ` [wip/rfc] " leahneukirchen
2021-09-24 15:25 ` dkwo
2021-09-24 15:25 ` dkwo
2021-09-24 15:29 ` [PR PATCH] [Updated] " dkwo
2021-09-24 15:31 ` dkwo
2021-09-24 21:45 ` dkwo
2021-09-24 21:55 ` dkwo
2021-09-25 9:05 ` dkwo [this message]
2021-09-25 19:31 ` [PR PATCH] [Updated] " dkwo
2021-09-25 20:16 ` dkwo
2021-09-27 15:47 ` leahneukirchen
2021-09-30 15:50 ` [PR PATCH] [Updated] " dkwo
2021-09-30 15:54 ` dkwo
2021-09-30 15:55 ` dkwo
2022-01-02 8:33 ` dkwo
2022-01-02 8:33 ` [PR PATCH] [Closed]: " dkwo
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=20210925090505.qeSTt0R9GyzAFDhA8Tz4PQCXs-ExRO_pi7QRg6XbpSY@z \
--to=dkwo@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).