3.8 Release Candidate Builds

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

3.8 Release Candidate Builds

Rik-4
Everyone,

We will soon be in a position to start building release candidates and getting feedback on Octave 3.8.  But, we don't need to go to users with an RC1 when we already know there are bugs in the build process.  I have culled the list of "Configuration and Build System" bugs from savannah and put them on the 3.8 Bug Fix List (http://wiki.octave.org/3.8_Bug_Fix_List#Bugs_marked_Configuration_and_Build_System).  And to be thorough, here they are:
  • Owner: ??? #40358 Octave Java classes missing on 64-bit Ubuntu 12.04
  • Owner: ??? #40356 Please ship an AppData file upstream
  • Owner: ??? #40321 MXE / MinGW - mkoctfile fails (& doesn't pick up compile flags)
  • Owner: ??? #40273 'sed' is used even if a different value for 'SED' is specified during configure
  • Owner: ??? #40252 Make GUI compatible with both Qt4 and Qt5
  • Owner: ??? #40111 Support runtime selection of Java version on Linux and Unix systems
  • Owner: ??? #39856 Cannot compile an Oct-File in Windows 7 64 or Vista 64 oct file
  • Owner: ??? #39465 configure needs jvm.dll for Windows builds
  • Owner: ??? #39454 Fix building core Java support for MinGW builds
  • Owner: ??? #39446 MXE-Octave: LAPACK build mixes MinGW and MSVC
  • Owner: ??? #38928 confugure -> hdf5 doesn't handle path through
  • Owner: ??? #38776 Tests in private functions cannot be tested directly
  • Owner: ??? #38351 mkoctfile -p returns wrong flags on mingw.
  • Owner: ??? #36477 use XDG dirs instead of HOME
  • Owner: ??? #36064 MAGICK_X extra flags are shadowed by system CPPFLAGS and LDFLAGS
  • Owner: ??? #35207 add gl2ps to the configure script
  • Owner: ??? #34301 Can't compile oct files using gcc -fvisibility=hidden option
  • Owner: ??? #34169 Support -f compiler flags in mkoctfile

We don't need to fix every one just now, but I think it would be a good idea to knock off half of them before we start in with the release candidate cycle.

Cheers,
Rik
Reply | Threaded
Open this post in threaded view
|

Re: 3.8 Release Candidate Builds

PhilipNienhuis
Rik-4 wrote
Everyone,

We will soon be in a position to start building release candidates and
getting feedback on Octave 3.8.  But, we don't need to go to users with an
RC1 when we already know there are bugs in the build process.  I have
culled the list of "Configuration and Build System" bugs from savannah and
put them on the 3.8 Bug Fix List
(http://wiki.octave.org/3.8_Bug_Fix_List#Bugs_marked_Configuration_and_Build_System).
And to be thorough, here they are:

  * Owner: ??? #40358 <https://savannah.gnu.org/bugs/?40358> Octave Java
    classes missing on 64-bit Ubuntu 12.04
  * Owner: ??? #40356 <https://savannah.gnu.org/bugs/?40356> Please ship an
    AppData file upstream
  * Owner: ??? #40321 <https://savannah.gnu.org/bugs/?40321> MXE / MinGW -
    mkoctfile fails (& doesn't pick up compile flags)
  * Owner: ??? #40273 <https://savannah.gnu.org/bugs/?40273> 'sed' is used
    even if a different value for 'SED' is specified during configure
  * Owner: ??? #40252 <https://savannah.gnu.org/bugs/?40252> Make GUI
    compatible with both Qt4 and Qt5
  * Owner: ??? #40111 <https://savannah.gnu.org/bugs/?40111> Support
    runtime selection of Java version on Linux and Unix systems
  * Owner: ??? #39856 <https://savannah.gnu.org/bugs/?39856> Cannot compile
    an Oct-File in Windows 7 64 or Vista 64 oct file
  * Owner: ??? #39465 <https://savannah.gnu.org/bugs/?39465> configure
    needs jvm.dll for Windows builds
  * Owner: ??? #39454 <https://savannah.gnu.org/bugs/?39454> Fix building
    core Java support for MinGW builds
  * Owner: ??? #39446 <https://savannah.gnu.org/bugs/?39446> MXE-Octave:
    LAPACK build mixes MinGW and MSVC
  * Owner: ??? #38928 <https://savannah.gnu.org/bugs/?38928> confugure ->
    hdf5 doesn't handle path through
  * Owner: ??? #38776 <https://savannah.gnu.org/bugs/?38776> Tests in
    private functions cannot be tested directly
  * Owner: ??? #38351 <https://savannah.gnu.org/bugs/?38351> mkoctfile -p
    returns wrong flags on mingw.
  * Owner: ??? #36477 <https://savannah.gnu.org/bugs/?36477> use XDG dirs
    instead of HOME
  * Owner: ??? #36064 <https://savannah.gnu.org/bugs/?36064> MAGICK_X extra
    flags are shadowed by system CPPFLAGS and LDFLAGS
  * Owner: ??? #35207 <https://savannah.gnu.org/bugs/?35207> add gl2ps to
    the configure script
  * Owner: ??? #34301 <https://savannah.gnu.org/bugs/?34301> Can't compile
    oct files using gcc -fvisibility=hidden option
  * Owner: ??? #34169 <https://savannah.gnu.org/bugs/?34169> Support -f
    compiler flags in mkoctfile


We don't need to fix every one just now, but I think it would be a good
idea to knock off half of them before we start in with the release
candidate cycle.

Cheers,
Rik
I think Anirudha already has a fix for bug #39465 in his mxe-octave branch.

<OT> I think it is about time that his work gets merged into the 'formal' mxe-octave branch.

Philip