unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: gnutls error
Date: Sat, 15 Jul 2017 17:06:52 +0200	[thread overview]
Message-ID: <CAH8Pv0ihwTV30tCj0SgviupSO-vaUD96rFTxvPEbNq=X_hhZNw@mail.gmail.com> (raw)
In-Reply-To: <83379yexyx.fsf@gnu.org>

On Sat, Jul 15, 2017 at 1:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Dani Moncayo <dmoncayo@gmail.com>
>> Date: Sat, 15 Jul 2017 13:14:35 +0200
>>
>> I've tried to build the current version of the master branch on
>> Ubuntu-GNOME 17.04; it fails this way:
>>
>> [...]
>>   CC       floatfns.o
>>   CC       fns.o
>> In file included from ../../repo/src/fns.c:30:0:
>> ../../repo/src/fns.c:4748:34: error: ‘Fsecure_hash_algorithms’
>> undeclared here (not in a function)
>>  DEFUN ("secure-hash-algorithms", Fsecure_hash_algorithms,
>>                                   ^
>> ../../repo/src/lisp.h:2925:26: note: in definition of macro ‘DEFUN’
>>         { .a ## maxargs = fnname },     \
>>                           ^~~~~~
>> ../../repo/src/fns.c:4748:34: warning: no previous prototype for
>> ‘Fsecure_hash_algorithms’ [-Wmissing-prototypes]
>>  DEFUN ("secure-hash-algorithms", Fsecure_hash_algorithms,
>>                                   ^
>> ../../repo/src/lisp.h:2927:16: note: in definition of macro ‘DEFUN’
>>     Lisp_Object fnname
>>                 ^~~~~~
>> ../../repo/src/fns.c: In function ‘extract_data_from_object’:
>> ../../repo/src/fns.c:4928:24: error: ‘Qiv_auto’ undeclared (first use
>> in this function)
>>    else if (EQ (object, Qiv_auto))
>>                         ^~~~~~~~
>> ../../repo/src/fns.c:4928:24: note: each undeclared identifier is
>
> 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)

>  Are you
> sure your Git clone is up to date with upsteam?

I think so. "git log -1" gives here this:
------------------------------------------------
commit b30ee0c9225bad6e3fd0b511a6c5d9a64b8fd66a
Author: Eli Zaretskii <eliz@gnu.org>
Date:   Sat Jul 15 16:54:12 2017 +0300

    Avoid link errors with older versions of GnuTLS

    * src/gnutls.c (Fgnutls_ciphers, gnutls_symmetric_aead)
    (Fgnutls_macs, Fgnutls_digests): Conditionally compile code that
    calls GnuTLS functions which might be unavailable in older
    versions of GnuTLS.
------------------------------------------------

-- 
Dani Moncayo



  reply	other threads:[~2017-07-15 15:06 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 [this message]
2017-07-15 15:10         ` Dani Moncayo
2017-07-15 15:25         ` Eli Zaretskii
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8Pv0ihwTV30tCj0SgviupSO-vaUD96rFTxvPEbNq=X_hhZNw@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).