Fwd: interval 0.1.1 released

[Marius Schamschula]

Hi all,

I’m forwarding what I sent to the octave-maintainers list. From their responses it appears that octave-1.0.tcl is again doing some mischief in setting environment variables.

Begin forwarded message:

> From: Marius Schamschula <lists at schamschula.com>
> Subject: Re: interval 0.1.1 released
> Date: February 1, 2015 at 2:15:14 PM CST
> To: Carnë Draug <carandraug at octave.org>
> Cc: octave-maintainers <octave-maintainers at gnu.org>, help-octave at gnu.org
> 
> Hi all,
> 
> While building interval 0.1.1 under MacPorts I get the following error:
> 
> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval" && /opt/local/bin/octave -q -f --eval 'pkg build -verbose -nodeps /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/interval.tar.gz''
> DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval" && /opt/local/bin/octave -q -f --eval 'pkg build -verbose -nodeps /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/interval.tar.gz' 
> mkdir (/opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/oct-SH5Gl4)
> untar (/opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/interval.tar.gz, /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/oct-SH5Gl4)
> /opt/local/bin/mkoctfile-3.8.2 -o mpfr_function_d.oct -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -lmpfr -lgmp  mpfr_function_d.cc
> mkoctfile: unrecognized argument -archmake: *** [mpfr_function_d.oct] Error 1
> 
> pkg: error running `make' for the interval package.
> error: called from 'configure_make' in file /opt/local/share/octave/3.8.2/m/pkg/private/configure_make.m near line 82, column 9
> error: called from:
> error:   /opt/local/share/octave/3.8.2/m/pkg/private/install.m at line 199, column 5
> error:   /opt/local/share/octave/3.8.2/m/pkg/private/build.m at line 50, column 3
> error:   /opt/local/share/octave/3.8.2/m/pkg/pkg.m at line 516, column 7
> Command failed:  cd "/opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval" && /opt/local/bin/octave -q -f --eval 'pkg build -verbose -nodeps /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/interval /opt/local/var/macports/build/_Users_marius_Development_MacPorts_ports_math_octave-interval/octave-interval/work/.tmp/interval.tar.gz' 
> Exit code: 1
> 
> Where does the stray “make” come form? Any ideas?
> 
> Note: I had no issues building interval 0.1.0.
> 
> On Feb 1, 2015, at 1:28 PM, Carnë Draug <carandraug at octave.org> wrote:
> 
>> Hi everyone
>> 
>> a new release of the interval package [1] is out, version 0.1.1, by
>> Oliver Heimlich.
>> A summary of important user-visible changes is also available online [2].
>> 
>> The interval package provides data types and fundamental operations
>> for real valued interval arithmetic based on the common floating-point
>> format "binary64" a.k.a. double-precision.  It aims to be standard
>> compliant with the (upcoming) IEEE 1788 and therefore implements the
>> set-based interval arithmetic flavour.
>> 
>> Enjoy Octave responsibly,
>> Carnë
>> 
>> [1] http://octave.sourceforge.net/interval/
>> [2] http://octave.sourceforge.net/interval/NEWS.html
>> 
> 
> Marius
> --
> Marius Schamschula


You should not need to set any special flags as octave will use the same
used to build it.  Take a look at the man page of mkoctfile, and you will
see a list of all flags.  These are the same as the ones you get when you
use octave_config_info.

Carnë
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150201/03553035/attachment.html>