From: Tassilo Horn <tsdh@gnu.org>
To: Erik Colson <eco@ecocode.net>
Cc: "ding\@gnus.org" <ding@gnus.org>
Subject: Re: error since upgraded to 24.3 and gnus from git
Date: Wed, 13 Mar 2013 17:35:37 +0100 [thread overview]
Message-ID: <874ngfcl5y.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m0obenphil.fsf@ecocode.net> (Erik Colson's message of "Wed, 13 Mar 2013 14:16:02 +0100")
Erik Colson <eco@ecocode.net> writes:
Hi Erik,
> Thanks for the info. I'll try that. However I narrowed the thing
> down, using git bisect, to the commit 04580ac401 which is the one
> preceding the commit I went back to.
>
> But, as I went through :
>
> make clean && ./configure && make
>
> several times to find the error causing commit, I don't think it can
> be related to a configure error..
>
> Maybe it's related to a group-name or something else, but my lisp
> isn't good enough to debug this thing without help.
Very unlikely that a void-function error could be caused by that.
I still think it's a configure problem. When you run make, it says
something like
cd lisp && make EMACS="emacs-24" lispdir="/usr/share/emacs/site-lisp/gnus" all
What's the value of EMACS? And is that the same emacs you use for
running gnus?
Bye,
Tassilo
next prev parent reply other threads:[~2013-03-13 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:08 Erik Colson
2013-03-13 11:29 ` Erik Colson
2013-03-13 12:29 ` Tassilo Horn
2013-03-13 13:16 ` Erik Colson
2013-03-13 16:35 ` Tassilo Horn [this message]
2013-03-13 19:17 ` Erik Colson
2017-03-25 0:23 ` dovecot X-MAILBOX and X-REAL-UID support in nnimap ? Erik Colson
2013-03-13 16:30 ` error since upgraded to 24.3 and gnus from git Wolfgang Jenkner
2013-03-13 19:19 ` Erik Colson
2013-03-13 19:41 ` Wolfgang Jenkner
2013-03-13 21:37 ` Erik Colson
2013-03-14 7:05 ` Tassilo Horn
2013-03-14 7:43 ` Erik Colson
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=874ngfcl5y.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=eco@ecocode.net \
/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).