From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Xemacs 21.5.32 and org-8.03, compilation problems
Date: Sun, 26 May 2013 19:17:35 +0200 [thread overview]
Message-ID: <87fvx9hd8w.fsf@Rainer.invalid> (raw)
In-Reply-To: 87sj1aorfn.fsf@mat.ucm.es
Uwe Brauer writes:
> I know that compiling org under Xemacs is delicate. I succeeded with
> 7.8.3 but it seems that the installation process has changed quite a
> bit.
No, not really.
> I edit the relevant
>
> default.mk
> file (OK I should not do that but create local.mk)
>
> EMACS=/usr/local/bin/xemacs
> BATCH = $(EMACS) -batch -vanilla # Xemacs
Yes, you should not do this. A configuration file for XEmacs is here:
http://orgmode.org/worg/dev/org-build-system.html#sec-4-1-4
> Now when running make the following problems showed up:
You're not using the sources you think you are using.
> Did anybody sucessfully compile the latest org version under
> Xemacs 21.5.X?
No, despite repeated calls for help no feedback from actual XEmacs users
was registered and at some point I've stopped bugging Bastien about the
incompatibilities introduced. There are at least a handful of functions
that'd need compatibility macros /defuns on XEmacs and I don't know what
turns up when these are out of the way, but the results were sketchy
already on 7.x whenever I tried. Your best bet is running uncompiled
(which probably still needs compatibility definitions).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-05-26 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 18:17 Xemacs 21.5.32 and org-8.03, compilation problems Uwe Brauer
2013-05-26 17:17 ` Achim Gratz [this message]
2013-05-30 20:33 ` Uwe Brauer
2013-05-31 19:15 ` Achim Gratz
2013-06-01 9:37 ` Achim Gratz
2013-06-02 8:39 ` Uwe Brauer
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvx9hd8w.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).