octave-maintainers
[Top][All Lists]
Advanced

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

Re: FYI: libcruft merged into liboctave


From: John W. Eaton
Subject: Re: FYI: libcruft merged into liboctave
Date: Sat, 1 Sep 2012 11:06:15 -0400

On  1-Sep-2012, Daniel J Sebald wrote:

| On 09/01/2012 01:01 AM, John W. Eaton wrote:
| > On 31-Aug-2012, Rik wrote:
| >
| > | 8/31/12
| > |
| > | All,
| > |
| > | I have refactored liboctave into multiple directories using convenience
| > | libraries.  In addition, the top-level directory and library libcruft is
| > | now a subdirectory and sublibrary of liboctave.
| > |
| > | The source tree will hopefully be slightly easier to understand for new
| > | programmers coming to Octave.  A side effect, however, has been an
| > | explosion in the number of -I include statements during the build process.
| > |
| > | As always, the exact division of files may be imperfect and is open to
| > | tinkering.
| >
| > I had to make the changes in the attached patch to get the build to
| > finish successfully.
| 
| Compilation failed here too near the end.  The patch hasn't quite worked 
| (I did both autogen.sh and configure first.)
| 
| mv numeric/Quad-opts.h-t numeric/Quad-opts.h
| (cd operators; gawk -f ../../octave/liboctave/operators/mk-ops.awk 
| prefix=mx ../../octave/liboctave/operators/mx-ops)
| gawk: fatal: can't open source file 
| `../../octave/liboctave/operators/mk-ops.awk' for reading (No such file 
| or directory)
| make[2]: *** [operators/mx-cdm-dm.h] Error 2
| make[2]: Leaving directory 
| `/usr/local/src/octave/octave/build-gui-3/liboctave'
| 
| If doing a "cd operators", then there should be another level up in the 
| file names, i.e.,
| 
| (cd operators; gawk -f ../../../octave/liboctave/operators/mk-ops.awk 
| prefix=mx ../../../octave/liboctave/operators/mx-ops)

I checked in the following change (same as I posted earlier except
for the added commit message):

  http://hg.savannah.gnu.org/hgweb/octave/rev/dd794aa84232

I don't know why you are seeing the failure.  It works for me when
building in a clean directory tree.

jwe


reply via email to

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