Re: octave-config-h?

[Keith Keith]

I hope I'm replying to this correctly.  I never had a problem caused by calling ./bootrstrap ./configure and make from the same folder that they're in.  I just recloned the hg archive and built it in the octave folder and it has definitely gone past the point where I was getting the errors concerning octave-config.h.  When I got was getting the errors I was able to reproduce it by trying to build in octave/ and in octave/.BUILD32.  So I'd say its OK to build in the hg archive folder.  It's weird that we're getting the same errors but mine has disappeared.  I'm not familiar with make or the octave source yet so I'm sorry the only help I can be is try something and see if it works.

On Fri, Feb 12, 2016 at 6:44 PM, Ben Abbott <address@hidden> wrote:

> On Feb 12, 2016, at 3:24 PM, John W. Eaton <address@hidden> wrote:
>
> On 02/12/2016 09:02 AM, Ben Abbott wrote:
>>> On Feb 12, 2016, at 7:33 AM, Ben Abbott <address@hidden> wrote:
>>>
>>> John,
>>>
>>> Did the new octave-config.h not get pushed, or is it not ready yet?
>>>
>>>  GEN      libinterp/corefcn/LSODE-opts.cc
>>>  GEN      libinterp/corefcn/Quad-opts.cc
>>>  GEN      libinterp/octave.df
>>> In file included from libinterp/octave.cc:42:
>>> ./liboctave/util/cmd-edit.h:26:10: fatal error: 'octave-config.h' file not found
>>> #include "octave-config.h”
>>>
>>> Ben
>>
>> I should have spent more time reviewing the recent changesets. Im able to use the new-file, mk-octave-config-h.sh, to generate octave-config.h.
>>
>>      ./build-aux/mk-octave-config-h.sh config.h > octave-config.h
>>
>> It looks to me like this should happen automatically
>>
>> $ fgrep -in octave-config.h Makefile.am
>> 148:  octave-config.h \
>> 175:octinclude_HEADERS += octave-config.h oct-conf-post.h
>> 191:octave-config.h: config.h build-aux/mk-octave-config-h.sh
>>
>> Expanding the relevant lines …
>>
>> 191 octave-config.h: config.h build-aux/mk-octave-config-h.sh
>> 192   $(AM_V_GEN)$(top_srcdir)/build-aux/mk-octave-config-h.sh $< > address@hidden && \
>> 193   mv address@hidden $@
>>
>> Unfortunately, the build process doesn’t generate octave-config.h for me. I’m trying to build on Mac OS X and am using Fink for dependencies (anyone else?).
>>
>> Perhaps there is a dependency requirement I’m lacking (maybe my version is too old?). Rather than dumping everything into email, I’ll wait for feedback.
>
> It should happen automatically after this change:
>
>  http://hg.savannah.gnu.org/hgweb/octave/rev/5ddc9b61a0c4
>
> Is octave-config.h listed in BUILT_SOURCES in your Makefile?
>
> jwe

Looking at my Makefile, I see octave-config.h is present in BUILT_SOURCES.

 5037 BUILT_SOURCES = $(BUILT_INCS) $(BUILT_LIBOCTAVE_OPERATORS_SOURCES) \
 5038   $(GENERATED_MAKE_BUILTINS_INCS) libinterp/build-env.cc \
 5039   libinterp/builtin-defun-decls.h libinterp/builtins.cc \
 5040   libinterp/corefcn/oct-errno.cc \
 5041   libinterp/corefcn/oct-tex-lexer.cc \
 5042   libinterp/corefcn/oct-tex-parser.cc \
 5043   libinterp/corefcn/oct-tex-symbols.cc \
 5044   libinterp/operators/ops.cc libinterp/parse-tree/lex.cc \
 5045   libinterp/parse-tree/oct-parse.cc $(am__append_15) \
 5046   $(GENERATED_TEST_FILES) octave-config.h run-octave \
 5047   $(DIRSTAMP_FILES) $(am__append_65) $(am__append_66)

I tried a fresh bootstrap, configure, & make, but octave-config.h is still not being automatically generated.

  GEN      libinterp/corefcn/defaults.h
libinterp/corefcn/defaults.h is unchanged
  GEN      libinterp/corefcn/graphics-props.cc
libinterp/corefcn/graphics-props.cc is unchanged
  GEN      libinterp/corefcn/graphics.h
libinterp/corefcn/graphics.h is unchanged
  GEN      libinterp/corefcn/mxarray.h
libinterp/corefcn/mxarray.h is unchanged
  GEN      libinterp/version.h
libinterp/version.h is unchanged
  GEN      libinterp/build-env.cc
libinterp/build-env.cc is unchanged
  GEN      libinterp/octave.df
In file included from libinterp/octave.cc:42:
./liboctave/util/cmd-edit.h:26:10: fatal error: 'octave-config.h' file not found
#include "octave-config.h"

I’ve never been successful having a build tree separate from my archive. Thus, I’m building in hg archive. Is there any reason that may produce such a problem?

Ben