[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #46863] build_packages.m not up to date.
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #46863] build_packages.m not up to date. |
Date: |
Sun, 10 Jan 2016 12:26:33 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 |
Update of bug #46863 (project octave):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #1:
While you are quite right, but you report several distinct issues here.
1. As to build_packages.m not being up to date:
This is a duplicate of bug #46761 and some other bug reports. AFAICS in the
development version of (mxe-)Octave, build_packages is largely op to date. It
should also be up-to-date in the octave-4.0.1 binary installer (release
candidate); did you try that one? it's here:
ftp://alpha.gnu.org/gnu/octave/octave-4.0.1-rc1-installer.exe
(beta testers needed !)
Please try that one and report back here if build_packages.m there works fine
for you.
2. The long list of compiler messages and warnings is due to individual
Octave-Forge packages which don't always exactly match the development status
of core Octave; however, that has nothing to do with build_packages.m
It would really help if you could sort out what OF packages give what warnings
and enter separate bug reports for that.
(You see, if an O-F package builds with warnings but otherwise works fine,
Octave developers rather tackle other more urgent issues :-) )
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46863>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/