From: lfdebrux <lfdebrux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cannot cross-compile gettext
Date: Sun, 02 Jan 2022 19:13:10 +0100 [thread overview]
Message-ID: <20220102181310.xcFLUBt-Td05e6k_M2XgpcqVW-yrSRVm8t915okRirA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34810@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
New comment by lfdebrux on void-packages repository
https://github.com/void-linux/void-packages/issues/34810#issuecomment-1003754647
Comment:
The step to run `autoreconf -fi` was added back in 2013 for version 0.18.3 of gettext:
https://github.com/void-linux/void-packages/commit/17f6ad8b9c9319c46820941e7fbae3f73ddcb20a
There isn't and detail in the commit message why running autoreconf is needed, I` tried googling 'gettext autoreconf' but couldn't find anything relevant. Googling 'gettext cross-compile' also didn't suggest that autoreconf is needed. There's also nothing about in the package `INSTALL` doc, either [then](https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=INSTALL;h=671b157a6429121883c370dbfd80f4b09217cb26;hb=147dbca63d56e784ae0bfdf4e8174c110c384ec6) or [now](https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=INSTALL;h=671b157a6429121883c370dbfd80f4b09217cb26;hb=eb83efc3b58d690d444da0b82c3ecf36a54f28ac).
next prev parent reply other threads:[~2022-01-02 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 18:06 [ISSUE] " lfdebrux
2022-01-02 18:13 ` lfdebrux [this message]
2022-01-02 18:13 ` lfdebrux
2022-01-02 18:33 ` ericonr
2022-01-03 18:20 ` lfdebrux
2022-01-03 19:50 ` ericonr
2022-04-17 17:34 ` [ISSUE] [CLOSED] " paper42
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=20220102181310.xcFLUBt-Td05e6k_M2XgpcqVW-yrSRVm8t915okRirA@z \
--to=lfdebrux@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).