Re: problem with docs (Was: make check?)

[Mike Miller]

On Sun, Jul 10, 2016 at 20:33:36 -0400, Ben Abbott wrote:
> > On Jul 10, 2016, at 8:09 AM, Ben Abbott <address@hidden> wrote:
> > 
> > I tried “make check” for the default branch and encountered the error below.
> > 
> > warning: docstring file 
> > '/sw/local/share/octave/4.1.0+/etc/built-in-docstrings' not found
> > error: no such file, 
> > '/Users/bpabbott/Development/mercurial/default/build/test/--no-init-path'
> > error: source: error sourcing file 
> > '/Users/bpabbott/Development/mercurial/default/build/test/--no-init-path'
> > error: execution exception in --no-init-path
> > 
> > Is anyone else seeing this?
> > 
> > $ hg tip
> > pulling from /Users/bpabbott/Development/mercurial/octave
> > searching for changes
> > no changes found
> > changeset:   22081:a5a99a830c8c
> > bookmark:    @
> > tag:         tip
> > user:        Mike Miller <address@hidden>
> > date:        Thu Jul 07 13:55:37 2016 -0700
> > summary:     Set default floating point unit state when initializing the 
> > interpreter (bug #48418)
> > 
> > Ben
> 
> Ok. My mistake. It’s not “make check” that fails. I’m just no longer able to 
> build the docs.
> 
> I suspect a problem with the changeset below.
> 
>       http://hg.savannah.gnu.org/hgweb/octave/rev/df50d42d4b1b
> 
>  I’m not building in the source tree, but have started a build to see if that 
> works.
> 
> The warnings/errors I see are below. 

Can you try again with

  http://hg.savannah.gnu.org/hgweb/octave/rev/66db9a493c84

or later? That should fix the incorrect handling of command line
options.

-- 
mike