octave-maintainers
[Top][All Lists]
Advanced

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

Re: Snapshot 3.5.91


From: marco atzeri
Subject: Re: Snapshot 3.5.91
Date: Sun, 25 Dec 2011 08:35:40 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0

On 12/25/2011 2:31 AM, Rik wrote:
The snapshot builds and all tests pass on Kubuntu 10.04.  A caveat to this
is that my system is a developer's system and has every library necessary
installed and easily found by configure.

I don't know if this is just my system, but the documentation had to be
re-built during the build.  This shouldn't happen and it makes it harder on
systems where a complete Texinfo is not available.

In this case, the problem was that the file src/DOCSTRINGS embedded in the
tar.gz file differed by a single space from the DOCSTRINGS file created
during the local build.  Make detected the difference and caused a full
rebuild of the documentation.  The problem is line 10009 of src/DOCSTRINGS
where "codes " should just be "codes".  I went back, with Mercurial, to
revision ss-3-5-91 and built a new tarball and the DOCSTRINGS file is
correct.  The docstring for daspk_options comes from src/DASPK-opts.cc, but
this file is auto-generated from liboctave/DASPK-opts.in.  The build chain
is pretty long at this point.  It might be necessary to delete
src/*-opts.cc and have these files be re-generated before creating a tar
ball.  The Make rules must be mostly right, however, because I can do
'touch ../liboctave/DASPK-opts.in; make' and everything gets rebuilt.

--Rik


also on cygwin the documentation is rebuilt, but this a defect
already present on 3.4.x so I was ignoring it.

Checking your hint, I found two points where the src/DOCSTRINGS
files differ:
-------------------------------------------------------------------------
--- src/octave-3.5.91/src/DOCSTRINGS    2011-12-24 01:02:08.000000000 +0100
+++ build/src/DOCSTRINGS        2011-12-24 23:32:38.487392700 +0100
@@ -7022,14 +7022,6 @@
 or that may be passed to @code{fcntl} to set the write mode to append.
@seealso{fcntl, O_ASYNC, O_CREAT, O_EXCL, O_NONBLOCK, O_RDONLY, O_RDWR, O_SYNC, O_TRUNC, O_WRONLY}
 @end deftypefn
-^_O_ASYNC
address@hidden O_ASYNC src/syscalls.cc
--*- texinfo -*-
address@hidden {Built-in Function} {} O_ASYNC ()
-Return the numerical value of the file status flag that may be
-returned by @code{fcntl} to indicate asynchronous I/O.
address@hidden, O_APPEND, O_CREAT, O_EXCL, O_NONBLOCK, O_RDONLY, O_RDWR, O_SYNC, O_TRUNC, O_WRONLY}
address@hidden deftypefn
 ^_O_CREAT
 @c O_CREAT src/syscalls.cc
 -*- texinfo -*-
@@ -10006,7 +9998,7 @@
 A vector of the same length as the state specifying the type of
 inequality constraint.  Each element of the vector corresponds to an
 element of the state and should be assigned one of the following
-codes
+codes

 @table @asis
 @item -2
------------------------------------------------------------------------


no idea why I miss the O_ASYNC paragraph.

Marco


reply via email to

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