unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: 20068-done@debbugs.gnu.org
Subject: bug#20068: 24.4.91; Too many warnings building Emacs
Date: Wed, 11 Mar 2015 08:47:58 -0300	[thread overview]
Message-ID: <87lhj3ycup.fsf@moondust.localdomain> (raw)
In-Reply-To: <83egox5rs8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Mar 2015 07:45:59 +0200")

At 02:45 -0300 on Tuesday 2015-03-10, Eli Zaretskii wrote:

>> From: Glenn Morris <rgm@gnu.org>
>> 
>> If you get that many warnings, you must be doing a bootstrap
>
> No, he isn't.  A small number of Lisp files are byte-compiled when
> building a release tarball (this was fixed by you on master, I think),
> and the files he mentions are those.

Glen is right, actually. I neglected to read the README and INSTALL
files (Sorry. I've read them now.) and, instead, I just used my usual
build recipe which includes a bootstrap.

Rebuilding with a bare make after a fresh extraction from the tarball, I
get 37 warnings which is much less overwhelming than than 158!

>> Lisp compilation errors are never (good enough) platform specific and
>> can always be ignored by non-developers.
>
> Indeed, in this case I looked at the reported warnings and saw nothing
> grave there, I'm quite sure I saw the same warnings when I built the
> pretest.

Well if nothing can reasonably be done about any of the warnings that's
unfortunate, of course, since it cheapens their value, but it's just one
of those things I suppose. I'm closing this.

Thank you for Emacs.






      reply	other threads:[~2015-03-11 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 22:59 bug#20068: 24.4.91; Too many warnings building Emacs N. Jackson
2015-03-10  0:31 ` Glenn Morris
2015-03-10  5:45   ` Eli Zaretskii
2015-03-11 11:47     ` N. Jackson [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhj3ycup.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=20068-done@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).