From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apr-util: update to 1.6.3
Date: Thu, 09 Mar 2023 22:09:07 +0100 [thread overview]
Message-ID: <20230309210907.1LUbAhTWcpMzMCPpNRZK6L42CiteEv6m3b_U8RG4HpQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42636@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/42636#issuecomment-1462820131
Comment:
The arm libtool package should be consistent with the x86_64 libtool package, I'm not sure why this change should be made for one but not the other (especially if that patch breaks building some packages like ntl).
If you need `LD=${LD:=ld}`, maybe you can sed libtool to XBPS_WRAPPERDIR and use that?
next prev parent reply other threads:[~2023-03-09 21:09 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:42 [PR PATCH] " klarasm
2023-03-06 22:44 ` [PR PATCH] [Updated] " klarasm
2023-03-06 22:50 ` klarasm
2023-03-06 22:55 ` klarasm
2023-03-07 0:28 ` klarasm
2023-03-07 1:01 ` [PR PATCH] [Updated] " klarasm
2023-03-07 1:07 ` klarasm
2023-03-09 16:39 ` klarasm
2023-03-09 17:04 ` klarasm
2023-03-09 17:11 ` klarasm
2023-03-09 17:14 ` [PR PATCH] [Updated] " klarasm
2023-03-09 18:28 ` paper42
2023-03-09 19:03 ` klarasm
2023-03-09 19:12 ` [PR PATCH] [Updated] " klarasm
2023-03-09 19:33 ` klarasm
2023-03-09 19:37 ` klarasm
2023-03-09 21:05 ` oreo639
2023-03-09 21:06 ` oreo639
2023-03-09 21:07 ` oreo639
2023-03-09 21:07 ` oreo639
2023-03-09 21:07 ` oreo639
2023-03-09 21:09 ` oreo639 [this message]
2023-03-09 21:10 ` oreo639
2023-03-09 21:54 ` [PR PATCH] [Updated] " klarasm
2023-03-09 22:04 ` klarasm
2023-03-09 22:04 ` klarasm
2023-05-15 16:46 ` [PR PATCH] [Updated] " klarasm
2023-05-15 16:46 ` klarasm
2023-05-15 16:53 ` klarasm
2023-08-04 10:00 ` dkwo
2023-08-04 10:42 ` oreo639
2023-08-04 10:42 ` oreo639
2023-08-04 10:43 ` oreo639
2023-08-04 10:44 ` oreo639
2023-08-04 10:44 ` oreo639
2023-08-04 10:47 ` oreo639
2023-08-04 10:47 ` oreo639
2023-08-04 10:49 ` oreo639
2023-08-04 10:50 ` oreo639
2023-08-04 10:51 ` oreo639
2023-08-04 10:57 ` klarasm
2023-08-04 11:18 ` oreo639
2023-08-04 11:18 ` oreo639
2023-08-04 11:20 ` klarasm
2023-08-04 11:21 ` klarasm
2023-08-04 11:22 ` oreo639
2023-08-04 11:22 ` oreo639
2023-08-04 11:23 ` oreo639
2023-08-04 11:24 ` oreo639
2023-08-04 13:07 ` dkwo
2023-08-08 19:57 ` oreo639
2023-08-08 20:02 ` oreo639
2023-08-08 20:03 ` oreo639
2023-08-08 20:10 ` oreo639
2023-08-08 22:26 ` klarasm
2023-08-08 22:28 ` oreo639
2023-08-08 22:29 ` oreo639
2023-08-08 22:30 ` oreo639
2023-08-08 22:30 ` klarasm
2023-08-08 22:31 ` [PR PATCH] [Updated] " klarasm
2023-08-08 22:38 ` klarasm
2023-08-08 22:43 ` oreo639
2023-08-08 22:46 ` oreo639
2023-08-08 22:47 ` oreo639
2023-08-08 22:47 ` oreo639
2023-08-08 22:48 ` oreo639
2023-08-08 22:50 ` [PR PATCH] [Updated] " klarasm
2023-08-08 22:55 ` klarasm
2023-08-17 21:43 ` [PR PATCH] [Updated] " klarasm
2023-08-17 21:50 ` klarasm
2023-08-19 18:27 ` Emru1
2023-08-20 7:04 ` oreo639
2023-08-22 18:20 ` [PR PATCH] [Merged]: " classabbyamp
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=20230309210907.1LUbAhTWcpMzMCPpNRZK6L42CiteEv6m3b_U8RG4HpQ@z \
--to=oreo639@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).