From: Kaushal Modi <kaushal.modi@gmail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Noam Postavsky <npostavs@users.sourceforge.net>,
wingo@igalia.com, 25061@debbugs.gnu.org, ludo@gnu.org,
p.stephani2@gmail.com, michael.albinus@gmx.de, larsi@gnus.org
Subject: bug#25061: consider adding %COMPAT to default gnutls priority string
Date: Tue, 19 Dec 2017 22:00:34 +0000 [thread overview]
Message-ID: <CAFyQvY02a=ZZZyzH3FSkOYSAPDpwzVhxUR9Qa3QO9-2gTwEG+w@mail.gmail.com> (raw)
In-Reply-To: <87shc6k3tf.fsf@lifelogs.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Tue, Dec 19, 2017 at 12:47 PM Ted Zlatanov <tzz@lifelogs.com> wrote:
>
> Please try again, I added a fix that should remove %DUMBFW if it's not
> supported.
>
Hi Ted,
I couldn't test the fix on my local machine because I cannot recreate the
problem there.
So I was waiting for the emacs-26 branch build to finish on the Travis CI
set up by Noam.. but the build itself failed:
https://travis-ci.org/npostavs/emacs-travis/jobs/318857869
CC lastfile.o
CCLD temacs
gnutls.o: In function `Fgnutls_available_p':
gnutls.c:(.text+0x105d): undefined reference to `gnutls_ext_get_name'
collect2: error: ld returned 1 exit status
make[1]: *** [temacs] Error 1
make[1]: Leaving directory `/tmp/emacs-emacs-26/src'
make: *** [src] Error 2
make: Leaving directory `/tmp/emacs-emacs-26'
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1422 bytes --]
next prev parent reply other threads:[~2017-12-19 22:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 10:24 bug#25061: consider adding %COMPAT to default gnutls priority string Andy Wingo
2016-12-01 18:32 ` Ted Zlatanov
2016-12-01 20:25 ` Ludovic Courtès
2016-12-01 21:44 ` Ted Zlatanov
2017-01-24 22:48 ` Lars Ingebrigtsen
2017-01-30 8:01 ` Ludovic Courtès
2017-02-10 15:51 ` Andy Wingo
2017-02-13 16:04 ` Ted Zlatanov
2017-09-02 13:49 ` Eli Zaretskii
2017-09-06 19:32 ` Ted Zlatanov
2017-09-07 7:18 ` Michael Albinus
2017-09-14 21:11 ` Ted Zlatanov
2017-09-15 6:05 ` Eli Zaretskii
2017-12-02 17:36 ` Eli Zaretskii
2017-12-09 23:50 ` Ted Zlatanov
2017-12-10 7:04 ` Eli Zaretskii
2017-12-10 13:29 ` Ted Zlatanov
2017-12-10 14:12 ` Eli Zaretskii
2017-12-11 15:03 ` Ted Zlatanov
2017-12-11 15:40 ` Eli Zaretskii
2017-12-15 4:18 ` Ted Zlatanov
2017-12-16 23:25 ` Philipp Stephani
2017-12-16 23:34 ` Ted Zlatanov
2017-12-17 3:39 ` Eli Zaretskii
2017-12-17 15:17 ` Eli Zaretskii
2017-12-19 17:46 ` Ted Zlatanov
2017-12-17 17:52 ` Philipp Stephani
2017-12-10 9:31 ` Michael Albinus
2017-12-18 17:16 ` Kaushal Modi
2017-12-18 19:52 ` Philipp Stephani
2017-12-19 17:47 ` Ted Zlatanov
2017-12-19 22:00 ` Kaushal Modi [this message]
2017-12-20 1:08 ` Ted Zlatanov
2017-12-20 11:41 ` Robert Pluim
2017-12-20 16:09 ` Eli Zaretskii
2017-12-21 13:20 ` Kaushal Modi
2017-12-21 13:26 ` Ted Zlatanov
2017-12-20 11:48 ` Kaushal Modi
2017-12-20 12:54 ` Andy Moreton
2017-12-20 13:16 ` Andy Moreton
2017-12-20 16:19 ` Eli Zaretskii
2017-12-20 16:38 ` Andy Moreton
2017-12-21 1:15 ` Ted Zlatanov
2017-12-21 1:39 ` Ted Zlatanov
2017-12-21 8:30 ` Robert Pluim
2017-12-21 13:12 ` Ted Zlatanov
2017-12-21 16:20 ` Eli Zaretskii
2017-12-21 10:54 ` Andy Moreton
2017-12-21 16:26 ` Eli Zaretskii
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='CAFyQvY02a=ZZZyzH3FSkOYSAPDpwzVhxUR9Qa3QO9-2gTwEG+w@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=25061@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=ludo@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=npostavs@users.sourceforge.net \
--cc=p.stephani2@gmail.com \
--cc=tzz@lifelogs.com \
--cc=wingo@igalia.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.
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.