From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Using pkgconf instead of pkg-config
Date: Sat, 26 Jun 2021 21:56:27 +0200 [thread overview]
Message-ID: <20210626195627.hsqphHhmC6JEIseXvrqP_kdp5V4k7SxU_ydXkCAKL1c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-3391@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/issues/3391#issuecomment-869053910
Comment:
@ericonr OK, seems like there are many packages which will be broken by `pkgconf`:
>this massively breaks most packages cross compilation. That behavior is not in line with the spec.
It would be nice tho either to fix `pkgconf` to make it match the spec in this aspect or to alter `./xbps-src` to not to rely on this behaviour. But someone has to do this dirty job :( Certainly, not anytime soon.
P. S. Arch Linux has been using `pkgconf` for 3 years, but they don't have to support multiple architectures (Arch is x86_64/i686 only), so their experience isn't applicable to Void.
prev parent reply other threads:[~2021-06-26 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-3391@inbox.vuxu.org>
2020-04-22 20:31 ` ericonr
2020-04-22 20:50 ` Cogitri
2020-04-23 17:19 ` ericonr
2021-02-15 5:49 ` [ISSUE] [CLOSED] " ericonr
2021-06-26 19:39 ` Logarithmus
2021-06-26 19:48 ` ericonr
2021-06-26 19:54 ` Logarithmus
2021-06-26 19:56 ` Logarithmus
2021-06-26 19:56 ` Logarithmus [this message]
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=20210626195627.hsqphHhmC6JEIseXvrqP_kdp5V4k7SxU_ydXkCAKL1c@z \
--to=logarithmus@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).