Re: [O] Compile failure
On Tuesday, 25 Jun 2019 at 13:53, Gregor Zattler wrote: > I assume you both know this will pin your git repo to this very > commit. Yes but I don't update frequently so it's not a big deal (for me). Thanks, eric -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.4-379-g1b74ae
Re: [O] Compile failure
Hi Eric, Klaushal, * "Fraga, Eric" [2019-06-24; 18:04]: > On Monday, 24 Jun 2019 at 11:48, Kaushal Modi wrote: >> That issue on Emacs master is fixed now for me. > > If it happens not to be, for Bill: just go to your emacs and > > git checkout 63b29f81075a3fdca70348f023d3ebb37a4f2a63 I assume you both know this will pin your git repo to this very commit. If one wants to use the emacs development version it's better to do git pull git co -f master an you will use cutting edge of emacs development. > make clean > make && make install > > and things should work. They do for me. Ciao; Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: [O] Compile failure
On Monday, 24 Jun 2019 at 11:48, Kaushal Modi wrote: > That issue on Emacs master is fixed now for me. If it happens not to be, for Bill: just go to your emacs and git checkout 63b29f81075a3fdca70348f023d3ebb37a4f2a63 make clean make && make install and things should work. They do for me. -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.4-379-g1b74ae
Re: [O] Compile failure
That issue on Emacs master is fixed now for me. -- Kaushal Modi On Mon, Jun 24, 2019, 11:43 AM William Denton wrote: > On 24 June 2019, Robert Pluim wrote: > > > Thatʼs an emacs issue, not an org-mode issue. If you specify the full > > path to your emacs binary instead of using a symlink, does it compile? > > I'm just going to wait, not touch anything more, and wait until the Emacs > developers fix things. I should have realized it wasn't an Org problem. > > It's often fun to keep on top of the current Emacs development tree, but > then > things like this happen. Ah well! > > Bill > -- > William Denton :: Toronto, Canada --- Listening to Art: > https://listeningtoart.org/ > https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/ > Caveat lector. --- STAPLR: http://staplr.org/
Re: [O] Compile failure
On 24 June 2019, Robert Pluim wrote: Thatʼs an emacs issue, not an org-mode issue. If you specify the full path to your emacs binary instead of using a symlink, does it compile? I'm just going to wait, not touch anything more, and wait until the Emacs developers fix things. I should have realized it wasn't an Org problem. It's often fun to keep on top of the current Emacs development tree, but then things like this happen. Ah well! Bill -- William Denton :: Toronto, Canada --- Listening to Art: https://listeningtoart.org/ https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/ Caveat lector. --- STAPLR: http://staplr.org/
Re: [O] Compile failure
> On Mon, 24 Jun 2019 08:49:07 -0400 (EDT), William Denton > said: William> The current source isn't compiling, at least for me (this is with an William> Emacs freshly compiled from source): William> $ make William> make -C doc clean; make -C lisp clean; William> make[1]: Entering directory '/usr/local/src/org-mode/doc' William> rm -f org orgguide *.pdf *.html *_letter.tex org-version.inc \ William> org-version.tex *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys \ William> *.pg *.pgs *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps William> make[1]: Leaving directory '/usr/local/src/org-mode/doc' William> make[1]: Entering directory '/usr/local/src/org-mode/lisp' William> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc William> org-install.elc William> rm -f *.elc William> make[1]: Leaving directory '/usr/local/src/org-mode/lisp' William> make -C lisp compile William> make[1]: Entering directory '/usr/local/src/org-mode/lisp' William> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc William> org-install.elc William> org-version: 9.2.4 (release_9.2.4-381-g226363) William> emacs: could not resolve realpath of "(null)": No such file or directory William> Makefile:70: recipe for target 'org-version.el' failed William> make[1]: *** [org-version.el] Error 1 William> make[1]: Leaving directory '/usr/local/src/org-mode/lisp' William> mk/targets.mk:95: recipe for target 'compile' failed William> make: *** [compile] Error 2 Thatʼs an emacs issue, not an org-mode issue. If you specify the full path to your emacs binary instead of using a symlink, does it compile? Robert
Re: [O] Compile failure
On Monday, 24 Jun 2019 at 08:49, William Denton wrote: > The current source isn't compiling, at least for me (this is with an > Emacs freshly compiled from source): [...] > emacs: could not resolve realpath of "(null)": No such file or directory I've run into this problem with the latest Emacs. I reset back to 63b29f8107 and everything is fine. There's been quite a bit of activity on Emacs the past few days and something has broken (but I haven't had time to explore the cause as I have too much work to do...). I don't know if it is related to org or not. I could not even start Emacs but I do initialize org at startup so... -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.4-379-g1b74ae
