From: Glenn Morris <rgm@gnu.org>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: 9750@debbugs.gnu.org
Subject: bug#9750: 24.0.90; Windows binary distribution build fails with 24.0.90 Pretest
Date: Tue, 18 Oct 2011 03:39:10 -0400 [thread overview]
Message-ID: <hzobxezr35.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86aa94p88p.fsf@googlemail.com> (Christoph Scholtes's message of "Thu, 13 Oct 2011 21:22:46 -0600")
Christoph Scholtes wrote:
> The automated Windows binary distribution build fails with the 24.0.90
> Pretest because the `mingw32-make dist' target cannot find README.W32.
>
> There is a comment in `make dist':
> ## Exclude README.W32 because it is specific to pre-built binaries(?).
AIUI, README.W32 has information specific to the pre-built binaries
provided on ftp.gnu.org. Eg it starts:
This README file describes how to set up and run a precompiled
version of GNU Emacs for Windows. This distribution can be found on
the ftp.gnu.org server and its mirrors:
So it's inappropriate to include it in the source tarfile because it
contains information that is incorrect/irrelevant for people building
from source.
> README.W32 needs to be included in the
> tarball for `mingw32-make dist' to work.
But you're saying that you want to start from a source tarfile and make
a binary tarfile? I don't know how to reconcile these two.
next prev parent reply other threads:[~2011-10-18 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 3:22 bug#9750: 24.0.90; Windows binary distribution build fails with 24.0.90 Pretest Christoph Scholtes
2011-10-18 7:39 ` Glenn Morris [this message]
2011-10-18 14:18 ` Jason Rumney
2011-10-18 14:34 ` Jason Rumney
2011-10-18 15:47 ` Stefan Monnier
2011-10-19 1:15 ` Christoph Scholtes
2012-02-04 23:23 ` Christoph Scholtes
2012-02-05 16:45 ` Eli Zaretskii
2012-02-05 18:18 ` Christoph Scholtes
2012-02-05 21:01 ` Christoph Scholtes
2011-10-19 1:01 ` Christoph Scholtes
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=hzobxezr35.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=9750@debbugs.gnu.org \
--cc=cschol2112@googlemail.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.