From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Unable to compile using Emacs 23 in Windows Date: Fri, 28 Aug 2009 13:29:42 +0200 Message-ID: References: <877hwpwbwd.fsf@gmail.com> <87my5lxoob.fsf@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgzeT-0008J5-3e for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 07:29:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgzeN-0008E3-FO for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 07:29:51 -0400 Received: from [199.232.76.173] (port=51195 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgzeN-0008Dp-6z for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 07:29:47 -0400 Received: from ey-out-1920.google.com ([74.125.78.147]:24853) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgzeM-0005dc-D0 for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 07:29:47 -0400 Received: by ey-out-1920.google.com with SMTP id 3so423561eyh.34 for ; Fri, 28 Aug 2009 04:29:45 -0700 (PDT) In-Reply-To: <87my5lxoob.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Paul Mead Cc: emacs-orgmode@gnu.org On Aug 27, 2009, at 5:27 PM, Paul Mead wrote: > Manish writes: > >> On Thu, Aug 27, 2009 at 8:18 PM, Paul Mead wrote: >>> I had everything working fine using NT Emacs v22.xxx but now that >>> I've >>> completely upgraded to 23 I'm getting numerous warnings comiling >>> org.el, >>> org-agenda.el, and it just hangs on org-attach.el. Not even an >>> error to >>> work with. >>> >>> If there's one thing I can't stand it's silent failure :-) >>> >>> I tried to redirect the errors to a text file, but it only >>> captured the >>> commands, not the errors. Any suggestions? >>> >>> Just my luck, everything works fine on my Linux machine, but I use >>> org-mode >>> mostly on the work laptop which is Windows. >> >> How do you compile Org on Windows? Using the solution that >> Sebastian and >> others recently worked out or some other way? >> >> FWIW, I use Cygwin Emacs (23) to compile Org but use Windows GNU >> Emacs >> exclusively. There are some odd looking messages but they have >> never bothered >> me (compilation log at http://paste.lisp.org/display/86127) > OK, so I've managed to redirect stderr so I can show you what I > get. Doesn't look much different to the start of your log to be > honest. > > -------------------------- > emacs -batch -q -no-site-file -eval "(progn (add-to-list (quote load- > path) \"/usr/local/share/emacs/site-lisp\") (add-to-list (quote load- > path) (expand-file-name \"./lisp/\")))" -f batch-byte-compile lisp/ > org.el > > In org-version: > org.el:105:23:Warning: attempt to let-bind constant `org-version' > org.el:125:49:Warning: variable assignment to constant `org-version' > > In org-read-date: > org.el:12359:11:Warning: `view-diary-entries-initially' is an obsolete > variable (as of Emacs 23.1); use `calendar-view-diary-initially- > flag' > instead. > org.el:12361:11:Warning: `view-calendar-holidays-initially' is an > obsolete > variable (as of Emacs 23.1); use `calendar-view-holidays- > initially-flag' > instead. > > In org-goto-calendar: > org.el:13369:10:Warning: `view-diary-entries-initially' is an obsolete > variable (as of Emacs 23.1); use `calendar-view-diary-initially- > flag' > instead. > org.el:13367:10:Warning: `view-calendar-holidays-initially' is an > obsolete > variable (as of Emacs 23.1); use `calendar-view-holidays- > initially-flag' > instead. > > In org-iswitchb: > org.el:13484:8:Warning: function `org-iswitchb' defined multiple > times in this > file > > In org-create-formula-image: > org.el:14051:19:Warning: reference to free variable > `org-export-latex-packages-alist' > Wrote c:/home/MEAD8982/elisp/org-mode/lisp/org.elc > emacs -batch -q -no-site-file -eval "(progn (add-to-list (quote load- > path) \"/usr/local/share/emacs/site-lisp\") (add-to-list (quote load- > path) (expand-file-name \"./lisp/\")))" -f batch-byte-compile lisp/ > org-agenda.el > > In org-agenda-get-some-entry-text: > org-agenda.el:2275:43:Warning: assignment to free variable `drawer-re' > org-agenda.el:2282:43:Warning: assignment to free variable `kwd-time- > re' > org-agenda.el:2278:28:Warning: reference to free variable `drawer-re' > org-agenda.el:2302:43:Warning: reference to free variable `kwd-time- > re' > org-agenda.el:2293:27:Warning: assignment to free variable `ind' > org-agenda.el:2298:37:Warning: reference to free variable `ind' > > In org-get-entries-from-diary: > org-agenda.el:3446:11:Warning: `fancy-diary-buffer' is an obsolete > variable > (as of Emacs 23.1); use `diary-fancy-buffer' instead. > > In org-agenda-goto-calendar: > org-agenda.el:6329:11:Warning: `view-calendar-holidays-initially' is > an > obsolete variable (as of Emacs 23.1); use > `calendar-view-holidays-initially-flag' instead. > org-agenda.el:6330:11:Warning: `view-diary-entries-initially' is an > obsolete > variable (as of Emacs 23.1); use `calendar-view-diary-initially- > flag' > instead. > Wrote c:/home/MEAD8982/elisp/org-mode/lisp/org-agenda.elc > emacs -batch -q -no-site-file -eval "(progn (add-to-list (quote load- > path) \"/usr/local/share/emacs/site-lisp\") (add-to-list (quote load- > path) (expand-file-name \"./lisp/\")))" -f batch-byte-compile lisp/ > org-ascii.el > Wrote c:/home/MEAD8982/elisp/org-mode/lisp/org-ascii.elc > emacs -batch -q -no-site-file -eval "(progn (add-to-list (quote load- > path) \"/usr/local/share/emacs/site-lisp\") (add-to-list (quote load- > path) (expand-file-name \"./lisp/\")))" -f batch-byte-compile lisp/ > org-attach.el > make: *** [lisp/org-attach.elc] Interrupt Hi Paul, did you interrupt the compilation here? The fact that there are a number of compilation *warnings* is no problem at all, I do clean these up only occasionally, for a release. In between releases, the can be present and usually pose no problem. The messages about goto-line are from a new policy in Emacs, apparently this is no longer a function that should be called from Lisp programs.... - Carsten