octave-maintainers
[Top][All Lists]
Advanced

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

Re: (mxe-octave) forge package build issues with compiler and dev octave


From: JohnD
Subject: Re: (mxe-octave) forge package build issues with compiler and dev octave
Date: Wed, 12 Jul 2017 08:09:01 -0400

> 
> Message: 3
> Date: Tue, 11 Jul 2017 22:35:16 -0700 (PDT)
> From: PhilipNienhuis <address@hidden>
> To: address@hidden
> Subject: Re: (mxe-octave) forge package build issues with compiler and
>       dev     octave
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> John W. Eaton wrote
> > On 07/10/2017 01:16 PM, John W. Eaton wrote:
> >> On 07/08/2017 09:56 PM, Mike Miller wrote:
> >>
> >>> I think it's fair for gnulib to put a libtool-specific option into a
> >>> variable called LTLIBICONV. The problem is when those options get used
> >>> by a non-libtool-aware build system, like calling gcc directly. Gnulib
> >>> also provides the corresponding LIBICONV for use by non-libtool-based
> >>> builds. This variable does not contain the -R option.
> >>>
> >>> LTLIBICONV should be used for building Octave, but maybe LIBICONV
> should
> >>> be exported for use by mkoctfile and other build tools.
> >>
> >> Thanks.  I pushed a couple of changesets and now default-octave cross
> >> compiles.
> >>
> >> The next issue is that of-control is failing to build, apparently
> >> because of a change I made to octave-config.  Looking at that now.
> >
> > I checked in two more changes for mxe-octave to allow of-control and
> > of-general to build with current Octave sources:
> >
> >    http://hg.octave.org/mxe-octave/rev/eb8b37422e16
> >    http://hg.octave.org/mxe-octave/rev/60b45297db4a
> >
> > Now the following packages fail to build, all apparently due to the same
> > obsolete(?) configure.base file that is not used in other Octave Forge
> > packages:
> >
> >    of-linear-algebra
> >    of-netcdf
> >    of-windows
> 
> Yes there were earlier issues with those packages caused by their old
> configure-make setup:
> http://savannah.gnu.org/bugs/?41131, sse comment #5
> 
> After just deleting these 3 packages from the pertinent Makefile rule,
> of-database also fails to build with:
> 
> :
> x86_64-w64-mingw32-g++ -std=gnu++11 -c
> -I/home/philip/devel/octdev/mxe/mxe_w64_qt4_201706010/usr/x86_64-w64-
> mingw32/include
> -I/home/philip/devel/octdev/mxe/mxe_w64_qt4_201706010/usr/x86_64-w64-
> mingw32/include/octave-4.3.0+/octave/..
> -I/home/philip/devel/octdev/mxe/mxe_w64_qt4_201706010/usr/x86_64-w64-
> mingw32/include/octave-4.3.0+/octave
> -I/home/philip/devel/octdev/mxe/mxe_w64_qt4_201706010/usr/x86_64-w64-
> mingw32/include
> -pthread -fopenmp -g -O2 -Wno-deprecated-declarations
> -I/home/philip/devel/octdev/mxe/mxe_w64_qt4_201706010/usr/include
> bytea2var.cc -o bytea2var.o
> bytea2var.cc: In function 'octave_value_list Fbytea2var(const
> octave_value_list&, int)':
> bytea2var.cc:97:22: error: 'flt_fmt_unknown' is not a member of
> 'oct_mach_info'
>        if (flt_fmt == oct_mach_info::flt_fmt_unknown)
>                       ^
> Makefile:95: recipe for target 'bytea2var.o' failed
> make[2]: *** [bytea2var.o] Error 1
> 
> 
> Dropping that one as well, the cross-build continues fine.
> 
> So it is just those 4 of-packages that have issues being (cross-)built.
> 
> Philip
> 
> 
> 

I pushed some changes to the windows repo for the windows package - I'll
push some changes for fixing the current windows package in mxe today

I have a fix for database, which I believe failed from these changes:
http://hg.savannah.gnu.org/hgweb/octave/rev/a732be902061, I will post up as
a new bug today
 
Netcdf was posted on bug #51443, fixed and currently waiting release as
1.0.12





reply via email to

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