unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: "Official" binary of Emacs-24.4 for MS-Windows
Date: Sat, 25 Oct 2014 15:27:01 +0200	[thread overview]
Message-ID: <CAH8Pv0i2ZDZ2p_nfbUkQvKvt=sX4KAFK84FwunHW3_hFQ5ZkZA@mail.gmail.com> (raw)
In-Reply-To: <83tx2s4bzf.fsf@gnu.org>

>> I've tried (for the first time) the "make install-strip" target from a
>> trunk build, and I've noticed something strange: the size of the
>> resulting stripped "emacs.exe" is ~ 16 MB, whereas the same file for
>> the 24.4 release (also stripped) is ~ 9 MB.
>>
>> Such big difference is strange, isn't it?
>
> I think it's expected.  You will see the same 7MB difference between
> the unstripped src/emacs.exe in the emacs-24 branch vs the trunk.

Between unstripped executables, the difference is close to 10 MB, but
ok, this seems expected.

>> Also, I've noticed this suspicious errors in the output of "make
>> install-strip", which don't appear in a "make install" from the same
>> build:
>
> Looks like some redirection snafu: for some reason, install-info is
> called with arguments taken from Make messages that announce entering
> and leaving directories.  Maybe it comes from this line:
>
>>    info_misc=`MAKELEVEL=0 make -s -C doc/misc echo-info`; \
>
> Looks like MAKELEVEL=0 doesn't work with your Make.  Try adding the
> "--no-print-directory" switch to the "make" command, and see if that
> helps.

Yes, it helps.  The install-info errors are gone with that switch.

> This sounds like bug #13962, but since we now require GNU Make on the
> trunk, I think it's OK to use --no-print-directory instead of the
> MAKELEVEL=0 trick.

Fine with me.  Thank you.

-- 
Dani Moncayo



  reply	other threads:[~2014-10-25 13:27 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 15:13 "Official" binary of Emacs-24.4 for MS-Windows Dani Moncayo
2014-10-24 15:17 ` Windows build pipeline - " Nic Ferrier
2014-10-24 15:42   ` Dani Moncayo
2014-10-24 15:55 ` Eli Zaretskii
2014-10-24 15:56   ` Dani Moncayo
2014-10-24 17:26     ` Eli Zaretskii
2014-10-24 18:03       ` Dani Moncayo
2014-10-24 19:29         ` Eli Zaretskii
2014-10-24 20:21           ` Dani Moncayo
2014-10-25  6:28             ` Eli Zaretskii
2014-10-25  8:00               ` Dani Moncayo
2014-10-25  8:11                 ` Eli Zaretskii
2014-10-25  8:39                   ` Dani Moncayo
2014-10-25  9:23                     ` Eli Zaretskii
2014-10-25  9:31                       ` Dani Moncayo
2014-10-25  9:37                         ` Eli Zaretskii
2014-10-25 11:08                           ` Dani Moncayo
2014-10-25 11:36                             ` Eli Zaretskii
2014-10-25 13:27                               ` Dani Moncayo [this message]
2014-10-30 15:04                                 ` Dani Moncayo
2014-10-30 15:58                                   ` Eli Zaretskii
2014-10-25  8:38                 ` Glenn Morris
2014-10-30 15:06                   ` Dani Moncayo
2014-10-30 15:25                     ` Glenn Morris
2014-11-10  5:34 ` Eli Zaretskii
2014-11-10  7:29   ` Dani Moncayo
2014-11-10  7:34     ` Dani Moncayo
2014-11-10 10:49     ` Eli Zaretskii
2014-11-12 12:02       ` Dani Moncayo
2014-11-12 13:59         ` Thorsten Jolitz
2014-11-12 14:02           ` Dani Moncayo
2014-11-12 15:44             ` Thorsten Jolitz
2014-11-12 17:39           ` Alexander Shukaev
2014-11-13  9:57             ` Thorsten Jolitz
2014-11-15 12:09         ` Dani Moncayo
2014-11-15 13:03           ` Eli Zaretskii
     [not found]           ` <<83egt4fwf4.fsf@gnu.org>
2014-11-15 14:53             ` Drew Adams
2014-11-15 15:31           ` Stefan Monnier

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='CAH8Pv0i2ZDZ2p_nfbUkQvKvt=sX4KAFK84FwunHW3_hFQ5ZkZA@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).