From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Copley Newsgroups: gmane.emacs.bugs Subject: bug#16099: 24.3.50; Build failure, undefined function `cl-member' Date: Tue, 10 Dec 2013 18:25:11 +0000 Message-ID: References: <1ua9g8o9qu.fsf_-_@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b3435a2a160a604ed323b85 X-Trace: ger.gmane.org 1386699974 16359 80.91.229.3 (10 Dec 2013 18:26:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Dec 2013 18:26:14 +0000 (UTC) Cc: 16099@debbugs.gnu.org To: Glenn Morris Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Dec 10 19:26:19 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 1VqS0e-0008L8-Tb for geb-bug-gnu-emacs@m.gmane.org; Tue, 10 Dec 2013 19:26:17 +0100 Original-Received: from localhost ([::1]:50795 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqS0e-0006a4-EW for geb-bug-gnu-emacs@m.gmane.org; Tue, 10 Dec 2013 13:26:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqS0V-0006Rn-Sb for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 13:26:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqS0R-0001r1-3E for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 13:26:07 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56295) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqS0Q-0001qw-WC for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 13:26:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VqS0Q-0002Io-9w for bug-gnu-emacs@gnu.org; Tue, 10 Dec 2013 13:26:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Richard Copley Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 10 Dec 2013 18:26: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: moreinfo unreproducible Original-Received: via spool by 16099-submit@debbugs.gnu.org id=B16099.13866999198777 (code B ref 16099); Tue, 10 Dec 2013 18:26:02 +0000 Original-Received: (at 16099) by debbugs.gnu.org; 10 Dec 2013 18:25:19 +0000 Original-Received: from localhost ([127.0.0.1]:42081 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VqRzh-0002HU-VL for submit@debbugs.gnu.org; Tue, 10 Dec 2013 13:25:18 -0500 Original-Received: from mail-ea0-f181.google.com ([209.85.215.181]:46637) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VqRzc-0002HD-3G for 16099@debbugs.gnu.org; Tue, 10 Dec 2013 13:25:15 -0500 Original-Received: by mail-ea0-f181.google.com with SMTP id m10so2448454eaj.40 for <16099@debbugs.gnu.org>; Tue, 10 Dec 2013 10:25:11 -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=iGo6Gomh6DBCwfVQFoUIUkUuwmJ3QJ770Dl2wXUwhCA=; b=Eim0sWoQBzDQ/saprmSEQ+BRZ83ynWZFGqKznduKJrM15mXOBuKswwZU8JTnt94Clx Bu52vnOOIAiCLKzj85fc3/USn5tQkVqPj59mbgYlXZxUmYZ2PKfqg5kbTVDSaiA53Fyc FERemy90QgN5GuNotqbgTHqKr3EVUEpd28129u7iBqjSyUh5aY5/cYvrmAiWhXQRXfEb 4nhmAQyoJ6wL95FUCCOkXYchBb/aJrNqH5suD4Jq0KDy6YCS8iZ5X/tUnKhEgeu/d2tV dL9yn5VcZu45cQBGLkDl6cwFJVVCUKtTUwjI2O2lk/+zlwnAxPm5rlyP9u4MFdtQnr5v 0Gmw== X-Received: by 10.14.202.137 with SMTP id d9mr19377760eeo.23.1386699911420; Tue, 10 Dec 2013 10:25:11 -0800 (PST) Original-Received: by 10.14.7.201 with HTTP; Tue, 10 Dec 2013 10:25:11 -0800 (PST) In-Reply-To: <1ua9g8o9qu.fsf_-_@fencepost.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:81697 Archived-At: --047d7b3435a2a160a604ed323b85 Content-Type: text/plain; charset=ISO-8859-1 On 10 Dec 2013 18:12, "Glenn Morris" wrote: > > > What's going on here: > > Buffer is read-only: # > [...] > Buffer is read-only: # > [...] > Opening output file: no such file or directory, c:/c/emacs/trunk/lisp/loaddefs.el > [...] > loaddefs.el: No such file or directory > > ? That certainly looks suspect, well spotted. I guess "c:/c/emacs/trunk/lisp/loaddefs.el" is the value of `generated-autoload-file' which is set a few lines up: [...] --eval '(setq generated-autoload-file (expand-file-name "/c/emacs/trunk/lisp/loaddefs.el"))' [...] I think that's probably a bug (mixing MSYS- and native-style paths), but if I had used a relative path to invoke the configure script, it would have been a benign bug. I'll reconfigure using a relative path and try again. --047d7b3435a2a160a604ed323b85 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On 10 Dec 2013 18:12, "Glenn Morris" <rgm@gnu.org> wrote:
>
>
> What's going on here:
>
> =A0 Buffer is read-only: #<buffer cus-load.el>
> =A0 [...]
> =A0 Buffer is read-only: #<buffer finder-inf.el>
> =A0 [...]
> =A0 Opening output file: no such file or directory, c:/c/emacs/trunk/l= isp/loaddefs.el
> =A0 [...]
> =A0 loaddefs.el: No such file or directory
>
> ?

That certainly looks suspect, well spotted. I guess "c:/c/emacs/trunk/= lisp/loaddefs.el" is the value of `generated-autoload-file' which = is set a few lines up:

[...] --eval '(setq generated-= autoload-file (expand-file-name "/c/emacs/trunk/lisp/loaddefs.el"= ))' [...]

I think that's probably a bug (mixing MSYS- and native-style pat= hs), but if I had used a relative path to invoke the configure script, it w= ould have been a benign bug. I'll reconfigure using a relative path and= try again.

--047d7b3435a2a160a604ed323b85--