From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: A Cleaner Build
Date: Thu, 17 Mar 2011 21:55:54 +0100 [thread overview]
Message-ID: <87wrjxtqjp.fsf@randomsample.de> (raw)
In-Reply-To: <m3wrjxr2ux.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 17 Mar 2011 19:58:14 +0100")
Lars Magne Ingebrigtsen writes:
> David Engster <deng@randomsample.de> writes:
>
>> Lars Magne Ingebrigtsen writes:
>>> I've started tackling the warnings in the Gnus build. But here's one I
>>> don't understand:
>>>
>>> Compiling /home/larsi/pgnus/lisp/gnus-gravatar.el...
>>> While compiling toplevel forms in file
>>> /home/larsi/pgnus/lisp/gnus-gravatar.el:
>>> !! Symbol's function definition is void ((locate-user-emacs-file))
>>
>> Isn't that a real error?
>>
>> Anyway, I don't see that one in the stdio from
>
> No, it's from when I'm trying to build Gnus with XEmacs here. :-)
Yes, I figured that from /home/larsi (unless you hacked the buildbot,
that is). :-) locate-user-emacs-file existed in FSF Emacs 21. I have no
idea where that's coming from. But I'm guessing it's some quirk in your
installation.
> And I'm not getting that when compiling with Emacs 24 here. Has your
> Emacs 24 been built without X support?
It's a server; who needs X there? ;-)
Yeah well. That's what I thought. I fixed that now.
The last warning I see is from Emacs22:
In toplevel form:
message.el:1923:20:Warning: `make-variable-buffer-local' should be called at
toplevel
Otherwise it looks nice&clean, at least for the warnings enabled in
dgnushack (the buildbot does a normal 'make', not 'make warn').
-David
next prev parent reply other threads:[~2011-03-17 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 18:42 Lars Magne Ingebrigtsen
2011-03-17 18:50 ` David Engster
2011-03-17 18:58 ` Lars Magne Ingebrigtsen
2011-03-17 19:00 ` Lars Magne Ingebrigtsen
2011-03-17 20:55 ` David Engster [this message]
2011-03-17 21:05 ` Lars Magne Ingebrigtsen
2011-03-17 21:11 ` David Engster
2011-03-17 21:30 ` Lars Magne Ingebrigtsen
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=87wrjxtqjp.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.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.
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).