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: Thu, 12 Dec 2013 20:53:29 +0100 Message-ID: References: <1ua9g8o9qu.fsf_-_@fencepost.gnu.org> <8338m0y2px.fsf@gnu.org> <83txegwips.fsf@gnu.org> <83iouvwbvh.fsf@gnu.org> <83a9g66nbs.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=089e0160c36e1c35c004ed5bb3b9 X-Trace: ger.gmane.org 1386878052 20921 80.91.229.3 (12 Dec 2013 19:54:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Dec 2013 19:54:12 +0000 (UTC) Cc: 16099@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Dec 12 20:54:18 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 1VrCKw-0005qW-Dx for geb-bug-gnu-emacs@m.gmane.org; Thu, 12 Dec 2013 20:54:18 +0100 Original-Received: from localhost ([::1]:38369 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrCKw-0008Ml-3M for geb-bug-gnu-emacs@m.gmane.org; Thu, 12 Dec 2013 14:54:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49106) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrCKo-0008It-Ag for bug-gnu-emacs@gnu.org; Thu, 12 Dec 2013 14:54:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrCKg-0005bK-OT for bug-gnu-emacs@gnu.org; Thu, 12 Dec 2013 14:54:10 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:60319) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrCKg-0005bG-La for bug-gnu-emacs@gnu.org; Thu, 12 Dec 2013 14:54:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VrCKg-0005PT-9p for bug-gnu-emacs@gnu.org; Thu, 12 Dec 2013 14:54:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dani Moncayo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 12 Dec 2013 19:54:02 +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.138687801420755 (code B ref 16099); Thu, 12 Dec 2013 19:54:02 +0000 Original-Received: (at 16099) by debbugs.gnu.org; 12 Dec 2013 19:53:34 +0000 Original-Received: from localhost ([127.0.0.1]:46105 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VrCKD-0005Og-Sq for submit@debbugs.gnu.org; Thu, 12 Dec 2013 14:53:34 -0500 Original-Received: from mail-la0-f44.google.com ([209.85.215.44]:57713) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VrCKA-0005OX-Tj for 16099@debbugs.gnu.org; Thu, 12 Dec 2013 14:53:32 -0500 Original-Received: by mail-la0-f44.google.com with SMTP id ep20so692771lab.3 for <16099@debbugs.gnu.org>; Thu, 12 Dec 2013 11:53:29 -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 :cc:content-type; bh=W4MjaOILiguVrGcgUGRrSsAaEaFObrNjkiguGYiLATQ=; b=TW9oYLHArcz1Fb7LsyWRK9Dcu3A2NClMmNUf7sM+Rx/cghXqX4eqQ/zUE0U44uwidY u8ATcEdP9ER53NjFEdnpeLl1h+CaalaE9vVegXlviJHuWYW9yOzE8ex58qVaECMQYXiJ B4aeSzbT0QZXBB/IygvDFLzc/qMAd/O9/VeGBEufnh07z4afaJgGKwjP6VSD+2WLAcOj VagV+e6lSih+++Sdc2WaQYu7PuYewTjnarRxyzxZCGAfD8eeo2Wn7/QxqjmPdZjplOcX KSzHzriIbzCzJSHIqOszmVMeRcx/qduzF/jUtpCtK2CO0V2Irru8ipmYeg2apta593Sp Ct8w== X-Received: by 10.152.26.72 with SMTP id j8mr551628lag.85.1386878009614; Thu, 12 Dec 2013 11:53:29 -0800 (PST) Original-Received: by 10.114.59.36 with HTTP; Thu, 12 Dec 2013 11:53:29 -0800 (PST) In-Reply-To: <83a9g66nbs.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:81837 Archived-At: --089e0160c36e1c35c004ed5bb3b9 Content-Type: text/plain; charset=ISO-8859-1 >> >> In that case, 'unmsys--file-name' will not translate the MSYS path >> >> ("/home/user/...") as expected. >> > >> > How is this different from your use case, which is already handled? >> >> The difference is this: I invoke the configure script (from the build >> dir) using a relative path, which works with the current trunk. But >> if someone invokes the configure script using an absolute path which >> doesn't match the "/c/foo/bar" pattern (e.g. >> "/home/user-foo/emacs/trunk/configure"), the build will fail. > > The "pwd -W" method worked with both. I understand that the > msys-to-w32 method broke that. No, the msys-to-w32 method didn't broke that. It was at revno 114990 (which is not mine, BTW). > Then please un-break it. The attached patch seems to be what you want (I've tested it and works fine). >> But your way of implementing the translation doesn't work with all >> types of MSYS paths, as we've already seen. > > It isn't supposed to. > >> PS: The only "tricky" part of the patch is this: >> >> leimdir=`${srcdir}/../build-aux/msys-to-w32 "${leimdir}"` && \ >> ${RUN_EMACS} -l international/quail \ >> --eval "(update-leim-list-file \"$${leimdir}\");" >> ^ >> ^ >> ^ >> This semicolon does not alter the effect of the lisp expression, but >> prevents MSYS from altering the argument, since such argument (in the >> MSYS case) will have a colon ("c:/foo/bar") and that would make MSYS >> think about it as a list of posix paths which need translation to >> native windows format. See the rules in [1]. (This technique has >> been employed in several points) > > I don't think we should rely on such fragility. Ok, I agree that it is fragile. I don't like the current approach either, but it seems better that the above one, yes. So I'll wait for you to validate the attached patch. -- Dani Moncayo --089e0160c36e1c35c004ed5bb3b9 Content-Type: text/plain; charset=US-ASCII; name="tmp.diff" Content-Disposition: attachment; filename="tmp.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hp4fbh870 ZGlmZiAtLWdpdCBhL2NvbmZpZ3VyZS5hYyBiL2NvbmZpZ3VyZS5hYwppbmRleCA0MTI1OGZjLi41 MjRlZTRjIDEwMDY0NAotLS0gYS9jb25maWd1cmUuYWMKKysrIGIvY29uZmlndXJlLmFjCkBAIC0y NCw3ICsyNCwxNyBAQCBkbmwgIGFsb25nIHdpdGggR05VIEVtYWNzLiAgSWYgbm90LCBzZWUgPGh0 dHA6Ly93d3cuZ251Lm9yZy9saWNlbnNlcy8+LgogQUNfUFJFUkVRKDIuNjUpCiBBQ19JTklUKGVt YWNzLCAyNC4zLjUwKQogCi10ZXN0ICJ4JE1TWVNURU0iID0gInhNSU5HVzMyIiAmJiAuICRzcmNk aXIvbnQvbWluZ3ctY2ZnLnNpdGUKK2lmIHRlc3QgIngkTVNZU1RFTSIgPSAieE1JTkdXMzIiCit0 aGVuCisgICAjIE1TWVMtc3BlY2lmaWMgcHJvY2Vzc2luZworICAgLiAkc3JjZGlyL250L21pbmd3 LWNmZy5zaXRlCisKKyAgICMgQ29udmVydCBzcmNkaXIgdG8gYW4gYWJzb2x1dGUgTVNZUyBwYXRo IG9mIHRoZSBmb3JtICIvYy9mb28vYmFyIgorICAgIyB0byBzaW1wbGlmeSB0aGUgY29udmVyc2lv biBvZiBwYXRocyB0byB3aW5kb3dzLW5hdGl2ZSBmb3JtYXQKKyAgICMgImM6L2Zvby9iYXIiCisg ICBzcmNkaXI9YGNkICIke3NyY2Rpcn0iICYmIHB3ZCAtV2AKKyAgIHNyY2Rpcj0iLyR7c3JjZGly OjA6MX0ke3NyY2RpcjoyfSIKK2ZpCiAKIGRubCBTZXQgZW1hY3NfY29uZmlnX29wdGlvbnMgdG8g dGhlIG9wdGlvbnMgb2YgJ2NvbmZpZ3VyZScsIHF1b3RlZCBmb3IgdGhlIHNoZWxsLAogZG5sIGFu ZCB0aGVuIHF1b3RlZCBhZ2FpbiBmb3IgYSBDIHN0cmluZy4gIFNlcGFyYXRlIG9wdGlvbnMgd2l0 aCBzcGFjZXMuCg== --089e0160c36e1c35c004ed5bb3b9--