BTW, I don't have net access from home, so I won't be able to reply
over the weekend. If you see any more errors like that, just fix 'em
however looks best.
-Miles
--
Do not taunt Happy Fun Ball.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http:
Miles Bader <[EMAIL PROTECTED]> writes:
>> The patch below gets bootstrap working again. Can you confirm that
>> it's the right fix?
>
> Yes that looks correct.
Committed,
Lute.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org
> The patch below gets bootstrap working again. Can you confirm that
> it's the right fix?
Yes that looks correct.
Thanks,
-Miles
--
Do not taunt Happy Fun Ball.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
Quoting martin rudalics <[EMAIL PROTECTED]>:
> Jason Rumney wrote:
>
> >
> > Rather than patch the source, can you please try to debug the startup
> > code at the bottom of w32menu.c that decides whether to use Unicode
> > menu names. Does Windows ME have a stubbed out version of
> > unicode_
Juanma Barranquero wrote:
Perhaps it is Vader-style evil, after all. Today I've had the "intense
pleasure" of spending about three hours trying to understand why was I
able to do a MinGW build on one computer and GNU make ab-so-lu-te-ly
refused to work on another, identically set-up machine...
About a week ago, I said:
> Having files in CVS *with* CRLF end-lines
> and marked as text, not binary, is kinda... evil (not Darth
> Vader-style evil, but evil nonetheless).
Perhaps it is Vader-style evil, after all. Today I've had the "intense
pleasure" of spending about three hours trying to u
Jason Rumney wrote:
>
> Rather than patch the source, can you please try to debug the startup
> code at the bottom of w32menu.c that decides whether to use Unicode
> menu names. Does Windows ME have a stubbed out version of
> unicode_append_menu (AppendMenuW) that does nothing? The code assumes
>
> > IMHO CRLFs are not part of the file contents in case of text files
>
> Is that really so? Is there some legal opinion that changes in
> whitespace are not regarded as modifications?
Good question. Similarly you can ask whether you are allowed to
distribute a file in compressed form -- this
Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> IMHO CRLFs are not part of the file contents in case of text files --
>
> Is that really so? Is there some legal opinion that changes in
> whitespace are not regarded as modifications?
Not just any changes in whitespace: Change of line endings.
Simil
> Date: Wed, 25 May 2005 05:45:17 +0200 (CEST)
> Cc: [EMAIL PROTECTED], emacs-devel@gnu.org
> From: Werner LEMBERG <[EMAIL PROTECTED]>
>
> IMHO CRLFs are not part of the file contents in case of text files --
Is that really so? Is there some legal opinion that changes in
whitespace are not regar
> > IMHO CRLFs are not part of the file contents in case of text files
> > -- just think of transferring it via ftp in `ascii' mode. I vote
> > for converting it to Unix linefeeds. Objections?
>
> Every version of diff I've encountered treats CRLF as different than
> plain LF. This would make i
Jason Rumney <[EMAIL PROTECTED]> writes:
> Every version of diff I've encountered treats CRLF as different than
> plain LF.
Try diff -b.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> IMHO CRLFs are not part of the file contents in case of text files --
> just think of transferring it via ftp in `ascii' mode. I vote for
> converting it to Unix linefeeds. Objections?
Every version of diff I've encountered treats CRLF as different t
> > And some files have CRLF without a need -- at least I can't see a
> > reason to have them:
>
> > MISC-DIC/cangjie-table.b5
> > MISC-DIC/cangjie-table.cns
>
> They are verbatim copies of the original files I got from
> Christian Wittern. There's no strong reason to keep CRLFs,
> but I thi
> Date: Tue, 24 May 2005 21:37:56 +0200
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: David Kastrup <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> emacs-devel@gnu.org
>
> Interestingly enough I believe I just saw on the MSYS-MINGW mailing list
> that there are is now a port of bash
That is goo
In article <[EMAIL PROTECTED]>, Werner LEMBERG <[EMAIL PROTECTED]> writes:
> And some files have CRLF without a need -- at least I can't see a
> reason to have them:
> MISC-DIC/cangjie-table.b5
> MISC-DIC/cangjie-table.cns
They are verbatim copies of the original files I got from
Christian Wi
Eli Zaretskii wrote:
I don't know this for a fact (you will have to ask MSYS people if you
want a definitive answer), but I'm guessing that the problem is no one
ported Bash to MinGW. Since building a typical GNU package requires
to run the configure and libtool scripts, one cannot have a work
> Date: Tue, 24 May 2005 14:55:31 +0200
> From: Lennart Borgman <[EMAIL PROTECTED]>
> Cc: emacs-devel@gnu.org
>
> As far as I understand it is the .bat files that are special. The
> makefiles are not.
AFAIK, yes and yes.
> Why then not handle the .bat file separately? Can't
> they be stored as
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Tue, 24 May 2005 10:43:00 +0200
> Cc: emacs-devel@gnu.org
>
> I don't get it, though. The purpose of Mingw was to compile
> standalone binaries without requiring something like cygwin.dll as
> far as I understood it.
True.
> So I am surprised th
Jason Rumney wrote:
David Kastrup <[EMAIL PROTECTED]> writes:
Stupid question: why are the files stored into the repository with DOS
line endings?
Those files require DOS line ends.
The release is checked out on a GNU machine.
I have a (maybe sufficiently humble) suggestion:
As
martin rudalics <[EMAIL PROTECTED]> writes:
> There must be some reason: I frequently try to build Emacs on WindowsME
> and so far have not been able to retrieve a source which installs me a
> menubar.
Several people have reported this, and I have asked them to help
debugging it, but noone ever r
Juanma Barranquero <[EMAIL PROTECTED]> writes:
>> I don't have MSYS installed
>> where I type this to look under the hood and tell you what's with the
>> Cygwin DLL there, but I know for a fact that they forked from Cygwin.
>
> Well, msys/bin contains two DLLs, libW11.dll and msys-1.0.dll, and
> m
> So I am surprised that it would appear that they don't use their own
> runtime.
I think MSYS is sort of a development environment for MinGW. Certainly
MinGW does not use a Unix-emulation DLL.
--
/L/e/k/t/u
___
Emacs-devel mailin
Eli Zaretskii wrote:
Why ``fix'' that which isn't broken? Emacs still supports platforms
that are much older than Windows 9x, so I certainly don't see any
reasons for such a crusade against W9x build capabilities, nor any
reason to assume that no one builds Emacs on those old versions of
Window
> I don't have MSYS installed
> where I type this to look under the hood and tell you what's with the
> Cygwin DLL there, but I know for a fact that they forked from Cygwin.
Well, msys/bin contains two DLLs, libW11.dll and msys-1.0.dll, and
most executables in the dir depend on msys-1.0.dll, so it
> Cc: Juanma Barranquero <[EMAIL PROTECTED]>, emacs-devel@gnu.org
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Tue, 24 May 2005 01:50:22 +0200
>
> > (MSYS tools are actually Cygwin ports).
>
> Uh what? They are MinGW as far as I know. They don't need the Cygwin
> DLL.
MSYS was _created_ b
Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> Date: Mon, 23 May 2005 10:06:00 +0200
>> From: Juanma Barranquero <[EMAIL PROTECTED]>
>>
>> Well, Eli, "I'd suggest" is hardly a crusade, isn't it?
>
> Sorry, I'm so idiosyncratic to suggestions to drop ``old'' platforms
> that I sometimes go way out o
> Cc: emacs-devel@gnu.org
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Mon, 23 May 2005 10:46:08 +0200
>
> Since we both read and write the files in question and use \n in the
> patterns for reading and writing, this affects us, and the natural
> consequence would be to recommend using the Wi
> Date: Mon, 23 May 2005 10:06:00 +0200
> From: Juanma Barranquero <[EMAIL PROTECTED]>
>
> Well, Eli, "I'd suggest" is hardly a crusade, isn't it?
Sorry, I'm so idiosyncratic to suggestions to drop ``old'' platforms
that I sometimes go way out of line.
> > Then I'd say get a better port of rm.ex
> Date: Mon, 23 May 2005 10:08:22 +0200
> From: Juanma Barranquero <[EMAIL PROTECTED]>
>
> > The last part depends on the quality of the ported CVS clients one
> > uses. Most of them indeed do the stupid thing and blindly add a \r to
> > every line of a non-binary file.
>
> Stupid or not stupid,
> > So the Windows release contains mostly non-DOS line ends?
>
> Yes.
>
> > Is that a good idea?
>
> I don't see anything wrong with it. Emacs certainly doesn't have
> any problems with Unix EOLs, and most modern development tools don't
> have such problems either.
Personally, I don't like h
On 5/23/05, David Kastrup <[EMAIL PROTECTED]> wrote:
> The "solution" text checkout for editing, binary for compilation is, I
> must say, an idea I find appalling rather than appealing.
:)
In Emacs, if the nt/*.bat files need to be in CRLF form to allow
creating the tarball from a GNU/Linux or U
"Eli Zaretskii" <[EMAIL PROTECTED]> writes:
>> From: David Kastrup <[EMAIL PROTECTED]>
>> Date: Mon, 23 May 2005 02:15:07 +0200
>> Cc: Lennart Borgman <[EMAIL PROTECTED]>, emacs-devel@gnu.org
>>
>> > There is no such thing as a "Windows release" of Emacs. There are
>> > binary builds for Windows,
- Original Message -
From: Juanma Barranquero <[EMAIL PROTECTED]>
> The reason why I assume that not many (not "no one" as you say) people
> builds on Emacs is that two or three years ago I did regularly, and
> there were quite a few quirks. As recently as two weeks ago I
> tried to
> do
Adrian Aichner <[EMAIL PROTECTED]> writes:
> 2>&1 looks right to me, but according to "man bash" 2&>1 is preferred.
2&>1 is something completely different, it redirects to the file named
`1'.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90
On 5/23/05, Eli Zaretskii <[EMAIL PROTECTED]> wrote:
> The last part depends on the quality of the ported CVS clients one
> uses. Most of them indeed do the stupid thing and blindly add a \r to
> every line of a non-binary file.
Stupid or not stupid, CVSNT is perhaps the most used CVS
implementa
On 5/23/05, Eli Zaretskii <[EMAIL PROTECTED]> wrote:
> As Jason pointed out, this would cause trouble to users who build
> released Emacs versions from Emacs tarballs. Please let's not forget
> that people who get Emacs via CVS still aren't our main audience...
I read Jason's message after sendi
> Is this just a typo in this mail?
>
> 2>&1 looks right to me, but according to "man bash" 2&>1 is preferred.
Yes, a typo. I use 2>&1 on both. On 4NT,
echo test 2&>1
would echo "test 2" and create an empty file named "1".
--
/L/e/k/t/u
_
> Date: Mon, 23 May 2005 00:27:19 +0200
> From: Juanma Barranquero <[EMAIL PROTECTED]>
>
> Anyway, I agree with David: the files should be in the repository with
> text line endings in the first place, unless there's a real reason not
> to do so.
As Jason pointed out, this would cause trouble to
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Sun, 22 May 2005 23:54:42 +0200
> Cc: Lennart Borgman <[EMAIL PROTECTED]>, emacs-devel@gnu.org
>
> We currently have \r\n on Unix and \r\r\n on Windows.
The last part depends on the quality of the ported CVS clients one
uses. Most of them indeed
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Mon, 23 May 2005 00:30:35 +0200
> Cc: Lennart Borgman <[EMAIL PROTECTED]>, emacs-devel@gnu.org
>
> So the Windows release contains mostly non-DOS line ends?
Yes.
> Is that a good idea?
I don't see anything wrong with it. Emacs certainly doesn't
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Mon, 23 May 2005 02:15:07 +0200
> Cc: Lennart Borgman <[EMAIL PROTECTED]>, emacs-devel@gnu.org
>
> > There is no such thing as a "Windows release" of Emacs. There are
> > binary builds for Windows, but the source they are built from is the
> > same
Jason Rumney <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> Jason Rumney <[EMAIL PROTECTED]> writes:
>>
>>> David Kastrup <[EMAIL PROTECTED]> writes:
>>>
Stupid question: why are the files stored into the repository with DOS
line endings?
>>>
>>> Those files
Juanma Barranquero <[EMAIL PROTECTED]> writes:
> And yet another oddity. I usually run the make process from inside 4NT, and
>
> C:\bin\emacs\nt> (cmd /c nmake) 2&>1 | tee build.log
>
> works, but
>
> C:\bin\emacs\nt> (cmd /c nmake install) 2>&1 | tee install.log
I noticed 2&>1 vs. 2>&1
Is thi
David Kastrup <[EMAIL PROTECTED]> writes:
> Jason Rumney <[EMAIL PROTECTED]> writes:
>
>> David Kastrup <[EMAIL PROTECTED]> writes:
>>
>>> Stupid question: why are the files stored into the repository with DOS
>>> line endings?
>>
>> Those files require DOS line ends.
>> The release is checked out
And yet another oddity. I usually run the make process from inside 4NT, and
C:\bin\emacs\nt> (cmd /c nmake) 2&>1 | tee build.log
works, but
C:\bin\emacs\nt> (cmd /c nmake install) 2>&1 | tee install.log
often (but not always) hangs when running addpm.exe. It never hangs
when there's no redire
Jason Rumney <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> Stupid question: why are the files stored into the repository with DOS
>> line endings?
>
> Those files require DOS line ends.
> The release is checked out on a GNU machine.
So the Windows release contains m
Jason Rumney wrote:
>David Kastrup <[EMAIL PROTECTED]> writes:
>
>
>
>>Stupid question: why are the files stored into the repository with DOS
>>line endings?
>>
>>
>
>Those files require DOS line ends.
>The release is checked out on a GNU machine.
>
>
>
There is something I do not understa
> > On 5/22/05, Jason Rumney <[EMAIL PROTECTED]> wrote:
> I don't know, I have never studied the code for CVS, it just seems
> safer to me to avoid checking in changes from a directory that has
> been checked out with -kb.
Well, I don't have the full nt/ dir checked out as -kb, just the files
nee
David Kastrup <[EMAIL PROTECTED]> writes:
> Stupid question: why are the files stored into the repository with DOS
> line endings?
Those files require DOS line ends.
The release is checked out on a GNU machine.
___
Emacs-devel mailing list
Emacs-deve
Juanma Barranquero <[EMAIL PROTECTED]> writes:
> On 5/22/05, Jason Rumney <[EMAIL PROTECTED]> wrote:
>
>> I generally keep two copies
>> of the nt directory checked out. One checked out with -kb for
>> compiling with, and one checked out normally for checking in any
>> changes I make, or doing dif
Jason Rumney <[EMAIL PROTECTED]> writes:
> Lennart Borgman <[EMAIL PROTECTED]> writes:
>
>>>Did you run "cvs update -kb" in the emacs/nt directory, as recommended
>>>by the INSTALL file in there?
>>>
>>>
>>>
>> Eh..., no. I totally forgot that. Thanks.
>>
>> BTW why is this not done in the repos
On 5/22/05, Jason Rumney <[EMAIL PROTECTED]> wrote:
> I generally keep two copies
> of the nt directory checked out. One checked out with -kb for
> compiling with, and one checked out normally for checking in any
> changes I make, or doing diffs etc.
Why would that be necessary? Having a non -kb
Lennart Borgman <[EMAIL PROTECTED]> writes:
>>Did you run "cvs update -kb" in the emacs/nt directory, as recommended
>>by the INSTALL file in there?
>>
>>
>>
> Eh..., no. I totally forgot that. Thanks.
>
> BTW why is this not done in the repository?
Because the files are not binary, so we lose
Lennart Borgman <[EMAIL PROTECTED]> writes:
>>Did you run "cvs update -kb" in the emacs/nt directory, as recommended
>>by the INSTALL file in there?
>>
>>
>>
> Eh..., no. I totally forgot that. Thanks.
>
> BTW why is this not done in the repository? Is there any strange reason
> sending out file
>Did you run "cvs update -kb" in the emacs/nt directory, as recommended
>by the INSTALL file in there?
>
>
>
Eh..., no. I totally forgot that. Thanks.
BTW why is this not done in the repository? Is there any strange reason
sending out files that are in error? makefile.w32-in had ^M^M at the end
> Date: Sun, 22 May 2005 12:06:32 +0200
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: emacs-devel@gnu.org
>
> The pc is just reinstalled. I use the tools in my recommendations
> (follow the link at
> http://www.emacswiki.org/cgi-bin/wiki/WThirtyTwoInstallationKit - the
> recommendations are p
Lennart Borgman <[EMAIL PROTECTED]> writes:
> I just checked out Emacs from cvs and tried to do "make bootstrap",
> but it failed:
>
> D:\emacscvs\emacs\nt>configure.bat
> ...
> Emacs successfully configured.
> Run `gmake' to build, then run `gmake install' to install.
>
> D:\emacscvs\em
Eli Zaretskii wrote:
>>Date: Sun, 22 May 2005 00:09:07 +0200
>>From: Lennart Borgman <[EMAIL PROTECTED]>
>>
>>I just checked out Emacs from cvs and tried to do "make bootstrap", but
>>it failed:
>>
>> D:\emacscvs\emacs\nt>configure.bat
>> ...
>> Emacs successfully configured.
>> Run `gmake' t
> Date: Sun, 22 May 2005 00:09:07 +0200
> From: Lennart Borgman <[EMAIL PROTECTED]>
>
> I just checked out Emacs from cvs and tried to do "make bootstrap", but
> it failed:
>
> D:\emacscvs\emacs\nt>configure.bat
> ...
> Emacs successfully configured.
> Run `gmake' to build, then run `gma
60 matches
Mail list logo
