octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: odepkg on Mac (was: Octave 4.2.0 release candidate 1 available for f


From: c.
Subject: Re: odepkg on Mac (was: Octave 4.2.0 release candidate 1 available for ftp)
Date: Fri, 9 Sep 2016 20:06:22 +0200

On 9 Sep 2016, at 19:35, Mike Miller <address@hidden> wrote:

> On Fri, Sep 09, 2016 at 19:07:35 +0200, c. wrote:
>> 
>> On 9 Sep 2016, at 18:25, Nir Krakauer <address@hidden> wrote:
>> 
>>> pkg install -forge odepkg also works for me with Homebrew's Octave 
>>> (4.0.3-3). gcc and c++ are Apple LLVM version 7.3.0 (clang-703.0.31) and 
>>> gfortran is GNU Fortran (Homebrew gcc 6.2.0) 6.2.0
>> 
>> Can someone please try the same with Octave 4.1 or 4.2rc1 ?
>> The issue Sebastian refers to never occurred on 4.0
> 
> With the released package version 0.8.5 or the latest sources from hg?
> 
> Do you expect that the issue is macOS- and/or clang-specific? Has anyone
> other than Sebastian had this problem?
> 
> In bug #48380, there is a comment saying that the odepkg hg sources work
> fine against Octave default [1]. But of course this is with gcc.
> 
> There is a patch in mxe-octave for odepkg [2], presumably containing
> things that have been fixed in hg but not yet released.
> 
> [1]: https://savannah.gnu.org/bugs/?48380#comment10
> [2]: http://hg.octave.org/mxe-octave/file/tip/src/of-odepkg-1-fixes.patch

Mike,

There are different issues with compiling fortran routines included in odepkg
that surfaced with recent changes to the configure and build system in core 
octave,
some where already fixed in the odepkg repository in preparation for Octave 4.2

The particular one that Sebastian refers to can be tracked down to the fact that
none of the macros F77_USES_*_CALLING_CONVENTION is defined in octave-config.log

This issue is similar to what was discussed here: 
https://savannah.gnu.org/bugs/?48559
and apparently fixed with this changeset by jwe: 
http://hg.savannah.gnu.org/hgweb/octave/rev/1bd872efdab5

Indeed on my own laptop (OSX 10.9.5, macports, gcc-4.8) after configure I get:
$ grep -i f77_uses octave-config.h 
/* #  undef F77_USES_CRAY_CALLING_CONVENTION */
/* #  undef F77_USES_F2C_CALLING_CONVENTION */
#  define F77_USES_GFORTRAN_CALLING_CONVENTION 1
/* #  undef F77_USES_VISUAL_FORTRAN_CALLING_CONVENTION */
 $ grep -i f77_uses config.h 
/* #undef F77_USES_CRAY_CALLING_CONVENTION */
/* #undef F77_USES_F2C_CALLING_CONVENTION */
#define F77_USES_GFORTRAN_CALLING_CONVENTION 1
/* #undef F77_USES_VISUAL_FORTRAN_CALLING_CONVENTION */

therefore I never managed to reproduce the issue here.

on the mac-mini at EPFL thoug (OSX 10.11, homebrew, glang) I get:

bash-3.2$ grep -i f77_uses octave-config.h 
bash-3.2$ grep -i f77_uses config.h 
/* #undef F77_USES_CRAY_CALLING_CONVENTION */
/* #undef F77_USES_F2C_CALLING_CONVENTION */
#define F77_USES_GFORTRAN_CALLING_CONVENTION 1
/* #undef F77_USES_VISUAL_FORTRAN_CALLING_CONVENTION */
bash-3.2$ 

so, for some reason the move of those definitions is not working there ...

c.









reply via email to

[Prev in Thread] Current Thread [Next in Thread]