unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: 16099@debbugs.gnu.org
Subject: bug#16099: 24.3.50; Build failure, undefined function `cl-member'
Date: Tue, 10 Dec 2013 21:09:14 +0100	[thread overview]
Message-ID: <CAH8Pv0hS+XboPoYJNfj=S7UTUOuDNGou=VfawgKtfCDV4O2icQ@mail.gmail.com> (raw)
In-Reply-To: <snd2l4zgn7.fsf@fencepost.gnu.org>

>> Other options might be for configure to abort on MinGW if srcdir is
>> absolute and has the "wrong" format (which must means that the user
>> specified srcdir, as in this case). Or to simply fix such a srcdir
>> before generating the Makefiles.
>>
>> Might be easier than unmsys'ing every present and future instance of
>> srcdir in the Makefiles.
>
> In fact I think that might mean that you could remove unmsys--file-name
> altogether...?

I think that the function 'unmsys--file-name' is conceptually wrong, because:

1. It assumes that every MSYS path will match the "/c/foo/bar"
pattern, which in general is false (as we've already seen).

2. Some directory "c:/whatever" could be mounted in MSYS as "/c/foo",
and therefore "/c/foo/bar" should be translated as "c:/whatever/bar"
(not "c:/foo/bar"). Improbable but possible.

Therefore, like I've said before, IMO this is unreliable, and we
should translate (or "unmsys") _all_ MSYS paths with the 'msys-to-w32'
script.

-- 
Dani Moncayo





  parent reply	other threads:[~2013-12-10 20:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 12:13 bug#16099: 24.3.50; Build failure, undefined function `cl-member' Richard Copley
2013-12-10 16:46 ` Eli Zaretskii
2013-12-10 16:53   ` Richard Copley
2013-12-10 17:09     ` Glenn Morris
2013-12-10 18:05     ` Eli Zaretskii
2013-12-10 18:13       ` Richard Copley
2013-12-10 18:16         ` Glenn Morris
2013-12-10 18:35         ` Eli Zaretskii
     [not found] ` <handler.16099.D16099.138669538824350.notifdone@debbugs.gnu.org>
2013-12-10 17:42   ` bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member') Richard Copley
2013-12-10 17:55     ` Richard Copley
2013-12-10 18:12       ` bug#16099: 24.3.50; Build failure, undefined function `cl-member' Glenn Morris
2013-12-10 18:25         ` Richard Copley
2013-12-10 18:34           ` Eli Zaretskii
2013-12-10 18:37             ` Richard Copley
2013-12-10 18:59               ` Eli Zaretskii
2013-12-10 20:47                 ` Richard Copley
2013-12-10 20:58                   ` Eli Zaretskii
2013-12-10 21:08                     ` Glenn Morris
2013-12-11 17:07                       ` Eli Zaretskii
2013-12-10 18:42             ` Glenn Morris
2013-12-10 18:48               ` Glenn Morris
2013-12-10 18:58                 ` Eli Zaretskii
2013-12-10 20:09                 ` Dani Moncayo [this message]
2013-12-10 20:31                   ` Eli Zaretskii
2013-12-10 20:57                     ` Dani Moncayo
2013-12-11 17:12                       ` Eli Zaretskii
2013-12-12 14:08                         ` Dani Moncayo
2013-12-12 16:33                           ` Eli Zaretskii
2013-12-12 19:53                             ` Dani Moncayo
2013-12-14  9:33                               ` Dani Moncayo
2013-12-14  9:56                                 ` Eli Zaretskii
2013-12-14 20:08                                 ` Glenn Morris
2013-12-14 21:32                                   ` Dani Moncayo
2013-12-14 21:43                                     ` Glenn Morris
2013-12-14 21:56                                       ` Dani Moncayo
2013-12-10 18:58               ` Eli Zaretskii
2013-12-10 18:13     ` bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member') 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='CAH8Pv0hS+XboPoYJNfj=S7UTUOuDNGou=VfawgKtfCDV4O2icQ@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=16099@debbugs.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).