From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: lftp 4.7.4 build fails with bad gettext version
Date: Wed, 16 Nov 2016 18:37:00 -0000 [thread overview]
Message-ID: <779p2c926cu5mrbcnqud43v2mudstmunb3@4ax.com> (raw)
Using cygport with no custom src_build function and
CYGCONF_ARGS="--with-openssl --enable-packager-mode", the build fails with
a mysterious message about a mismatched gettext version:
ASchulma@LZ77E1AASCHULMA ~/d/c/lftp> cygport lftp.cygport build
>>> Compiling lftp-4.7.4-1.x86_64
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: running: /usr/bin/autopoint -V 0.19.8.1 --force
autopoint: warning: Version mismatch: specified -V 0.19.8.1 but the package
uses gettext version 0.15. Forcibly upgrading to 0.19.8.1
autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.ac
file requires the infrastructure from gettext-0.19.8.1 but
this version
is older. Please upgrade to gettext-0.19.8.1 or newer.
autopoint: *** Stop.
autoreconf-2.69: /usr/bin/autopoint failed with exit status: 1
*** ERROR: autoreconf failed
So it says it wants gettext 0.19.8.1, but "the package uses gettext version
0.15". But I have gettext 0.19.8.1 installed:
ASchulma@LZ77E1AASCHULMA ~/d/c/lftp> cygcheck -c gettext
Cygwin Package Information
Package Version Status
gettext 0.19.8.1-2 OK
Does anyone know what the problem is here?
The last time I built lftp 4.7.3 it worked fine, but now the build of that
fails too, with the same error as above. So this seems to be caused by
autoconf, gettext, or something else in the Cygwin build environment,
rather than by lftp.
Thanks,
Andrew
next reply other threads:[~2016-11-16 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 18:37 Andrew Schulman [this message]
2016-11-18 17:16 ` Ken Brown
2016-11-23 23:39 ` Andrew Schulman
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=779p2c926cu5mrbcnqud43v2mudstmunb3@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).