From: Eli Zaretskii <eliz@gnu.org>
To: Help-gnu-emacs@gnu.org
Subject: Re: making an emacs-29 tarball for testing latest changes on the branch
Date: Tue, 30 May 2023 14:16:19 +0300 [thread overview]
Message-ID: <83v8gaf4sc.fsf@gnu.org> (raw)
In-Reply-To: <SJ1PR12MB636376B45BF46E7BB44A9959A64B9@SJ1PR12MB6363.namprd12.prod.outlook.com> (message from Andrés Ramírez on Tue, 30 May 2023 10:35:30 +0000)
> From: Andrés Ramírez <rrandresf@hotmail.com>
> Date: Tue, 30 May 2023 10:35:30 +0000
>
> $ ./make-dist --snapshot --no-compress --no-changelog
> Version number is 29.0.91
> Sanity checking (use --no-check to disable this)...
> The following .el files have no corresponding .elc files:
> lisp/emacs-lisp/comp.el lisp/emacs-lisp/comp-cstr.el
> Failed checks
> $ ./make-dist --snapshot --no-compress --no-changelog --no-check
> Version number is 29.0.91
> Creating staging directory: 'make-dist.tmp.41366'
> ./make-dist: line 397: make-dist.tmp.41366/MANIFEST: No such file or directory
> $ ./make-dist --snapshot --no-compress --no-changelog --no-check
> Version number is 29.0.91
> Creating staging directory: 'make-dist.tmp.41922'
> Creating top directory: 'make-dist.tmp.41922/emacs-29.0.91'
> Creating subdirectories
> mkdir: missing operand
> Try 'mkdir --help' for more information.
> Cleaning up the staging directory
> $
> --8<---------------cut here---------------end--------------->8---
>
> when
> ,---- [ ]
> | ./make-dist: line 397: make-dist.tmp.41366/MANIFEST: No such file or directory
> `----
>
> I did touch MANIFEST
>
> Then I got the last error message.
>
> What I am missing for making the tarball?
You are missing the detailed instructions in admin/make-tarball.txt.
(Those instructions are for those who actually prepare the
pretest/release tarballs, so they include stuff you don't need for
your case, but knowing which parts are needed and which aren't isn't
trivial.)
In your case, this part is relevant:
For Emacs 28 and later, as long as --with-native-compilation is
not the default, the tree needs to be configured with
native-compilation enabled, to ensure all the pertinent *.elc
files will end up in the tarball. Otherwise, the *.eln files
might not build correctly on the user's system.
./autogen.sh
./configure --with-native-compilation && make
The MANIFEST thing is because this script is supposed to be run from a
Git repository, and you didn't.
There are other issues with what you are trying to do, for example
version 29.0.91 is incorrect (that's the version of the last pretest,
not of the Emacs you are building).
Bottom line: you are doing something users aren't supposed to do
without knowing very well what they are doing and how to do it. So
don't be surprised you face an uphill battle...
next prev parent reply other threads:[~2023-05-30 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:35 making an emacs-29 tarball for testing latest changes on the branch Andrés Ramírez
2023-05-30 11:16 ` Eli Zaretskii [this message]
2023-06-03 11:14 ` andrés ramírez
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=83v8gaf4sc.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).