emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] org master: make fails


From: Julius Dittmar
Subject: Re: [O] org master: make fails
Date: Wed, 30 May 2018 13:45:02 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Am 30.05.2018 um 12:36 schrieb Nicolas Goaziou:
> Julius Dittmar <address@hidden> writes:
>> on two of my computers, both openSUSE-based with org-mode current master
>> and current texlive installed, make fails.
>>
>> The last messages are:
>>
>> make -C doc info
>> make[1]: Entering directory `/XXX/git/org-mode-CURRENT/doc'
>> emacs  -Q -batch --eval '(setq vc-handled-backends nil
>> org-startup-folded nil)' \
>>   --eval '(add-to-list '"'"'load-path "../lisp")' \
>>   --eval '(load "../mk/org-fixup.el")' \
>>   --eval '(org-make-manuals)'
>> Loading /XXX/git/org-mode-CURRENT/mk/org-fixup.el (source)...
>> Wrong number of arguments: #[(string &optional separators omit-nulls)
>>
>> ... followed by a long mainly empty and unreadable quoted string,
>> followed by ...
>>
>> " [separators omit-nulls split-string-default-separators list notfirst
>> start t 0 nil string-match ...] 5 1648329], 4
>> make[1]: *** [org.texi] Fehler 255
>> make[1]: Leaving directory `/XXX/git/org-mode-CURRENT/doc'
>> make: *** [info] Fehler 2
>>
>> As on the third of my computers (with an old debian and texlive 2017)
>> make works, I guess that's a local problem, not one of org-mode.
>> Nonetheless: Do you have any hints on what might be missing there, or
>> how I could proceed tracking down the problem?
> 
> Is your Emacs old (e.g., Emacs 23)?

GNU Emacs 24.3.1 in one instance, the other not older than that (can't
check the details right now).

> Did you try with emacs -Q, just
> loading Emacs?

As far as I can tell, the make fails somewhere in the 'make doc' part.
According to the quote above emacs is called with -Q.

'make autoloads' does not throw errors, and what I use of org-mode works
except for a minor and probably unrelated glitch I did not yet find time
to track down.

Thanks for looking into it and for a terrific tool,

Julius



reply via email to

[Prev in Thread] Current Thread [Next in Thread]