unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guy Gascoigne - Piggford <guy@wyrdrune.com>
Subject: Re: NT mingw/msys build problem
Date: Tue, 26 Oct 2004 11:11:42 -0700	[thread overview]
Message-ID: <417E935E.6050509@wyrdrune.com> (raw)
In-Reply-To: <011301c4baad$b282c680$0200a8c0@sedrcw11488>

Well I got everything built and working correctly.  In the end I had 
take msys off my path and use cygwin as the host instead.  That and 
mingw, and emacs build perfectly.

Thank you all for your help and suggestions.

Guy

Lennart Borgman wrote:

>----- Original Message ----- 
>From: "Guy Gascoigne-Piggford" <guy@wyrdrune.com>
>To: "Emacs Devel" <emacs-devel@gnu.org>
>Sent: Monday, October 25, 2004 10:28 AM
>Subject: NT mingw/msys build problem
>
>
>: I've been trying to track down a problem that my NT build has when
>: building with the latest mingw+msys environment.  Emacs builds and runs,
>: but certain autoloads seem to be missing, after much hunting through
>: build logs I ended out with this being the cause of the problem:
>:
>: Eventually make runs this:
>:
>: "./../bin/emacs.exe" -batch --no-init-file --no-site-file --multibyte -l
>: autoload \
>:     --eval '(setq find-file-hooks nil \
>:         find-file-suppress-same-file-warnings t \
>:         generated-autoload-file \
>:           "c:/dev/emacs-src/emacs/lisp/loaddefs.el")' \
>:     -f batch-update-autoloads c:/dev/emacs-src/emacs/lisp calc calendar
>: emacs-lisp emulation eshell gnus international language mail mh-e net
>: obsolete play progmodes term textmodes toolbar url
>:
>: the output of which is:
>:
>: Wrote c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el
>: Loading vc-cvs...
>: Wrote c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el
>: Autoloads file
>: c:/dev/emacs-src/emacs/lisp/c;C:Devmsys.0evacs-srcacslisploaddefs.el
>: does not exist
>
>This does not work because MSYS sh converts / to \ if the executable is
>outside of MSYS /bin or /usr/bin. Maybe it is a good idea for some programs
>but not for Emacs as can be seen here. Emacs must be handled as the programs
>in the bin-directories (no path style conversion).
>
>They should rethink the conversion a bit I believe. I will further this
>example to MSYS mailing list.
>
>- Lennart
>
>
>
>
>  
>

  reply	other threads:[~2004-10-26 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25  8:28 NT mingw/msys build problem Guy Gascoigne-Piggford
2004-10-25  9:15 ` Jason Rumney
2004-10-25 22:41   ` Guy Gascoigne-Piggford
2004-10-25 23:09     ` Jason Rumney
2004-10-27  9:50       ` Lennart Borgman
2004-10-27 10:21         ` Lennart Borgman
2004-10-27 10:43         ` Jason Rumney
2004-10-27 19:16           ` Lennart Borgman
2004-10-25 16:00 ` Lennart Borgman
2004-10-26 18:11   ` Guy Gascoigne - Piggford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-26  1:07 Fred Kunz
2004-10-26  1:15 Fred Kunz

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=417E935E.6050509@wyrdrune.com \
    --to=guy@wyrdrune.com \
    /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).