From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xbps-src fails with 'XBPS_CROSS_TRIPLET is not defined' when trying to cross-build same arch
Date: Wed, 14 Jun 2023 21:40:39 +0200 [thread overview]
Message-ID: <20230614194039.hisOm9IvtNW5ynXJ52EHcYVsKZM7W8jYLWPPZ5enoTs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13221@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Closed issue by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/13221
Description:
When *accidently* trying to cross-compile (for example with automation scripts) from one arch to the same it will error out with a non-descriptive error:
`XBPS_CROSS_TRIPLET is not defined`
I think it would be good to check if both `arch`s are equal and then error out displaying a msg that it's not allowed.
next prev parent reply other threads:[~2023-06-14 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 13:08 [ISSUE] xbps " voidlinux-github
2020-02-15 20:31 ` xbps-src " Anachron
2023-06-03 21:35 ` vincele
2023-06-14 19:40 ` Chocimier [this message]
2023-06-14 19:40 ` 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=20230614194039.hisOm9IvtNW5ynXJ52EHcYVsKZM7W8jYLWPPZ5enoTs@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).