From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: gnutls status
Date: Sat, 05 Mar 2011 08:46:13 -0600 [thread overview]
Message-ID: <87aah9zkui.fsf@lifelogs.com> (raw)
In-Reply-To: <m3ei6lsuek.fsf@quimbies.gnus.org>
On Sat, 05 Mar 2011 12:01:39 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Regenerating "configure" failed for me. I get this error at the end:
>>
>> ./configure: line 12620: gl_ASSERT_NO_GNULIB_POSIXCHECK: command not found
>> ./configure: line 12621: gl_ASSERT_NO_GNULIB_TESTS: command not found
>> ./configure: line 12622: gl_INIT: command not found
>> checking for lstat... yes
>> ./configure: line 12648: syntax error near unexpected token `lstat'
>> ./configure: line 12648: `gl_SYS_STAT_MODULE_INDICATOR(lstat)'
LMI> I tried applying your patch to configure.in, and it worked for me.
LMI> Here's the output from around the lstat check:
LMI> checking for working GNU getopt function... yes
LMI> checking whether getenv is declared... yes
LMI> checking for lstat... yes
LMI> checking for alarm... yes
Something is broken in my autoconf setup at home, because the exact same
configure.in worked on another machine (same Ubuntu 10.10 setup!)
yesterday. Weird.
Anyhow, since GnuTLS 2.10 is not available even in Ubuntu 10.10, I'm
working on a way to control the verification with the GnuTLS
verification flags. It's not as good as a verification callback but it
will be more useful for the vast majority of people right now. I hope
to have something ready this weekend.
Ted
prev parent reply other threads:[~2011-03-05 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 17:29 Julien Danjou
2010-11-26 0:28 ` Lars Magne Ingebrigtsen
2010-11-26 12:13 ` Ted Zlatanov
2010-11-26 12:51 ` Julien Danjou
2010-11-26 15:02 ` Stefan Monnier
2010-11-26 15:56 ` Julien Danjou
2010-11-26 18:42 ` Stefan Monnier
2010-11-27 9:36 ` Julien Danjou
2010-11-27 14:28 ` Stefan Monnier
2010-11-28 9:55 ` Lars Magne Ingebrigtsen
2010-11-26 14:10 ` Lars Magne Ingebrigtsen
2010-11-27 14:18 ` Lars Magne Ingebrigtsen
2010-11-27 14:40 ` Lars Magne Ingebrigtsen
2010-11-27 15:31 ` Lars Magne Ingebrigtsen
2010-11-27 16:04 ` Lars Magne Ingebrigtsen
2010-11-27 16:37 ` Steinar Bang
2010-11-27 16:41 ` Lars Magne Ingebrigtsen
2010-11-27 16:59 ` Lars Magne Ingebrigtsen
2010-11-27 17:33 ` Dan Christensen
2010-11-27 17:36 ` Lars Magne Ingebrigtsen
2010-11-27 17:42 ` Lars Magne Ingebrigtsen
2010-11-28 2:36 ` Automatic STARTTLS upgrades (was: gnutls status) Lars Magne Ingebrigtsen
2010-11-28 12:28 ` Automatic STARTTLS upgrades Lars Magne Ingebrigtsen
2010-11-28 13:34 ` Lars Magne Ingebrigtsen
2010-12-14 22:59 ` gnutls status Ted Zlatanov
2011-03-01 21:52 ` Ted Zlatanov
2011-03-05 11:01 ` Lars Magne Ingebrigtsen
2011-03-05 14:46 ` Ted Zlatanov [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=87aah9zkui.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).