From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dani Moncayo Newsgroups: gmane.emacs.bugs Subject: bug#16099: 24.3.50; Build failure, undefined function `cl-member' Date: Tue, 10 Dec 2013 21:57:04 +0100 Message-ID: References: <1ua9g8o9qu.fsf_-_@fencepost.gnu.org> <8338m0y2px.fsf@gnu.org> <83txegwips.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1386709098 32261 80.91.229.3 (10 Dec 2013 20:58:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Dec 2013 20:58:18 +0000 (UTC) To: 16099@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Dec 10 21:58:22 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VqUNp-0002HI-Q0 for geb-bug-gnu-emacs@m.gmane.org; Tue, 10 Dec 2013 21:58:22 +0100 Original-Received: from localhost ([::1]:51266 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqUNp-0005Kw-Hb for geb-bug-gnu-emacs@m.gmane.org; Tue, 10 Dec 2013 15:58:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58716) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqUNh-0005Kn-Pz for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 15:58:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqUNb-0007CD-CL for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 15:58:13 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56460) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqUNb-0007C6-97 for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 15:58:07 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VqUNV-0008UU-PD for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 15:58:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dani Moncayo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 10 Dec 2013 20:58:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16099 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16099-submit@debbugs.gnu.org id=B16099.138670902832560 (code B ref 16099); Tue, 10 Dec 2013 20:58:01 +0000 Original-Received: (at 16099) by debbugs.gnu.org; 10 Dec 2013 20:57:08 +0000 Original-Received: from localhost ([127.0.0.1]:42246 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VqUMd-0008T5-Jh for submit@debbugs.gnu.org; Tue, 10 Dec 2013 15:57:08 -0500 Original-Received: from mail-la0-f48.google.com ([209.85.215.48]:33524) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VqUMb-0008Sw-A2 for 16099@debbugs.gnu.org; Tue, 10 Dec 2013 15:57:05 -0500 Original-Received: by mail-la0-f48.google.com with SMTP id n7so3117027lam.35 for <16099@debbugs.gnu.org>; Tue, 10 Dec 2013 12:57:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=oQwGp0hlgTZdijTf9cG2pAfkU7xZF61vRZg/j0mfz4I=; b=sOMUyWEIA/XyayLVYadBQ0zNfNeGz1I1qYczcX1tXqJhEDqMRo4ksZY+VbuRIOACUU jFJS9QWFaiFSPQjWO8b3d8VNMR85DpQhWhJ4rbYYERQESRUC/4lbsm4KhFUDawJY8CGE ao9u3QTLqraOSeOTCjhhElYfAxPORJqZDPebxr6imGO0X0+lVAeaDdDh9lv8YcVX1brB 3WEL17xON2XhF+TwTFWNREx3iW70Ro1sQ+0u6dLOUtgMiG9okI4bVLdXqKk9HwJXvGil L7Oa4egXiJzy+/cDHQZm0imSa+jKuXxf+XoUvzTJDo2CNIe2EpEnW6VkcsNhgFEU2x3p F66w== X-Received: by 10.152.143.101 with SMTP id sd5mr9349568lab.26.1386709024151; Tue, 10 Dec 2013 12:57:04 -0800 (PST) Original-Received: by 10.114.59.36 with HTTP; Tue, 10 Dec 2013 12:57:04 -0800 (PST) In-Reply-To: <83txegwips.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:81714 Archived-At: >> 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" > > It does nothing of the kind. It handles _only_ those file names that > slip into Emacs in the /c/foo/bar form, which Emacs cannot handle. I think that it would be possible that the path to "unmsys" had the form "/foo/bar". For example if someone has the source code tree under his MSYS tree and invokes the configure script with an absolute MSYS path (e.g. "/home/user/emacs/trunk/configure"). In that case, 'unmsys--file-name' will not translate the MSYS path ("/home/user/...") as expected. >> pattern, which in general is false (as we've already seen). > > Not sure what you meant here. If you mean your use case of building > inside the MSYS tree, then that one should be (and was) handled by > different means. It was handled in one place (for generating the native paths in 'src/epaths.h'), but it seems that there are more places where a translation to native w32 format is performed, and it would be nice if that translation was as reliable as possible. >> 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. > > People also shoot themselves in the foot, but why should we cater to > suicidal ones? "If it hurts, don't do that." MSYS is a tool to build > Posix packages, it has no purpose other than that. So it makes very > little sense to configure MSYS in a way that interferes with its main > purpose. People could do that by mistake, of course, but then the > solution is to recognize the mistake and correct it. Well yes, this second problem is minor, but we could fix it with the same effort. >> 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. > > Which is also unreliable, as we've seen. > > There are no bullet-proof solutions with MSYS. Building Posix > packages on Windows is inherently fragile, and always will be. > Therefore, the solutions should be the simplest ones we can find that > do the job. People who do unreasonable things should be told not to. I agree that the MSYS shell auto-conversion of paths can be tricky, but we still don't know the origin of this problem. In any case, the problem I pointed out doesn't seem to be the problem reported by the OP. Perhaps it would be interesting to see the file 'src/epaths.h' produced in the failed build. If some path is wrong there, then _maybe_ the culprit could be the script 'msys-to-w32'. -- Dani Moncayo