Wed 03 Jun 2015 02:09:27 AM UTC, comment #12:
I believe this bug report is obsolete, the odepkg hg repo has been updated and odepkg 0.8.5 has been released and works with Octave 4.0.
|
Tue 02 Jun 2015 04:41:42 PM UTC, comment #11:
Retagging release from 4.0.0-rc2 to 4.0.0.
|
Thu 16 Apr 2015 11:32:43 PM UTC, comment #10:
Sorry the last post without revise by myself
John wrote:
> I don't believe it requires 4.0.0, however it may need the .NOTPARALLEL: in the Makefile?
I have confirmed that source of mercurial repository could be complied both 3.8 and 4.0 on both Ubuntu 14.04 and windows 7 using octave 4.0.0 rc2. (It was done before very recently change of source of mercurial repository.)
|
Thu 16 Apr 2015 11:29:37 PM UTC, comment #9:
John wrote:
> I don't believe it requires 4.0.0, however it may need the .NOTPARALLEL: in the Makefile?
I have confirm that the source of mercurial repository could be complied both 3.8 and 4.0. (It was done before very recently change of source of mecurial repository.)
|
Thu 16 Apr 2015 06:02:28 PM UTC, comment #8:
Tried cross compile - it does pull wrong values in the configure script, however doesn't appear actually use those values.
ie: SHLEXT, canonical_host_type, OCTAVE_VERSION, so appears to compile ok.
|
Thu 16 Apr 2015 05:50:57 PM UTC, comment #7:
I don't believe it requires 4.0.0, however it may need the .NOTPARALLEL: in the Makefile?
See https://savannah.gnu.org/bugs/?44594
The make process will probably fail when attempting a cross compile as runs native octave to get some of its settings in configure.
I haven't tried cross compile yet to see.
When attempting a native install in windows I get the following issues:
and on pkg load:
|
Thu 16 Apr 2015 04:34:51 PM UTC, comment #6:
Do these patches still work with the current
version in the mercurial repository on Octave-Forge?
Are they still needed?
I see the patches bump the minimum required version
of Octave to 4.0, is it really needed? Is there something
in these changes that breaks compatibility with 3.8?
|
Fri 10 Apr 2015 03:15:16 PM UTC, comment #5:
sorry, I wrote that comment in the wrong bug report
|
Fri 10 Apr 2015 03:14:07 PM UTC, comment #4:
I have installed specfun in the last dev version, and it compiled without warnings
|
Wed 08 Apr 2015 11:47:25 PM UTC, comment #3:
See the thread:
http://octave.1599824.n4.nabble.com/Octave-Forge-Octave-4-0-call-for-packages-td4669204i20.html#a4669709
As I wrote the above I decided that I do not make odepkg-0.8.5.
Therefore please close this post.
|
Wed 08 Apr 2015 10:51:05 AM UTC, comment #2:
John
I have re-made the changeset according to your advise.
For src/Makefile, your changeset is used.
Thanks!
(file #33592)
|
Wed 08 Apr 2015 10:33:33 AM UTC, comment #1:
You shouldnt need to rename configure.base as autogen.sh will use configure.base to generate the configure.in and finally generate configure.
|
Wed 08 Apr 2015 10:15:32 AM UTC, original submission:
I have tried to update odepkg-0.8.5 to be built on octave ver. 4.
http://octave.1599824.n4.nabble.com/Who-did-revise-codes-of-the-odepkg-package-to-work-on-octave-4-0-td4669683.html
I do not understand real means of "Clean up".
I did bump the Version number and Release date in the package DESCRIPTION file, update the NEWS and INDEX file, and the version in configure.ac file.
There is not src/confure.ac in odepkg-0.8.4 and I have renamed src/confure.base to src/confure.ac and modified. But "hg export tip" seem to be failed for src/confure.base
diff -ur odepkg/src/configure.base odepkg-work/src/configure.ac
Any help is appreciated.
Tasuro
|