From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap failure on MS-Windows
Date: Tue, 05 Nov 2013 20:26:43 +0200 [thread overview]
Message-ID: <83r4au7li4.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0g5Y2c-6Yujfq_NWOkHnqcMNmdTrwozMvXtzXbgjoW8aw@mail.gmail.com>
> Date: Tue, 5 Nov 2013 19:14:27 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Emacs development discussions <emacs-devel@gnu.org>
>
> On Tue, Nov 5, 2013 at 9:24 AM, Glenn Morris <rgm@gnu.org> wrote:
> >
> > BTW, if I need to suggest an actual patch for this, it would be
> > something like the following (obv. untested). This is the only place
> > left in the Makefiles that uses absolute filenames, so I don't think
> > anything else is needed.
>
> Thank you for the patch, Glenn.
>
> I've just tried to bootstrap (autogen + msysconfig + make bootstrap)
> with your patch applied, but it fails the same way.
I think there's a mistake in the patch:
! @(w32srcdir=`cd "$srcdir"; pwd -W | sed -e 's,^\([[A-Za-z]]\):,/\1,' | ${msys_to_w32}` ; \
^^^^^^^^^^
This should be "[A-Za-z]", i.e. only single pair of brackets. (The
second one was necessary in an Autoconf file, to protect from
expansion by m4.)
> BTW, as Óscar already said [1], there is a second problem here: Just
> after running autogen.sh (in the source tree) and msysconfig (in the
> -empty- build tree), "make bootstrap" re-runs autogen.sh (see line 137
> of the attached file) and the makefiles are re-generated. This should
> be unnecessary in this case, no?
This is on purpose, as this snippet from the top-level Makefile shows:
# Bootstrapping does the following:
# * Remove files to start from a bootstrap-clean slate.
# * Run autogen.sh.
# * Rebuild Makefile, to update the build procedure itself.
# * Do the actual build.
bootstrap: bootstrap-clean FRC
cd $(srcdir) && ./autogen.sh
$(MAKE) $(MFLAGS) MAKEFILE_NAME=force-Makefile force-Makefile
$(MAKE) $(MFLAGS) info all
next prev parent reply other threads:[~2013-11-05 18:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 18:04 Bootstrap failure on MS-Windows Dani Moncayo
2013-11-02 18:52 ` Glenn Morris
2013-11-05 8:24 ` Glenn Morris
2013-11-05 18:14 ` Dani Moncayo
2013-11-05 18:26 ` Eli Zaretskii [this message]
2013-11-05 19:46 ` Dani Moncayo
2013-11-05 20:05 ` Eli Zaretskii
2013-11-05 21:08 ` Dani Moncayo
2013-11-05 21:52 ` Glenn Morris
2013-11-06 15:38 ` Dani Moncayo
2013-11-06 20:32 ` Glenn Morris
2013-11-06 20:50 ` Eli Zaretskii
2013-11-06 20:55 ` Glenn Morris
2013-11-12 2:42 ` Glenn Morris
2013-11-06 0:27 ` Óscar Fuentes
2013-11-06 1:35 ` Glenn Morris
2013-11-06 1:42 ` Glenn Morris
2013-11-06 13:59 ` Andy Moreton
2013-11-06 17:08 ` Eli Zaretskii
2013-11-06 20:24 ` Andy Moreton
2013-11-08 10:32 ` Andy Moreton
2013-11-08 11:02 ` Eli Zaretskii
2013-11-08 13:34 ` Andy Moreton
2013-11-08 14:18 ` Eli Zaretskii
2013-11-09 12:36 ` Andy Moreton
2013-11-09 13:19 ` Eli Zaretskii
2013-11-10 21:21 ` Andy Moreton
2013-11-09 13:24 ` Jarek Czekalski
2013-11-09 13:51 ` Eli Zaretskii
2013-11-09 14:33 ` Dani Moncayo
2013-11-09 15:18 ` Eli Zaretskii
2013-11-05 20:29 ` Glenn Morris
2013-11-05 21:09 ` Dani Moncayo
2013-11-05 20:29 ` Glenn Morris
2013-11-05 18:27 ` Glenn Morris
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=83r4au7li4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--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).