> From: Ralf Angeli <[EMAIL PROTECTED]>
> Date: Wed, 28 Dec 2005 23:22:40 +0100
>
> Okay, now I tried again and creation of autoloads works. I checked
> this with MinGW's mingw32-make and MSYS' make. In both cases
> lisp/autoloads.el is created with only a small difference:
>
> $ diff -u build-
* Eli Zaretskii (2005-12-24) writes:
> I installed a change that should fix this problem for you. Can you
> sync with the repository and see if autoloads now work even with MSYS
> munging of the command line?
Okay, now I tried again and creation of autoloads works. I checked
this with MinGW's m
> Cc: emacs-pretest-bug@gnu.org
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Date: Mon, 26 Dec 2005 16:56:17 +0100
>
> "./../bin/emacs.exe" -batch --no-init-file --no-site-file --multibyte -l
> autoload \
> --eval '(setq find-file-hook nil
> find-file-suppress-same-file-warnings t)' \
>
> Cc: emacs-pretest-bug@gnu.org
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Date: Mon, 26 Dec 2005 16:56:17 +0100
>
> Thanks for your efforts. I did a fresh checkout into a new directory,
> ran `configure ...' and while doing `mingw32-make bootstrap' the
> following error occurred:
>
> --8<---
* Eli Zaretskii (2005-12-24) writes:
> I installed a change that should fix this problem for you. Can you
> sync with the repository and see if autoloads now work even with MSYS
> munging of the command line?
Thanks for your efforts. I did a fresh checkout into a new directory,
ran `configure .
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Cc: emacs-pretest-bug@gnu.org
> Date: Mon, 19 Dec 2005 12:23:37 +0100
>
> > Is there any reasonable chance that MSYS maintainers will fix this?
> > Could you check with them, or maybe try their latest snapshot of
> > ported Bash and see if the problem went
* Eli Zaretskii (2005-12-19) writes:
>> From: Ralf Angeli <[EMAIL PROTECTED]>
>>
>> Oh great, then I'll probably have to do another upload to
>> alpha.gnu.org.
>
> Sorry, I'm confused: what upload to alpha.gnu? What did you upload
> there, and how is this discussion relevant to whatever you uplo
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Cc: emacs-pretest-bug@gnu.org
> Date: Mon, 19 Dec 2005 12:23:37 +0100
>
> * Eli Zaretskii (2005-12-18) writes:
>
> > However, I cannot accept your patch as it stands. First, you missed
> > the important WARNING in the comment just preceding the commands
* Eli Zaretskii (2005-12-18) writes:
> However, I cannot accept your patch as it stands. First, you missed
> the important WARNING in the comment just preceding the commands you
> wanted to patch,
Oh great, then I'll probably have to do another upload to
alpha.gnu.org. At least because of the u
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Date: Sun, 18 Dec 2005 16:56:18 +0100
>
> > 2005-07-08 Ralf Angeli <[EMAIL PROTECTED]>
> >
> > * makefile.w32-in (autoloads): Do not let autoload file name be
> > mangled by the shell.
>
> I'd like to followup on this because until now nothing h
* Ralf Angeli (2005-07-08) writes:
> * Ralf Angeli (2005-07-07) writes:
>
>> Using this for bootstrapping with `mingw32-make bootstrap' from a DOS
>> prompt in the nt/ directory I get the following error:
> [...]
>> Opening output file: invalid argument,
>> d:/software/windows/unix/src/emacs/lisp
* Eli Zaretskii (2005-07-09) writes:
> It's strange: MinGW-4.1.0.exe is under "Current", but MinGW Runtime is
> still at version 3.7. What is inside MinGW-X.Y.Z.exe---isn't it the
> runtime plus the compiler and Binutils?
I don't remember what was packaged with it. And as I am currently
enjoyin
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Cc: emacs-pretest-bug@gnu.org
> Date: Sat, 09 Jul 2005 10:41:33 +0200
>
> > Good God! Can you please explain why we need such a monstrosity with
> > MSYS, and why the original version fails (i.e., why is the file name
> > mangled)?
>
> I don't know exact
* Eli Zaretskii (2005-07-09) writes:
>> From: Ralf Angeli <[EMAIL PROTECTED]>
>>
>> + --eval $(ARGQUOTE)(let ((find-file-hook nil) \
>> + (find-file-suppress-same-file-warnings t) \
>> + (generated-autoload-file \
>> +
> From: Ralf Angeli <[EMAIL PROTECTED]>
> Date: Fri, 08 Jul 2005 23:06:09 +0200
>
> Okay, with the following patch (thanks, David, for reminding me of the
> technique) I can build Emacs under Windows using mingw32-make (MinGW
> 4.1.0) with MSYS' (1.0.10) sh.exe either present or not.
Thanks for w
* Ralf Angeli (2005-07-07) writes:
> Using this for bootstrapping with `mingw32-make bootstrap' from a DOS
> prompt in the nt/ directory I get the following error:
[...]
> Opening output file: invalid argument,
> d:/software/windows/unix/src/emacs/lisp/D;C:Programmemsysâș.0
> oftwarewindowsunix r
* Jason Rumney (2005-07-07) writes:
> The fact that you have no drive letters in the paths suggests to me that
> you are using cygwin or msys make, which corrupts DOS paths to look like
> unix paths in a way that only cygwin or msys tools can understand.
>From my former message:
>>The version
The fact that you have no drive letters in the paths suggests to me
that you are using cygwin or msys make, which corrupts DOS paths to
look like unix paths in a way that only cygwin or msys tools can
understand. This is not good behaviour for make, please try a different
version. There are non
* Jason Rumney (2005-07-07) writes:
> Can you please try to debug what has caused this on your machine. I do
> not have this problem, and noone else has reported it either.
Okay, I inserted a `sleep 60' at the end of the `autoloads' target of
lisp/makefile and this is what I could observe during
Ralf Angeli wrote:
* Ralf Angeli (2005-07-06) writes:
loaddefs.el in a Windows build checked out and compiled yesterday
doesn't seem to include all autoloads. For example the autoloads for
latexenc.el are missing. I suspect this is the cause for LaTeX files
in a Windows build of Emacs bei
* Ralf Angeli (2005-07-06) writes:
> loaddefs.el in a Windows build checked out and compiled yesterday
> doesn't seem to include all autoloads. For example the autoloads for
> latexenc.el are missing. I suspect this is the cause for LaTeX files
> in a Windows build of Emacs being opened with a r
loaddefs.el in a Windows build checked out and compiled yesterday
doesn't seem to include all autoloads. For example the autoloads for
latexenc.el are missing. I suspect this is the cause for LaTeX files
in a Windows build of Emacs being opened with a raw-text-dos coding
system (which prevents ch
22 matches
Mail list logo
