From: Jonathan Leech-Pepin <email@example.com>
To: John Hendy <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org,
Bostjan Vilfan <email@example.com>
Subject: Re: makefile for v. 7.9.1 on Windows 7 doesn't work
Date: Fri, 7 Sep 2012 09:32:38 -0400 [thread overview]
Message-ID: <CAHRqSkR2zEONA-VftLYseGJ8-RckncS_S3vkcEaTwW-Eaufirstname.lastname@example.org> (raw)
On Fri, Sep 7, 2012 at 9:05 AM, John Hendy <email@example.com> wrote:
> On Fri, Sep 7, 2012 at 7:45 AM, Jonathan Leech-Pepin
> <firstname.lastname@example.org> wrote:
>> On Fri, Sep 7, 2012 at 8:33 AM, John Hendy <email@example.com> wrote:
>>> On Fri, Sep 7, 2012 at 2:13 AM, Bostjan Vilfan <firstname.lastname@example.org> wrote:
>>>> I notice that the makefile in version 7.9.1 has been changed (with regard to v. 7.8.11). When I tried to run it under Windows7, it didn't work (the makefile for 7.8.11 ran OK). Can anyone provide some information?
>>> Can you provide more information? The error, what you were doing, etc?
>>> The last time I git pulled perhaps a week or so ago, I tried following
>>> Worg like so:
>>> | emacs -batch -Q -L lisp -l ../UTILITIES/org-fixup -f
>>> It failed. I inspected the dit directory and noticed that it's not
>>> ../UTILITIES anymore; all of the make stuff is in ../mk. Could that be
>>> the problem if you're following Worg?
>> If the problem is related to the missing =UTILITIES= directory, the
>> solution would seem to be just re-run the update. I had that issue on
>> several machines, all of which complained the first time about the
>> missing =UTILITIES= directory and then ran successfullly on the
>> subsequent updates.
> Can someone else confirm? I'm just pulled again and have no UTILITIES dir.
=UTILITIES/= was renamed =util/=, and then has since been moved to
=mk/=. The results I had seen seemed to indicate that it couldn't
find a script in UTILITIES/ so it could not continue (because it had
been renamed but was being looked for in the old location).
Running it a second time simply removed the confusion as to the
location of the files and permitted the update to continue without
>>> As an aside, I just tried re-compiling to check and I noticed that if
>>> I follow Worg and cd into /path/to/org.git/mk and then run =emace
>>> -batch ... ../mk/org-fixup.el ...=, I get the error:
>>> | Symbol's function definition is void: org-find-library-dir
>>> If I cd to /path/to/org.git and run the command with only one perios
>>> (=emacs ... ./mk/org-fixup.el ...=), then it works. But =M-x
>>> org-version= spits out something related to org-fixup and isn't a real
>>> version number.
>>> In any case, I can still compile as far as I know. Sorry if this
>>> wasn't your issue, but with the lack of details no one will be able to
>>> help you diagnose the problem.
>>> Best regards,
>>>  http://orgmode.org/worg/org-hacks.html#compiling-org-without-make
next prev parent reply other threads:[~2012-09-07 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 7:13 makefile for v. 7.9.1 on Windows 7 doesn't work Bostjan Vilfan
2012-09-07 12:33 ` John Hendy
2012-09-07 12:45 ` Jonathan Leech-Pepin
2012-09-07 13:05 ` John Hendy
2012-09-07 13:14 ` Bastien
2012-09-07 13:27 ` John Hendy
2012-09-07 13:32 ` Jonathan Leech-Pepin [this message]
2012-09-07 19:00 ` Achim Gratz
2012-09-10 17:59 ` John Hendy
2012-09-10 19:24 ` Achim Gratz
2012-09-10 19:48 ` John Hendy
2012-09-10 19:58 ` Achim Gratz
2012-09-10 20:01 ` Nick Dokos
2012-09-07 16:42 Bostjan Vilfan
2012-09-08 6:56 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).