From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gnutls-3.2.20 doesn't compile anymore, probably conficting with installed libopts-devel
Date: Tue, 11 Nov 2014 21:13:00 -0000 [thread overview]
Message-ID: <54627BF3.7080605@cygwin.com> (raw)
In-Reply-To: <87mw7xlb71.fsf@leila.volkerzell.de>
On 2014-11-11 14:44, Dr. Volker Zell wrote:
> Older gnutls versions compiled fine with cygwin. Latest versions come
> with their own libopts source tree, which is newer than the latest
> cygwin version. I get the following error when trying to compile gnutls-3.2.20
>
> In file included from srptool-args.c:43:0:
> srptool-args.h:61:3: error: #error option template version mismatches autoopts/options.h header
> # error option template version mismatches autoopts/options.h header
> ^
> srptool-args.h:62:3: error: unknown type name 'Choke'
> Choke Me
I cannot reproduce this. Do you have both autogen and libopts-devel
installed? Also, are you using the autogen VPATH patch:
http://sourceforge.net/p/cygwin-ports/gnutls/ci/master/tree/3.2.18-autogen-vpath.patch
> Can we get a newer autogen package ?
I can do that, but that's not the problem here.
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-11-11 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 20:44 Dr. Volker Zell
2014-11-11 21:13 ` Yaakov Selkowitz [this message]
2014-11-12 8:50 ` Dr. Volker Zell
2014-11-12 8:58 ` Dr. Volker Zell
2014-11-12 16:37 ` Yaakov Selkowitz
2014-11-12 20:40 ` Dr. Volker Zell
2014-11-13 6:35 ` Yaakov Selkowitz
2014-11-13 9:34 ` Dr. Volker Zell
2014-11-13 11:22 ` Yaakov Selkowitz
2014-11-13 13:45 ` Dr. Volker Zell
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=54627BF3.7080605@cygwin.com \
--to=yselkowitz@cygwin.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).