unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: configure-more.zip
Date: Sat, 02 Jul 2005 15:20:36 +0200	[thread overview]
Message-ID: <ull4pqr8b.fsf@gnu.org> (raw)
In-Reply-To: <42C676AC.2020903@student.lu.se> (message from Lennart Borgman on Sat, 02 Jul 2005 13:12:44 +0200)

> Date: Sat, 02 Jul 2005 13:12:44 +0200
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC: emacs-devel@gnu.org
> 
> Eli Zaretskii wrote:
> 
> ><rant>
> >Why send it as a .zip file in a binary attachment, when all you want
> >to send is plain text for inclusion in configure.bat?
> ></rant>
> >  
> >
> Because sending a bat-file was not allowed.

??? By whom?

> >Therefore, I suggest the following strategy for solving the -kb issue:
> >put a small C program into the nt subdirectory which would read
> >nt/configure.bat, nt/nmake.defs, and nt/makefile.w32-in in binary mode
> >and make sure they have the right line endings; if they don't, this
> >program would fail.  Then have this program invoked by "make bootstrap"
> >in the nt directory.
> >
> >Would you like to implement this solution?
> >  
> >
> You mean build and run this program at the end of configure.bat?

Not at the end of configure.bat, but rather at the beginning of 
"make bootstrap".  The point here is that running configure.bat does
not necessarily mean the user will be bootstrapping.  If she doesn't
bootstrap, there's no reason to bother her about issues that are only
relevant to bootstrapping.

> Would not "make bootstrap" be too late?

No, I don't think it is.  If the effect is that "make bootstrap"
refuses to continue if line endings are not right, we've reached our
goal, right?  This is similar to what lib-src/test-distrib.c does (for
every build, not just for bootstrap).

> Yes, it seems like a better solution.  I will try.

Thanks.

  reply	other threads:[~2005-07-02 13:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02  9:27 configure-more.zip Lennart Borgman
2005-07-02 10:47 ` configure-more.zip Jason Rumney
2005-07-02 11:00   ` configure-more.zip Lennart Borgman
2005-07-02 11:57 ` configure-more.zip Eli Zaretskii
2005-07-02 11:12   ` configure-more.zip Lennart Borgman
2005-07-02 13:20     ` Eli Zaretskii [this message]
2005-07-02 13:32       ` configure-more.zip Lennart Borgman
2005-07-02 16:57         ` configure-more.zip Eli Zaretskii
2005-07-03  2:22           ` configure-more.zip Kevin Gallagher
2005-07-03  6:22             ` configure-more.zip Eli Zaretskii
2005-07-03  6:24               ` configure-more.zip Kevin Gallagher
2005-07-03 10:42                 ` configure-more.zip Glenn Morris
2005-07-03 16:01                 ` configure-more.zip Eli Zaretskii
2005-07-02 17:05     ` configure-more.zip Stefan Monnier
2005-07-02 20:15   ` configure-more.zip Jason Rumney
2005-07-03  6:12     ` configure-more.zip Eli Zaretskii
2005-07-03  7:38       ` configure-more.zip Lennart Borgman
2005-07-03 16:14         ` configure-more.zip Eli Zaretskii
2005-07-03 15:28           ` configure-more.zip Lennart Borgman
2005-07-03 18:54             ` configure-more.zip Eli Zaretskii
2005-07-03 18:17               ` configure-more.zip Lennart Borgman
2005-07-03 19:22                 ` configure-more.zip Jason Rumney
2005-07-03 10:31       ` configure-more.zip Juanma Barranquero
2005-07-03 16:15         ` configure-more.zip Eli Zaretskii
2005-07-03 16:43           ` configure-more.zip Juanma Barranquero

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=ull4pqr8b.fsf@gnu.org \
    --to=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).