octave-general @1.3.2 fails to build

[roberthuston@…]

I did a self update and discovered that my octave-signal port needed to be upgraded to 1.2.0_0. As part of the upgrade, macports pulled down octave-general @1.3.2. But the build failed, thus preventing me from upgrading my octave-signal port. It appears that the portfile's build script fails to create intermediate directories and thus cannot populate them with intermediate results. I have attached the output of the main.log that was dumped as part of the build.

[roberthuston@…]

Build main.log output

[razzfazz (Daniel Becker)]

Seeing the same problem. This is on Mountain Lion.

[razzfazz (Daniel Becker)]

Cc Me!

[AP1010]

Cc Me!

[ruben+macports@…]

Cc Me!

[mv@…]

Cc Me!

[larryv (Lawrence Velázquez)]

Replying to mv@…:

Cc Me!

You need to actually click the “CcMe!” button next to the Cc list to be Cc’d. I’ve added you to the list.

[hnarayanan (Harish Narayanan)]

Cc Me!

[AP1010]

This could be a bug in octave (the main package) not octave-general. I have seen similar errors when trying to install other packages (e.g. octave-strings). On the other hand, when I replaced octave-3.2.4 with octave-devel-3.6.4, I could then install octave-general (and octave-strings) without any errors.

[roberthuston@…]

Replying to arthur@…:

This could be a bug in octave (the main package) not octave-general. I have seen similar errors when trying to install other packages (e.g. octave-strings). On the other hand, when I replaced octave-3.2.4 with octave-devel-3.6.4, I could then install octave-general (and octave-strings) without any errors.

I believe you are right. I was able to install octave-devel-3.6.4 and then octave-general happily installed. (My goal was to install octave-control and octave-signal, which pulls in octave-general and others.) At this point, octave-devel-3.6.4 is probably better anyway, since GNU Octave has version 3.6.4 marked as the actual release version. I've also since found that octave-devel-3.6.4 operates considerably faster and more efficiently than the standard octave-3.2.4. I don't understand why MacPorts keeps it at the "devel" state since GNU considers it "released."

[mv@…]

Cc Me!

[mv@…]

Cc Me!

[michaelld (Michael Dickens)]

Please do:

sudo port clean octave-general
sudo port selfupdate

and then try installing it again. Should be fixed with r114034.

[AP1010]

Replying to michaelld@…:

Please do:

sudo port clean octave-general
sudo port selfupdate

and then try installing it again. Should be fixed with r114034.

I am afraid it still fails to install:

---> Verifying checksums for octave-general ---> Checksumming general-1.3.2.tar.gz ---> Extracting octave-general ---> Extracting general-1.3.2.tar.gz ---> Configuring octave-general sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave-general/octave-general/work/general: No such file or directory

[roberthuston@…]

Replying to arthur@…:

Replying to michaelld@…:

Please do:

sudo port clean octave-general
sudo port selfupdate

and then try installing it again. Should be fixed with r114034.

I am afraid it still fails to install:

---> Verifying checksums for octave-general ---> Checksumming general-1.3.2.tar.gz ---> Extracting octave-general ---> Extracting general-1.3.2.tar.gz ---> Configuring octave-general sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave-general/octave-general/work/general: No such file or directory

It appears that the octave-devel port has recently been deprecated and the regular octave port is now the most recent version (@3.6.4_10 as of this writing).

I've discovered that this behavior occurs with all packages, not just octave-general. Basically, it can be fixed manually by attempting to install the package, manually creating the "package" directory (e.g., "general") after the configuration step fails, and then resuming the installation.

$ sudo port install octave
=> now "octave" port installs what used to be the "octave-devel" port (version 3.6.4_x)

$ sudo port install octave-general
=> fails due to inability to "cd" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave-general/octave-general/work/general" because the "general" subdirectory does not get created

$ cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_octave-general/octave-general/work
$ ls
=> verify that directory contains no "general" subdirectory
$ sudo mkdir general
$ sudo chown macports general
=> installer user account is "macports"
$ cd ../../..
=> need to do this last step because the build working directory gets deleted after installation
$ sudo port install octave-general
=> should successfully complete installation

I suspect there's something wrong with the octave package installer script in how it parses the package name in creating the build tree.

[ralph@…]

I am getting the same issue when trying to upgrade from 1.3.2 to 1.3.4. It seems that this issue is NOT fixed.

[ralph@…]

Hmm perhpas my issue is slightly different - it is some other files which are not there. I'll submit a new bug report.