bugGNU Octave - Bugs: bug #47831, mercurial build writes files to...

 
 

bug #47831: mercurial build writes files to source tree doc/{interpreter,liboctave}

Submitted by:  Dan Sebald <sebald>
Submitted on:  Mon 02 May 2016 11:31:56 PM UTC  
 
Category:  Configuration and Build System Severity:  1 - Wish
Priority:  1 - Later Item Group:  Feature Request
Status:  Postponed Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  dev Operating System:  Any

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 03 May 2016 04:39:55 PM UTC, comment #5: 

Yeah, we looked at this a couple weeks ago, Automake has partial support for generating docs in the build directory, but not completely.

This is not a bug in normal circumstances, because the source distribution contains the docs already built.

Mike Miller <mtmiller>
Project Administrator
Tue 03 May 2016 04:53:53 AM UTC, comment #4: 

It might be useful if it actually worked.  I tried it and it doesn't do the complete job.

If you can make it work, then great.  Submit a patch.

John W. Eaton <jwe>
Project Administrator
Tue 03 May 2016 03:55:28 AM UTC, comment #3: 

Does this option sound helpful in some way?

https://www.gnu.org/software/automake/manual/html_node/List-of-Automake-options.html

info-in-builddir

    Instruct Automake to place the generated .info files in the builddir rather than in the srcdir. Note that this might make VPATH builds with some non-GNU make implementations more brittle.

If so, I'll have a look at it.  Is it aclocal.m4 where the options for automake are defined?

Dan Sebald <sebald>
Tue 03 May 2016 02:51:58 AM UTC, comment #2: 

The rules that automake generates for building INFO files write in the source tree.  I look at it, but I'm not going to fight automake on this one.

It was also simplest to make the rules for the DOCSTRINGS files work properly if they write to the source tree.

John W. Eaton <jwe>
Project Administrator
Tue 03 May 2016 12:08:46 AM UTC, comment #1: 

Just noting that an "hg status" doesn't indicate that the files I listed above should not be in the repository.  It's odd though that build-generated or build-touched files would be there.  This ties in with

https://savannah.gnu.org/bugs/?47832

a couple of DOCSTRINGS files generated by the build process.

Dan Sebald <sebald>
Mon 02 May 2016 11:31:56 PM UTC, original submission:  

This error showed up all of a sudden:

cp: cannot create regular file ‘../octave/doc/interpreter/stamp-vti’: Permission denied
make[2]: *** [../octave/doc/interpreter/stamp-vti] Error 1
make[2]: Leaving directory `/home/user/octave/octave/build1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/octave/octave/build1'
make: *** [all] Error 2

It has to do with the way I go about building. I had posted about segfault in documentation; that occurred when I was building in the system directory as root. So I figured I'd try doing a completely fresh build as a user.

Looking at the source tree, I see some files that must have been generated by the build process:

[snipping all files that have the user ownership]

sebald@ ~/octave/octave/build1 $ ls -l ../octave/doc/interpreter/
total 4212
-rw-r--r-- 1 root   root    77660 May  2 17:09 octave.info
-rw-r--r-- 1 root   root   311839 May  2 17:08 octave.info-1
-rw-r--r-- 1 root   root   290920 May  2 17:08 octave.info-2
-rw-r--r-- 1 root   root   300940 May  2 17:08 octave.info-3
-rw-r--r-- 1 root   root   297686 May  2 17:08 octave.info-4
-rw-r--r-- 1 root   root   299211 May  2 17:08 octave.info-5
-rw-r--r-- 1 root   root   318235 May  2 17:08 octave.info-6
-rw-r--r-- 1 root   root   285106 May  2 17:09 octave.info-7
-rw-r--r-- 1 root   root   652861 May  2 17:09 octave.info-8
-rw-r--r-- 1 root   root    11118 May  2 17:09 octave.info-9
-rw-r--r-- 1 root   root       92 May  2 14:38 stamp-vti
-rw-r--r-- 1 root   root       92 May  2 14:38 version-octave.texi

sebald@ ~/octave/octave/build1 $ ls -l ../octave/doc/liboctave/
total 428
-rw-r--r-- 1 root   root   235854 May  2 15:28 liboctave.info
-rw-r--r-- 1 root   root       92 May  2 15:28 stamp-1
-rw-r--r-- 1 root   root       92 May  2 15:28 version-liboctave.texi

Dan Sebald <sebald>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by sebald (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-05-03 mtmiller Severity3 - Normal => 1 - Wish
        Priority5 - Normal => 1 - Later
        Item GroupBuild Failure => Feature Request
        StatusNone => Postponed
        Operating SystemGNU/Linux => Any
        SummaryBuild-generated files appearing in source-tree doc/<subdirectories> => mercurial build writes files to source tree doc/{interpreter,liboctave}

    Back to the top


    Powered by Savane 3.5