Upgrade octave port to 3.0.1

This ticket is a followup to #13686, and the proposed patch directly from 2.9.15 to 3.0.1 (skipping the now outdated 3.0.0 version).

Thanks for Portfile. Many scitech users are waiting for Octave on MacPorts. I can commit the Portfile after testing. * I will add your email address (alakazam@melix.net) in the list of maintainers. * I would like to retain ptex variant for Japanese users who have ptex (localized teTeX) in place of the original teTeX.

retain ptex variant for Japanese users who have ptex (localized teTeX) in place of the original teTeX

Oh, my bad, I agree that it would be a good idea to retain this variant. Do you want me to test it ?

Did you guys had problems with libmetis when building octave 3.0.1 ? I had to manually add -lmetis to liboctave flags.

I did not, but will look into it today. What was the output of port build octave ?

I slightly modified the suggested Portfile.

* ptex variant is left removed. It should use non port dependency since tex command can be installed by multiple ports (teTeX, TeX Live and pTeX). * port dependency to perl5.8 is used. If bin:perl:perl5.8 is set and perl5.8 is not installed perl command is looked for to find one in /usr/bin. Environmental variable PERL is set to ${prefix}/bin/perl. As a result, build fails. * Added alakazam@melix.net as a maintainer (if you like).

I forgot to mention this. I tested the modified Portfile on Intel and PowerPC Macs running Leopard. I also tested on an Intel Mac running Tiger. I don't have a PowerPC Mac running Tiger at home. I will wait for about half a day for any comments and then commit it.

Replying to alakazam@melix.net:

I did not, but will look into it today. What was the output of port build octave ?

I explained it in my message to -users list. Basically building liboctave failed on first run though leaving a liboctave.dylib file of 0 bytes. On second run libtool couldn't deal with this empty file and building of actual octave executable failed. Adding explicit -lmetis I could build -loctave, I tried to rebuild mets and SuiteSparse too but that didn't help. I didn't use Portfile in this ticket, I just updated release and checksums from 2.9.15, will try this one once it's submitted.

Added alakazam@melix.net as a maintainer (if you like).

Yes, that's fine for me.

I don't have a PowerPC Mac running Tiger at home

I will try compiling on one today, but that may take quite some time to complete (it probably doesn't have all the dependencies built yet, so it will take about 12h, I think).

I didn't use Portfile in this ticket, I just updated release and checksums from 2.9.15

There are many modifications (in particular regarding the configure script patches to make libmetis work). Please try this Portfile, which should work for 3.0.1. That the current trunk Portfile does not work for octave 3.0.1 does not surprise me.

I don't have a PowerPC Mac running Tiger at home

I will try compiling on one today, but that may take quite some time to complete (it probably doesn't have all the dependencies built yet, so it will take about 12h, I think).

Then, I will wait for you. I will commit the new Portfile tomorrow morning (around 0UTC, 18 May) or later.

I didn't use Portfile in this ticket, I just updated release and checksums from 2.9.15

There are many modifications (in particular regarding the configure script patches to make libmetis work). Please try this Portfile, which should work for 3.0.1.

This reply is not to me, is it?

Replying to takeshi@macports.org:

I didn't use Portfile in this ticket, I just updated release and checksums from 2.9.15

There are many modifications (in particular regarding the configure script patches to make libmetis work). Please try this Portfile, which should work for 3.0.1.

This reply is not to me, is it?

No, sorry, this is a reply to andrea.damore@macports.org, who has encountered difficulties compiling octave 3.0.1 using a modified 2.9.15 Portfile.

I have also tested parallel building :

use_parallel_build  yes

which worked fine for me on 10.5.2 Intel.

I committed the port with use_parallel_build yes. Thanks.