octave-maintainers
[Top][All Lists]
Advanced

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

Re: Building devel branch with MXE


From: JohnD
Subject: Re: Building devel branch with MXE
Date: Fri, 16 Oct 2015 12:19:12 -0400

> 
> Message: 5
> Date: Fri, 16 Oct 2015 07:02:56 -0700 (PDT)
> From: PhilipNienhuis <address@hidden>
> To: address@hidden
> Subject: Re: Building devel branch with MXE
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> Rik-4 wrote
> > I'm trying to build the development branch of Octave with MXE.  I made
> > a tarball from a local repository with 'make dist-bzip2' and placed it
> > in the pkg directory of MXE.  After that I munged the octave.mk file
> > to look for version 4.1.0+.  I've now built all the prerequisites, but
> > I'm failing to build Octave itself.  First, the patch
> > octave-1-docinstall.patch doesn't apply because it is looking for
> > doc/interpreter/Makefile.in and there is now only one Makefile.in at
> > the top-level.  I just deleted the patch for the time being.  But now
> > I'm failing on something that looks more fundamental, a lack of
> > &lt;sys/times.h&gt;.  This has been in the code since 2010 so it isn't
> > a new requirement.
> >
> > /home/rik/wip/Projects_Mine/mxe-octave/tmp-octave/octave-
> 4.1.0+/libinterp/corefcn/data.cc:31:23:
> > fatal error: sys/times.h: No such file or directory  #include
> > &lt;sys/times.h&gt;
> >                        ^
> > compilation terminated.
> >
> > If I do a find in the MXE directory it is clear that there is no
> > times.h anywhere in the source tree.  Is anyone else having this
problem?
> 
> In my mxe-octave tree there's no times.h either and it is up-to-date as of
Oct
> 14., at which date I've cross-built Octave-4.1.0+ that was also up-to-date
then
> (and that runs fine on my Win7 box).
> just to be sure, I searched for but couldn't find times.h in Octave's
installation
> directory on the Windows side.
> 
> I can only suppose that you have some cruft left in your Octave build
tree.
> 
> Philip
> 
> 

When running configure for mxe, if you specify --enable-octave=default, it
doesn't have issues with the doc install patch as it is updated to work with
the current default.

I am thinking the issue you are currently seeing is due to gnulib not being
fully built with the changes in mke.
See https://savannah.gnu.org/bugs/?45578


That is also changed in the mxe default-octave .mk file








reply via email to

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