From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: A Cleaner Build
Date: Thu, 17 Mar 2011 22:05:39 +0100 [thread overview]
Message-ID: <m3aagt5ufw.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87wrjxtqjp.fsf@randomsample.de>
David Engster <deng@randomsample.de> writes:
> 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.
Yup. Hm...
> Yeah well. That's what I thought. I fixed that now.
Great!
> 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').
Right. I'll switch on the "fail on warnings" thing in dgnushack. Or
should we have a special build target for that? Like "make warn"? I
guess so. I've now added a "warn" target in the makefile, but it just
does the same as "all" for now. But feel free to switch the target to
"make warn" on the buildbot, and I'll make the "warn" target do the
right thing later.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-03-17 21:05 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
2011-03-17 21:05 ` Lars Magne Ingebrigtsen [this message]
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=m3aagt5ufw.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).