[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Octave Forge] Octave 4.0 call for packages
From: |
JohnD |
Subject: |
RE: [Octave Forge] Octave 4.0 call for packages |
Date: |
Fri, 10 Apr 2015 16:05:15 -0400 |
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of
> Carnë Draug
> Sent: Tuesday, April 07, 2015 7:13 AM
> To: John Donoghue
> Cc: octave-maintainers; Mike Miller
> Subject: Re: [Octave Forge] Octave 4.0 call for packages
>
> On 6 April 2015 at 23:31, John Donoghue <address@hidden>
> wrote:
> > On 04/06/2015 06:16 PM, address@hidden wrote:
> >>
> >> Message: 4
> >> Date: Mon, 6 Apr 2015 21:17:38 +0100
> >> From: Carn? Draug<address@hidden>
> >> To: Mike Miller<address@hidden>
> >> Cc: Octave Maintainers<address@hidden>
> >> Subject: Re: [Octave Forge] Octave 4.0 call for packages
> >> Message-ID:
> >>
> >> <CAPOrs_1RNATmWYF9unM6NW7QDUxtJT24G-
> address@hidden>
> >> Content-Type: text/plain; charset=UTF-8
> >>
> >> On 15 March 2015 at 15:04, Mike Miller<address@hidden> wrote:
> >>>
> >>> >[...]
> >>> >
> >>> >The imminent Octave 4.0.0 release will be the first to supply an
> >>> >official binary distribution of Octave for Windows operating systems.
> >>> >This distribution will include a set of Octave Forge packages that
> >>> >may be installed at the user's option. This is why we would like to
> >>> >have compatible packages ready to incorporate into the next release
> >>> >candidate for further testing.
> >>> >
> >>
> >> Can users that have installed Octave with such installer then install
> >> more packages and other versions of those packages?
> >>
> >> If we are starting to distribute binaries of Octave core, would be
> >> nice if we can also distribute binaries for the packages, specially
> >> since the release cycle of core and OF is quite different.
> >>
> >> Carn?
I just tried installing all of packages that currently in the active list on
octave forge in Windows using octave 4.0.0 rc2 (32 bit)
This is trying to install on the windows machine, not attempting cross compile,
using what is available as the 'current' package on octave-forge.
Heres the following results:
bim 1.1.5 - OK
cgi 0.1.0 - OK
communications 1.2.1 - OK - warns unusable help found
control 2.8.0 - OK
database 2.3.1 - OK
dataframe 1.1.0 - OK
data-smoothing 1.3.0 - OK
dicom 0.1.1 - FAILED - Error with octave_map - Bug #44624
divand 1.1.2 - OK
econometrics 1.1.1 - OK
fem-fenics 0.0.3 - FAILED - requires eigen3 lib in mxe-octave, so currently
an expected failure
financial 0.4.0 - OK
fits 1.0.5 - OK
fl-core 1.0.0 - FAILED - has been patched in mxe-octave - Bug #41214
fpl 1.3.4 - OK
fuzzy-logic-toolkit 0.4.4 - OK - warning about continuation markers
depreciated
ga 0.10.0 - OK - lots of warning about continuation markers depreciated
general 1.3.4 - OK
generate_html 0.1.7 - OK
geometry 1.7.0 - OK - warning on printf args - warn on cant cleanup after
self
image 2.4.0 - OK
image-acquisition 0.2.1 - FAILED - requires v4l library no in mxe-octave so
expected
instrument-control 0.2.1 - OK
interval 0.1.5 - OK
io 2.2.7 - OK
java - part of core now not tried
level-set 0.2.0 - OK
linear-algebra 2.2.2 -OK - warnings on abstract class types
lssa 0.1.2 - OK
ltfat 2.0.1 - FAILED - 'cc' not found - patched in mxe. - bug #43603
mechanics 1.3.1 - FAILED - install failure Bug #44804
miscellaneous 1.2.1 - OK
mpi 1.2.0 - FAILED - mxe has no mpi lib, so expected
msh 1.0.10 - OK
mvn 1.1.0 - OK
nan 2.7.1 - OK - warning -fPIC, shadow core funcs
ncarray 1.0.3 - OK
netcdf 1.0.6 - OK
nurbs 1.3.9 - FAILED - matrix_value - bug #44651
ocs 0.1.3 - OK - continuation marker warnings
octcdf 1.1.8 - OK
octclip 1.0.3 - OK - printf format warnings
octproj 1.1.2 - FAILED - mxe-octave needs libproj, so expected failure
odepkg 0.8.4 - FAILED - octave_map - bug #44594
optics 0.1.1 - DONE
optim 1.4.1 - DONE
optiminterp 0.3.4 - DONE
parallel 2.2.1 - FAILED - bug #41148
quaternion 2.4.0 - OK
queueing 1.2.3 - OK
secs1d 0.0.9 - OK
secs2d 0.0.8 - FAILED - Octave_map error Bug #44803
secs3d 0.0.1 - OK
signal 1.3.1 - OK
sockets 1.2.0 - OK
specfun 1.1.0 - OK - warnings on some shadows funcs
splines 1.2.7 - OK
statistics 1.2.4 - OK
stk 2.2.0 - OK
strings 1.1.0 - FAILED - pcre - Bug #44640
struct 1.0.11 - OK
symbolic 2.1.0 - OK
tsa 4.2.9 - OK - warn on shadows a core lib function
vrml 1.0.13 - OK - warnings on continuation markers
windows 1.2.1 - FAILED - Array compile errors - Bug #44180
- Re: [Octave Forge] Octave 4.0 call for packages, (continued)
- Re: [Octave Forge] Octave 4.0 call for packages, Philip Nienhuis, 2015/04/06
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/06
- Re: [Octave Forge] Octave 4.0 call for packages, Philip Nienhuis, 2015/04/07
- Re: [Octave Forge] Octave 4.0 call for packages, Mike Miller, 2015/04/07
- Re: [Octave Forge] Octave 4.0 call for packages, Philip Nienhuis, 2015/04/07
- Re: [Octave Forge] Octave 4.0 call for packages, Daniel Kraft, 2015/04/08
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/13
Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/06
Re: [Octave Forge] Octave 4.0 call for packages, John Donoghue, 2015/04/06
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/07
- RE: [Octave Forge] Octave 4.0 call for packages,
JohnD <=
- Re: [Octave Forge] Octave 4.0 call for packages, Oliver Heimlich, 2015/04/10
- Re: [Octave Forge] Octave 4.0 call for packages, Mike Miller, 2015/04/10
- Re: [Octave Forge] Octave 4.0 call for packages, Oliver Heimlich, 2015/04/11
- Re: [Octave Forge] Octave 4.0 call for packages, Oliver Heimlich, 2015/04/11
- Re: [Octave Forge] Octave 4.0 call for packages, Lukas Reichlin, 2015/04/11
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/13
Re: [Octave Forge] Octave 4.0 call for packages, Tatsuro MATSUOKA, 2015/04/10
Re: [Octave Forge] Octave 4.0 call for packages, Julien Bect, 2015/04/11
Re: [Octave Forge] Octave 4.0 call for packages, Julien Bect, 2015/04/11
Re: [Octave Forge] Octave 4.0 call for packages, Oliver Heimlich, 2015/04/11