unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: limit native compilation - how
Date: Sun, 16 Jan 2022 15:48:44 +0200	[thread overview]
Message-ID: <83pmoryeo3.fsf@gnu.org> (raw)
In-Reply-To: <86h7a37qzf.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de)

> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
> Cc: help-gnu-emacs@gnu.org
> Date: Sun, 16 Jan 2022 14:24:52 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The contents of the native-lisp/ directory doesn't change once Emacs
> > is built.
> 
> Really, please see below, could it be you meant perhaps the preloaded/
> folder? (Just guessing.)

No, I meant the entire native-lisp/28.0.91-xxxxx directory (of which
there should be just one when you build a single version for a single
configuration).

> 
> > If you cannot figure this out, compare the contents of the two
> > native-lisp/ directories.
> 
> machine 105 MB:
> |- native-lisp/
>    |- 28.0.91-59ee6325/
>    |  |- Some .eln files
>    |  |- preloaded/
>    |     | 45 MB .eln
>    |- 28.0.91-aa40abb8/
>       | Some other .eln files
>       |- preloaded/
>          |- 45 Mb .eln files
> 
> machine 55 MB:
> |- native-lisp/
>    |- 28.0.91-59ee6325/
>    |- Some .eln files
>       |- preloaded/
>          | 45 MB .eln files
> 
> Might the differences come from multiple compilations?

Yes, you have two different builds in the first case.  I don't know
how that happened, assuming you built the pretest tarball.  Did you
build 2 different configurations in that tree, perhaps?



  parent reply	other threads:[~2022-01-16 13:48 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 15:42 limit native compilation - how Colin Baxter 😺
2022-01-15 15:58 ` Eli Zaretskii
2022-01-15 16:01   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 16:38     ` Eli Zaretskii
2022-01-15 16:51       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 17:55         ` Eli Zaretskii
2022-01-15 18:58           ` Colin Baxter 😺
2022-01-15 19:12             ` Eli Zaretskii
2022-01-15 19:21             ` H. Dieter Wilhelm
2022-01-15 20:31               ` Colin Baxter 😺
2022-01-15 22:15                 ` H. Dieter Wilhelm
2022-01-16  7:13                   ` Eli Zaretskii
2022-01-16  7:15                 ` Eli Zaretskii
2022-01-16  7:41                   ` Colin Baxter 😺
2022-01-16  9:26                     ` Eli Zaretskii
2022-01-17 19:37                     ` H. Dieter Wilhelm
2022-01-17 20:39                       ` Colin Baxter 😺
2022-01-16  8:39               ` Eli Zaretskii
2022-01-16 11:30                 ` H. Dieter Wilhelm
2022-01-16 11:42                   ` Eli Zaretskii
2022-01-16 12:01                     ` H. Dieter Wilhelm
2022-01-16 12:11                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 12:17                       ` Eli Zaretskii
2022-01-16 13:24                         ` H. Dieter Wilhelm
2022-01-16 13:36                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 13:52                             ` H. Dieter Wilhelm
2022-01-16 13:59                               ` Eli Zaretskii
2022-01-16 18:37                                 ` H. Dieter Wilhelm
2022-01-16 18:46                                   ` Eli Zaretskii
2022-01-17 13:38                                     ` H. Dieter Wilhelm
2022-01-17 13:49                                       ` Eli Zaretskii
2022-01-17 16:11                                         ` H. Dieter Wilhelm
2022-01-17 16:30                                           ` Corwin Brust
2022-01-17 19:03                                             ` H. Dieter Wilhelm
2022-01-17 19:23                                               ` Corwin Brust
2022-01-17 21:54                                               ` Corwin Brust
2022-01-18 14:34                                                 ` Eli Zaretskii
2022-01-18 19:04                                                 ` H. Dieter Wilhelm
2022-01-17 16:55                                           ` Eli Zaretskii
2022-01-18  2:57                                           ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18  3:22                                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:49                                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:53                                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 22:10                                   ` Michael Heerdegen
2022-01-16 13:48                           ` Eli Zaretskii [this message]
2022-01-16 17:08                           ` Andy Moreton
2022-01-16 18:09                             ` H. Dieter Wilhelm
2022-01-15 17:55   ` Colin Baxter 😺
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor

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=83pmoryeo3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).