From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build: other output Date: Mon, 17 Jun 2019 16:05:05 +0200 Message-ID: References: <83zhn6zkgf.fsf@gnu.org> <83a7eo9nsh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="45136"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 17 16:06:46 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hcsHW-000BcT-6E for ged-emacs-devel@m.gmane.org; Mon, 17 Jun 2019 16:06:46 +0200 Original-Received: from localhost ([::1]:47832 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcsHU-0000xN-Kt for ged-emacs-devel@m.gmane.org; Mon, 17 Jun 2019 10:06:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38192) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcsG0-0000kK-92 for emacs-devel@gnu.org; Mon, 17 Jun 2019 10:05:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hcsFy-0005JM-CE for emacs-devel@gnu.org; Mon, 17 Jun 2019 10:05:11 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:41388) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hcsFx-0005FD-U2 for emacs-devel@gnu.org; Mon, 17 Jun 2019 10:05:10 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=stories) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hcsFt-0005oM-Hd for emacs-devel@gnu.org; Mon, 17 Jun 2019 16:05:07 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEUHBgXW1tZkY2IYFxYF AwMKCAdn2ceNAAACZ0lEQVQ4jU2UTW7jMAyFido6gBR0X0vw3hbLvYEqe44V3v8q8yg7nVFTBdZn /j1SIVK7Vjc1nZ/vJyIj68yCDc+thQsw+ZZzZnYopE9T9Vfxn6OvFFORvRjcuVknO3NeBoq51GKE 83aETn1PufpxWVLpQkQADYCX5CapGDY4usBhxAVhgTJA9PAEZzNAXyl0kLL9ifFhPG2v2YMQiyKx vHy2Halx51VnIgCvxoM/6I8nxozEyEKgwNY93bTuvos82AL+iKoZjlCC4yKGnN0LaQ12elirOSbV gAQGCP7ZI7ToCPU9/3zaIEQBup9woUGW+DWH1Uyqg6EyTfxqanmlA08Znv28s1bh0D7wsueve3yM fuiJV8KTP1LNW3uGnisP4IUklyouaYPvDlkdQCposY2WPMhbi/KFPOMa13mGVYxfDUKNuKQ0h5q+ 27GXKcbt1Q4aVuSrFmnPpXBFgVfFNzgXzEmFslncz5DcG0lnLLxAx1zYg2q4QfuA3NYFBsJK18gB zMd0z0+UcRJuUDX8D2xM7QAr+QhhUCLEUm/rbfFFOQuGEPXae9gZ4Oe7hVrdz/kPdIDDx2iA/gtw DXwhDYFyPZe3Ix7gOMI03h0bOt1LYZJA7Zj0bXdZFHSwozWtKwYWV0WuCThzqmQzOhDa62gULrMu veRCrq9SQ3Z0LTcpMV/fFcJWXAVov3qMeAOokR8AvtaJx8EAfK8y7nQw4ZrorjRM5ZKKaBOBa7pr wowyq19OpId48RfcQ4yhaZwfHGk+/JoiV72aBEV7Zlj4D4Ff7G1oMcMVWRUA+LyWmuAXBpVrPyH0 Xwhi31X7JUg5AAAAAElFTkSuQmCC In-Reply-To: (Lars Ingebrigtsen's message of "Mon, 17 Jun 2019 15:30:44 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237787 Archived-At: We've only got four Warning: lines left, but there's some other irregular stuff being output, and I wonder whether we could reformat or remove or fix some of these things. (The point here is, of course, that when you're working on Emacs and then compile it, if you see something that looks like an error you know you've done something wrong.) There's 38 lines on stderr, so perhaps that's a good place to start. eieio.el: =E2=80=98object-print=E2=80=99 is an obsolete generic function (a= s of 26.1); use =E2=80=98cl-print-object=E2=80=99 instead. These are output by cl-defmethod/cl-defgeneric, and we're defining an (obsolete) fallback method, so we should suppress this warning. Do we need a new mechanism or do we have something to cover this? --- *Warning* default value of <> tokens changed to QUERY, was NULL_TO= KEN *Warning* default value of <> tokens changed to TRUE, was QUERY *Warning* default value of <> tokens changed to FALSE, was TRUE Grammar in javascript.el contains 2 useless nonterminals and 4 useless rules Grammar in js-wy.el contains 2 useless nonterminals and 4 useless rules Grammar in python-wy.el contains 2 useless nonterminals and 3 useless rules Grammar in python-wy.el contains 4 shift/reduce conflicts Grammar in python.el contains 2 useless nonterminals and 3 useless rules Grammar in python.el contains 4 shift/reduce conflicts These are from cedet, and are warning about grammars containing... useless rules? Perhaps this is more useful at run-time than at compile time? --- Loading /home/larsi/src/emacs/trunk/lisp/international/uni-name.el (source)= ... Hm... a "Loading" in the middle here? Does anybody know why? --- 10000 entries 20000 entries 30000 entries 40000 entries 50000 entries 60000 entries I thought these weren't very useful because they zipped by on my screen, but people protested. Could we perhaps reformat them so they look more like other compilation output: ELC vc/vc-svn.elc ELC progmodes/cc-defs.elc GEN 10000 entries GEN 20000 entries Or something? --- latin-ltx: 1535 rules (+ 0 conflicts)! Uhm... That doesn't seem very useful to me -- only output that if there are any conflicts? --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no