Per Michael Grant's comments in the octave bug report, this is a
non-compliant (illegal) C11++ construct in octave code (but happens to work
in gcc and MSVC). We can not ask Apple to fix it. Octave community needs
fix the illegal construct.
On Wed, Jun 10, 2015 at 4:10 PM, Alexander Hansen
On Jun 9, 2015, at 11:11 PM, Sunil Shah ssha...@gmail.com wrote:
On Tue, Jun 9, 2015 at 7:00 PM, Alexander Hansen alexanderk.han...@gmail.com
mailto:alexanderk.han...@gmail.com wrote:
On Jun 9, 2015, at 18:48, Sunil Shah ssha...@gmail.com
mailto:ssha...@gmail.com wrote:
I should
I suppose it does not help that Apple is moving over to Metal from OpenGL.
Do the offending modules have to do with OpenGL?
On Tue, Jun 9, 2015 at 7:00 PM, Alexander Hansen
alexanderk.han...@gmail.com wrote:
On Jun 9, 2015, at 18:48, Sunil Shah ssha...@gmail.com wrote:
I should have
On Jun 10, 2015, at 16:05, Sunil Shah ssha...@gmail.com wrote:
Is there a link to the clang syntax bug(s) in the Octave / fink forums?
Ben sent me this, and I’ll cc our mailing list
http://savannah.gnu.org/bugs/?41178 http://savannah.gnu.org/bugs/?41178
If Apple needs to address the
On Jun 10, 2015, at 9:35 PM, Sunil Shah ssha...@gmail.com wrote:
On Wed, Jun 10, 2015 at 4:10 PM, Alexander Hansen
alexanderk.han...@gmail.com mailto:alexanderk.han...@gmail.com wrote:
On Jun 10, 2015, at 16:05, Sunil Shah ssha...@gmail.com
mailto:ssha...@gmail.com wrote:
Is there a
On Jun 9, 2015, at 16:31, Ben Abbott bpabb...@mac.com wrote:
On Jun 9, 2015, at 7:06 PM, Alexander Hansen alexanderk.han...@gmail.com
wrote:
On Jun 9, 2015, at 16:02, Sunil Shah ssha...@gmail.com wrote:
Hi Alexander,
What is the plan to get octave 4.0. on fink?
Thanks,
Hi Alexander,
What is the plan to get octave 4.0. on fink?
Thanks,
Sunil
On Thu, Jun 4, 2015 at 5:54 PM, Alexander Hansen
alexanderk.han...@gmail.com wrote:
On Jun 4, 2015, at 16:28, Ben Abbott bpabb...@mac.com wrote:
On Jun 3, 2015, at 10:53 PM, Alexander Hansen
Is octave 3.8.2 is the last official version for fink on the latest mac
osx? Or, are you waiting for some other dependency to resolve the issue?
On Tue, Jun 9, 2015 at 4:06 PM, Alexander Hansen
alexanderk.han...@gmail.com wrote:
On Jun 9, 2015, at 16:02, Sunil Shah ssha...@gmail.com wrote:
On Jun 9, 2015, at 7:06 PM, Alexander Hansen alexanderk.han...@gmail.com
wrote:
On Jun 9, 2015, at 16:02, Sunil Shah ssha...@gmail.com wrote:
Hi Alexander,
What is the plan to get octave 4.0. on fink?
Thanks,
Sunil
The last thing I heard was that it wouldn’t build with
On Jun 9, 2015, at 18:48, Sunil Shah ssha...@gmail.com wrote:
I should have been careful in my statement about what worked for me.
I am trying to understand the problem you referred to about octave 4.0.0 not
building on clang++.
I have been quite impressed with the performance of
On Jun 9, 2015, at 17:44, Sunil Shah ssha...@gmail.com wrote:
Octave 3.8.2.6 did build with the -dev version on OSX 10.10.3 (latest
production release) on fink 0.38.5
There’s no -dev version. -dev means “contains stuff used for development, but
not needed at runtime”, like headers and
Octave 3.8.2.6 did build with the -dev version on OSX 10.10.3 (latest
production release) on fink 0.38.5
Most of my octave code runs faster on the octave 3.8.2.x build on iMacs
(late 2011, 4 core intel) than on Octave 4.0.0 on Ubuntu 36 core fastest
Amazon AWS EC2 instance (c4.8xlarge with SSD
I should have been careful in my statement about what worked for me.
I am trying to understand the problem you referred to about octave 4.0.0
not building on clang++.
I have been quite impressed with the performance of Octave code on Mac OSX
using fink. My tests used octave382-atlas-qtmac
On Jun 9, 2015, at 9:48 PM, Sunil Shah ssha...@gmail.com wrote:
Now, as you imply in your last email, if the default octave variant uses
clang already, what is the issue with octave 4.0.0 and clang++? Or is it a
new issue in octave 4.0.0 in moving from 3.8.2?
Yes. The problem is that the
On Jun 4, 2015, at 16:28, Ben Abbott bpabb...@mac.com wrote:
On Jun 3, 2015, at 10:53 PM, Alexander Hansen alexanderk.han...@gmail.com
wrote:
This isn't specific to fltk13-aqua. Updating any package with a PkgInfo
file fails on Yosemite.
While we work out a solution, the workaround
On Jun 3, 2015, at 10:53 PM, Alexander Hansen alexanderk.han...@gmail.com
wrote:
This isn't specific to fltk13-aqua. Updating any package with a PkgInfo file
fails on Yosemite.
While we work out a solution, the workaround would be to remove fltk13-aqua
and then install it, since the
This isn't specific to fltk13-aqua. Updating any package with a PkgInfo file
fails on Yosemite.
While we work out a solution, the workaround would be to remove fltk13-aqua and
then install it, since the issue only is triggered when upgrading.
I can't add it to the FAQ because my computer is
17 matches
Mail list logo