From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: gnutls error
Date: Sat, 15 Jul 2017 18:25:47 +0300 [thread overview]
Message-ID: <83tw2den7o.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0ihwTV30tCj0SgviupSO-vaUD96rFTxvPEbNq=X_hhZNw@mail.gmail.com> (message from Dani Moncayo on Sat, 15 Jul 2017 17:06:52 +0200)
> From: Dani Moncayo <dmoncayo@gmail.com>
> Date: Sat, 15 Jul 2017 17:06:52 +0200
> Cc: Emacs development discussions <emacs-devel@gnu.org>
>
> > These errors make no sense, the stuff they complain about is defined
> > right there in fns.c.
> >
> > How did you build Emacs? With what sequence of commands?
>
> >From the root of the source tree:
> $ git pull
> $ ./autogen.sh
>
> >From an empty directory:
> $ path-to-source-root/configure
> $ make
>
> (BTW, I've just repeated the above, with the same result)
What does this produce:
fgrep Qiv_auto src/globals.h
next prev parent reply other threads:[~2017-07-15 15:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 9:49 gnutls error Colin Baxter
2017-07-15 10:07 ` Colin Baxter
2017-07-15 11:05 ` Eli Zaretskii
2017-07-15 11:14 ` Dani Moncayo
2017-07-15 11:33 ` Eli Zaretskii
2017-07-15 15:06 ` Dani Moncayo
2017-07-15 15:10 ` Dani Moncayo
2017-07-15 15:25 ` Eli Zaretskii [this message]
2017-07-15 19:58 ` Dani Moncayo
2017-07-16 14:30 ` Eli Zaretskii
2017-07-16 16:02 ` Dani Moncayo
2017-07-16 16:19 ` Dani Moncayo
2017-07-16 17:15 ` Eli Zaretskii
2017-07-15 11:53 ` Colin Baxter
2017-07-15 12:42 ` Masaru Nomiya
2017-07-15 13:41 ` Colin Baxter
2017-07-15 13:53 ` Masaru Nomiya
2017-07-15 13:55 ` Eli Zaretskii
2017-07-15 14:07 ` Masaru Nomiya
2017-07-15 14:37 ` Eli Zaretskii
2017-07-15 15:18 ` Masaru Nomiya
2017-07-15 16:17 ` GnuTLS build-time configuration Paul Eggert
2017-07-15 16:42 ` Colin Baxter
2017-07-16 0:12 ` Paul Eggert
2017-07-15 18:27 ` Ted Zlatanov
2017-07-16 0:16 ` Paul Eggert
2017-07-17 14:22 ` Ted Zlatanov
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=83tw2den7o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.