From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: pinfo build fails with undefined macro: AM_INTL_SUBDIR
Date: Wed, 12 Apr 2023 09:29:38 +0200 [thread overview]
Message-ID: <875ya1v9r1.fsf@Rainer.invalid> (raw)
In-Reply-To: <hdsb3itklqdtqmt8i8jv4qqssf41odud89@4ax.com> (Andrew Schulman via Cygwin-apps's message of "Tue, 11 Apr 2023 19:51:26 -0400")
Andrew Schulman via Cygwin-apps writes:
> Thanks. I tried several different values of WANT_AUTOCONF and WANT_AUTOMAKE, but
> they didn't help. From what I can tell, AM_INTL_SUBDIR is just gone from
> automake now.
It never was there, this is a bug in gettext 0.21.
> So I removed the call to AM_INTL_SUBDIR, and that build problem is fixed. Anyway
> thanks for pointing me in a direction.
The correct solution seems to be to add 'external' to the arguments of AM_GNU_GETTEXT.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2023-04-12 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 13:21 Andrew Schulman
2023-04-11 14:32 ` Corinna Vinschen
2023-04-11 23:51 ` Andrew Schulman
2023-04-12 7:29 ` Achim Gratz [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=875ya1v9r1.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).