From: Bill Zissimopoulos <billziss@navimatics.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Id3tag and lame packages?
Date: Thu, 22 Sep 2016 21:06:00 -0000 [thread overview]
Message-ID: <D4099259.B47D%billziss@navimatics.com> (raw)
In-Reply-To: <76c024dd-6df1-6f5c-874b-bc8c09a209d7@cygwin.com>
On 9/22/16, 12:37 PM, Yaakov Selkowitz wrote:
>lame cannot be shipped however
>for legal reasons, but it's easy to build yourself with cygport:
>
>https://github.com/cygwinports-extras/lame
Alas this fails:
$ cygport lame.cygport compile
>>> Compiling lame-3.99.5-2.x86_64
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: configure.in: not using Gettext
autoreconf-2.69: running: aclocal --force
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 644.
configure.in:396: warning: macro `AM_PATH_GTK' not found in library
autoreconf-2.69: configure.in: tracing
autoreconf-2.69: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 644.
configure.in:396: warning: macro `AM_PATH_GTK' not found in library
autoreconf-2.69: running: /usr/bin/autoconf-2.69 --force
configure.in:396: error: possibly undefined macro: AM_PATH_GTK
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf-2.69: /usr/bin/autoconf-2.69 failed with exit status: 1
*** ERROR: autoreconf failed
Bill
next prev parent reply other threads:[~2016-09-22 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 19:37 Bill Zissimopoulos
2016-09-22 19:47 ` Yaakov Selkowitz
2016-09-22 20:55 ` Bill Zissimopoulos
2016-09-22 21:06 ` Bill Zissimopoulos [this message]
2016-09-22 21:58 ` Yaakov Selkowitz
2016-09-22 22:13 ` Bill Zissimopoulos
2016-09-23 7:40 ` David Stacey
2016-09-23 20:50 ` Bill Zissimopoulos
2016-09-23 7:50 ` Csaba Raduly
2016-09-23 8:35 ` Bill Zissimopoulos
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=D4099259.B47D%billziss@navimatics.com \
--to=billziss@navimatics.com \
--cc=cygwin@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).