Thank you, Lionel and Rodney. That did the trick: the whole thing built,
including the documents.
Will everything actually work properly without xref? I assume xref was
required because something uses it.
I even got a build in the original directory after doing a make clean.
There are still
Could you please try again with the latest master.
If it still doesn't work, please open an issue and we'll
figure it out from there.
Best,
Lionel
> On 6 mars 2018, at 19:25, Ross Boylan wrote:
>
> On Tue, Mar 06, 2018 at 10:18:13AM -0800, Ross Boylan wrote:
> ...
>>
On Tue, Mar 06, 2018 at 10:18:13AM -0800, Ross Boylan wrote:
...
> have -no-init-file). So I renamed it and tried again in the cloned ESS3.
> Results attached. Lots of warnings, but again it seems to get through
> the ess-sas stuff that was a problem, only to fail with
>
boy...@ucsf.edu>
Date: Tuesday, March 6, 2018 at 11:41 AM
To: Rodney Sparapani <rspar...@mcw.edu>
Cc: "ross.boy...@ucsf.edu" <ross.boy...@ucsf.edu>, ess-help
<ess-help@r-project.org>
Subject: Re: [ESS] make problems with latest git
warnings, while failing later on. I've at
On Tue, Mar 06, 2018 at 02:48:27PM +, Sparapani, Rodney wrote:
> Hi Ross:
>
> I can’t reproduce your problem here. From your make
> error below, it seems that ess-sas-a.el might be tampered.
> Could you refresh that file from
> git and rebuild to check?
>
> > [ess-sas-d:] require 'ess-sas-l
Hi Ross:
I can’t reproduce your problem here. From your make
error below, it seems that ess-sas-a.el might be tampered.
Could you refresh that file from
git and rebuild to check?
> [ess-sas-d:] require 'ess-sas-l ...
> Source file `/home/ross/ESS/lisp/ess-sas-a.el' newer than
> byte-compiled