Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Gack ... boring old nnimap and gmail problem again
Date: Wed, 11 Jan 2012 08:58:36 +0100	[thread overview]
Message-ID: <87aa5uisb7.fsf@tsdh.uni-koblenz.de> (raw)
In-Reply-To: <871ur73p1s.fsf@newsguy.com> (Harry Putnam's message of "Tue, 10 Jan 2012 22:18:07 -0500")

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

> I do compile myself. This was my ./configure command:
>
> ./configure  --with-xft  --with-x-toolkit=lucid 
>     --prefix=/usr/local/src/vcs/bzr/test

It might be that the configure script was generated before GnuTLS
support was integrated in emacs.  Please run

  make clean distclean
  ./autogen

and then again your usual configure & make procedure.  After having run
./configure, you can check if gnutls support has been picked up (and if
not, why) by checking config.log for a snippet like this:

--8<---------------cut here---------------start------------->8---
configure:11723: checking for gnutls >= 2.6.6
configure:11727: result: yes
configure:11731: checking LIBGNUTLS_CFLAGS
configure:11734: result:  
configure:11737: checking LIBGNUTLS_LIBS
configure:11740: result: -lgnutls  
configure:11777: checking for gnutls_certificate_set_verify_function
configure:11777: gcc -std=gnu99 -o conftest  -g -O2 -pthread -DQT_SHARED -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/libpng15 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/libdrm -I/usr/include/qt4/QtCore   -I/usr/include/ImageMagick   -pthread -DQT_SHARED -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/libdrm -I/usr/include/qt4/QtCore          -Wl,-znocombreloc  conftest.c -lgnutls   -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0   -lMagickWand -lMagickCore   -pthread -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lcairo -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0   -lX11 -lpthread   -ldbus-1 -lpthread -lrt   >&5 
configure:11777: $? = 0
configure:11777: result: yes
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo



  parent reply	other threads:[~2012-01-11  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 19:01 Harry Putnam
2012-01-10  9:35 ` Stefan Nobis
2012-01-10 10:28 ` Tassilo Horn
2012-01-11  3:18   ` Harry Putnam
2012-01-11  3:36     ` Harry Putnam
2012-01-11  7:58     ` Tassilo Horn [this message]
2012-01-11 13:08       ` Harry Putnam
2012-01-11 13:41         ` Ted Zlatanov
2012-01-11  9:13     ` Adam Sjøgren

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=87aa5uisb7.fsf@tsdh.uni-koblenz.de \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    --cc=reader@newsguy.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 NNTP newsgroup(s).