all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 20068@debbugs.gnu.org
Subject: bug#20068: 24.4.91; Too many warnings building Emacs
Date: Mon, 09 Mar 2015 20:31:08 -0400	[thread overview]
Message-ID: <co4mpt66cz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87mw3lhj53.fsf@moondust.localdomain> (N. Jackson's message of "Mon, 09 Mar 2015 19:59:36 -0300")


If you get that many warnings, you must be doing a bootstrap, which is
unnecessary and not the documented procedure for building (pre)releases.
Following the build instructions gets you 37 warnings, which should drop
to zero with Emacs 25.1 tarfiles where no lisp files should be recompiled.
So for pretests this issue is already nonexistent/solved.

If you bootstrap or build from a VCS checkout then yes, you get a lot of
warnings. History shows that no, we cannot meaningfully reduce the
number. New classes of warnings get added faster than the existing ones
can be removed. And in some cases the desire to be compatible with
multiple Emacs versions makes warnings inevitable (without excessive
jumping through hoops). We are all aware the warnings exist, I don't
think a bug report about it will make them go away.

Lisp compilation errors are never (good enough) platform specific and
can always be ignored by non-developers.





  reply	other threads:[~2015-03-10  0:31 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 [this message]
2015-03-10  5:45   ` Eli Zaretskii
2015-03-11 11:47     ` N. Jackson

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=co4mpt66cz.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=20068@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.