unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problem building emacs from CVS under MSWindow due to CR/LF and addsection
Date: Sun, 12 Oct 2008 21:09:46 +0200	[thread overview]
Message-ID: <BLU104-W160A5657A1CEF1F9AC354984370@phx.gbl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2170 bytes --]


Hello,

Thank you for your feedback. Sorry for the delay in answering.

So...

Actually, this $foo$ instead of foo$ does not seem to prevent building. 
What really prevents building is the mixture of Unix and Dos end of line 
in the makefile produced by configure.bat.

Replacing `$foo$' by `foo$' does not solve the issue which I am in.

In the attachment I have put this makefile, as you can see there is a 
mixture of DOS and Unix style EOL. When I build with `makefile' the 
build fails very soon. Now I edited `makefile' into 
`makefile.woextractrlm' to remove all extra CTRL-M and I tried to build 
with `-f makefile.woextractrlm' option.

It went quite further, but still it failed for a similar problem, in the 
file uni-bidi.el the Local Variable section has some CTRL-M at end of 
line, and this cause a load error. I included in the attached file a 
file temp.el examplifying the problem.

Maybe configure.bat could be fixed by testing if sed is present on the 
machine, and by filtering all the problematic files
by some `sed s/\r$//g'  command.

I am wondering whether the issue with Local Variable is a bug by itself ?

Regards,
   Vincent.
 

Eli Zaretskii a écrit :
>> Date: Fri, 10 Oct 2008 10:13:37 +0200
>> From: "Juanma Barranquero" 
>> Cc: emacs-devel 
>>
>> A few years ago, last I tested it, the only reason that 4NT/TCC failed
>> the build process is one line in nt/configure.bat:
>>
>>   if not "%$foo$%" == "123456789_123456789_123456789_123456789_123"
>> goto SmallEnv
>>
>> because 4NT expands %$ (is an internal variable, like %1, etc.) so the
>> comparison is always false. If $foo$ were called foo$ 4NT would have
>> no trouble at all.
>>
>> I mentioned that back then, but the idea of changing one character to
>> cater to non-free software was ill-received, IIRC.
>>     
>
> If you can test the change with current versions of 4NT, I don't mind
> the change.
>
>
>
>
>   



_________________________________________________________________
Installez gratuitement les 20 émôticones Windows Live Messenger les plus fous ! Cliquez ici !
http://www.emoticones-messenger.fr/

[-- Attachment #1.2: Type: text/html, Size: 2506 bytes --]

[-- Attachment #2: issuewithWindows2000build.tgz --]
[-- Type: application/octet-stream, Size: 7678 bytes --]

             reply	other threads:[~2008-10-12 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 19:09 Vincent Belaïche [this message]
2008-10-12 20:11 ` Problem building emacs from CVS under MSWindow due to CR/LF and addsection Eli Zaretskii
2008-10-12 22:21 ` Juanma Barranquero
  -- strict thread matches above, loose matches on Subject: below --
2008-10-20 18:33 Vincent Belaïche
2008-10-20 23:50 ` Eli Zaretskii
2008-10-19 19:13 Vincent Belaïche
2008-10-20 14:55 ` Eli Zaretskii
2008-10-14  5:01 Vincent Belaïche
2008-10-10  5:48 Vincent Belaiche
2008-10-10  7:58 ` Eli Zaretskii
2008-10-10  8:13   ` Juanma Barranquero
2008-10-10  9:00     ` Eli Zaretskii

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=BLU104-W160A5657A1CEF1F9AC354984370@phx.gbl \
    --to=vincent.b.1@hotmail.fr \
    --cc=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).