From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: Glenn Morris <rgm@gnu.org>
Cc: "21789@debbugs.gnu.org" <21789@debbugs.gnu.org>
Subject: bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration)
Date: Fri, 30 Oct 2015 23:27:10 +0100 [thread overview]
Message-ID: <DUB109-W3380D075DC9D3914CED8FC842F0@phx.gbl> (raw)
In-Reply-To: <DUB109-W766AD2C585DC092121C65B842F0@phx.gbl>
Dear Glenn & Eli,
Just to elaborate a bit more the idea of adding some test into
autogen.sh: autotools are perl and M4 scripts, so, as far as EOLs are
concerned, I think that what is relevant is checking what perl and M4
do.
I don't think that M4 does anything special with the EOL, it just put to
output the same EOL that are in input --- well, maybe my using an MSYS
M4 makes me think so.
So, the thing that really needs to be tested is whether the user is
using an MSYS perl or a native MSW perl.
VBR,
Vincent Belaïche
----------------------------------------
> From: vincent.b.1@hotmail.fr
> To: rgm@gnu.org
> CC: 21789@debbugs.gnu.org; eliz@gnu.org
> Subject: RE: bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration)
> Date: Fri, 30 Oct 2015 21:41:09 +0100
>
> Dear Glenn,
>
> I don't think that my problem is the toolchain.
>
> But git was not configured for setting attributes to configure.ac to have LF
> EOL's. So when configure.ac was pulled from repo it got native EOL's, ie
> CRLF, and that was the root cause IMHO.
>
> As per your suggestion, I think that what could be tested is that :
>
> perl -e 'print "\n"'
>
> will output an LF, and not a CRLF.
>
> For instance on my MSYS console I did this :
>
> $ if perl -e 'print "x\n"' | grep -U '^x$'> /dev/null; then echo "ok"; else echo "not ok"; fi
> -| ok
> $ if /c/Programmes/Perl64/bin/perl.exe -e 'print "x\n"' | grep -U '^x$'> /dev/null; then echo "ok"; else echo "not ok"; fi
> -| not ok
>
> In the former case the MSYS perl is used, so the verdict is OK, and in
> the latter, that is the native MSW perl that is used, so the verdict is
> NOT OK.
>
> Vincent.
>
> ----------------------------------------
>> From: rgm@gnu.org
>> To: eliz@gnu.org
>> CC: vincent.b.1@hotmail.fr; 21789@debbugs.gnu.org
>> Subject: Re: bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration)
>> Date: Fri, 30 Oct 2015 14:42:26 -0400
>>
>> Eli Zaretskii wrote:
>>
>>> Your Automake/Autoconf installation is not an MSYS installation, but a
>>> native Windows one, so it produces Windows CRLF EOLs, and that
>>> confuses all kinds of scripts and/or utilities that are involved in
>>> the configure process.
>>
>> If it is possible to test for that, sounds like autogen.sh should do so
>> and reject those versions of autotools.
>>
>
prev parent reply other threads:[~2015-10-30 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:53 bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration) Vincent Belaïche
2015-10-30 13:49 ` Eli Zaretskii
2015-10-30 18:17 ` Vincent Belaïche
2015-10-30 20:31 ` Eli Zaretskii
2015-10-31 13:26 ` Vincent Belaïche
2015-10-31 13:42 ` Eli Zaretskii
2015-10-31 17:57 ` Vincent Belaïche
2015-10-31 18:21 ` Eli Zaretskii
2015-10-30 18:42 ` Glenn Morris
2015-10-30 20:33 ` Eli Zaretskii
2015-10-30 20:41 ` Vincent Belaïche
2015-10-30 22:27 ` Vincent Belaïche [this message]
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=DUB109-W3380D075DC9D3914CED8FC842F0@phx.gbl \
--to=vincent.b.1@hotmail.fr \
--cc=21789@debbugs.gnu.org \
--cc=rgm@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).