octave-maintainers
[Top][All Lists]
Advanced

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

Re: 2 problems with 3.3.92


From: Rik
Subject: Re: 2 problems with 3.3.92
Date: Mon, 07 Feb 2011 17:52:49 -0800

marco atzeri wrote:
> On Mon, Feb 7, 2011 at 6:58 PM, Rik  wrote:
>>> John,
>>> two problems are still there
>>>
>>> 1) building in a separate dir, documentation fails as
>>>    contributors.texi is expected in the build dir, but it is only
>>> available in the src tree.
>>>
>>> ------------------------------------------------------------------------
>>> make -C doc/interpreter ../../AUTHORS
>>> make[3]: Entering directory
>>> `/pub/cygports/octave/octave-3.3.92-1/build/doc/interpreter'
>>> rm -f AUTHORS
>>> /bin/sh 
>>> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/build-aux/missing
>>> --run makeinfo -D AUTHORSONLY \
>>>          --no-validate --no-headers --no-split --output AUTHORS preface.texi
>>> preface.texi:82: @include `contributors.texi': No such file or directory.
>>> makeinfo: Removing output file `AUTHORS' due to errors; use --force to 
>>> preserve.
>>> make[3]: [../../AUTHORS] Error 1 (ignored)
>>> mv AUTHORS ../../AUTHORS
>>> mv: cannot stat `AUTHORS': No such file or directory
>>> make[3]: *** [../../AUTHORS] Error 1
>>> ----------------------------------------------------------
>> There is something wrong here.  If you are building from a tarball it
>> contains all of the documentation pre-built.  We specifically do this
>> because some distributions versions of Texinfo are weak.  At least on a
>> Debian system, building in a separate directory from the source works fine.
> 
> on cygwin with our build system cygport
> octave doc is rebuilt, while all the rest no
> 
>> I would start by untarring the 3.3.92 tarball and verifying that the
>> AUTHORS file is there and that the timestamp is newer than
>> contributors.texi in doc/interpreter.  This is the case for me.
>>
> same
> 
>> If this checks out then there may be an issue with your version of GNU Make
>> and VPATH builds.  For example, when I try a test make of AUTHORS in my
>> build directory I get
>> ----------------------------------------------------------
>> rik:~/downloads/build: make -n AUTHORS
>> make -C doc/interpreter ../../AUTHORS
>> make[1]: Entering directory `/home/rik/downloads/build/doc/interpreter'
>> make[1]: `../../../octave-3.3.92/doc/interpreter/../../AUTHORS' is up to 
>> date.
>> make[1]: Leaving directory `/home/rik/downloads/build/doc/interpreter'
>> ----------------------------------------------------------
>>
Is this after a successful build with AUTHORS in the build directory?  The
first invocation you quoted showed that AUTHORS needed to be rebuilt, and
that was causing the problem.  This invocation is showing that AUTHORS is
up-to-date and no commands will be executed.  It can't be both things.

>> Note that the file it checks for the timestamp is not './AUTHORS' in the
>> build directory, but a huge relative path name to the source directory.
>>
> not here
> 
> $ make -n AUTHORS
> make -C doc/interpreter ../../AUTHORS
> make[1]: Entering directory
> `/pub/cygports/octave/octave-3.3.92-1/build/doc/interpreter'
> make[1]: `../../AUTHORS' is up to date.
> make[1]: Leaving directory
> `/pub/cygports/octave/octave-3.3.92-1/build/doc/interpreter'
> 
> Please note that cygwin build system runs autoreconf on source tree
> before the configure step in the build tree.
This might be the problem, but I'm not sure.  I never run autoreconf.

Here is one test:
tar xf octave-3.3.92.tar.gz
mkdir build
cd build
../octave-3.3.92/configure
make AUTHORS

There is no need to 'make' the rest of Octave to test this.  On my system
there is no AUTHORS file in the build directory and the make command
reports that AUTHORS is up to date.

If that works, you could try running the autoreconf step and see if this
causes the documentation to require re-building.

--Rik
> 
>> What does your make log show for the two DOCSTRINGS files in src/ and
>> scripts/?  If it is mistakenly re-building these then this will trigger a
>> re-build of all the .texi files which would require AUTHORS to be re-built.
>>
> 
> I guess the first triggers the rebuild
> 
> if [ "x/pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/src" !=
> "x." ] && [ -f 
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/src/DOCSTRINGS
> ] && [ ! -f DOCSTRINGS ]; then \
>                 cp
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/src/DOCSTRINGS
> DOCSTRINGS; \
>                 touch -r
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/src/DOCSTRINGS
> DOCSTRINGS; \
>         fi
> creating .DOCSTRINGS from .cc source files
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/move-if-change
> .DOCSTRINGS DOCSTRINGS
> touch .DOCSTRINGS
> 
> 
> 
> if [ "x/pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/scripts"
> != "x." ] && [ -f
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/scripts/DOCSTRINGS
> ] && [ ! -f DOCSTRINGS ]; then \
>                 cp
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/scripts/DOCSTRINGS
> DOCSTRINGS; \
>                 touch -r
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/scripts/DOCSTRINGS
> DOCSTRINGS; \
>         fi
> mv testfun/PKG_ADD-t testfun/PKG_ADD
> mv time/PKG_ADD-t time/PKG_ADD
> creating .DOCSTRINGS from .m script files
> mv statistics/distributions/PKG_ADD-t statistics/distributions/PKG_ADD
> mv plot/PKG_ADD-t plot/PKG_ADD
> /pub/cygports/octave/octave-3.3.92-1/src/octave-3.3.92/move-if-change
> .DOCSTRINGS DOCSTRINGS
> DOCSTRINGS is unchanged
> touch .DOCSTRINGS
> 
> 
>>> 3) octave.info is updated/modified in the src tree
>> This is probably the same error in another form.  The documentation should
>> not require rebuilding.
> 
> likely as it is the only rebuilt. all the rest is unchanged
> 
>> --Rik
>>
> 
> Marco
> 



reply via email to

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