tomorrow is fine .
I am testing octave-4.0.0-rc3 today
;-)
On 4/18/2015 9:13 PM, Ralph Castain wrote:
I am planning on rc2 on Monday, if you’d prefer to wait
On Apr 18, 2015, at 9:30 AM, Marco Atzeri wrote:
Are you planning another rc or I should test the git stable repository ?
I am planning on rc2 on Monday, if you’d prefer to wait
> On Apr 18, 2015, at 9:30 AM, Marco Atzeri wrote:
>
> Are you planning another rc or I should test the git stable repository ?
>
>
> On 4/18/2015 5:10 PM, Ralph Castain wrote:
>> Should now be solved - it was a libtool compatibility iss
Are you planning another rc or I should test the git stable repository ?
On 4/18/2015 5:10 PM, Ralph Castain wrote:
Should now be solved - it was a libtool compatibility issue, and I
updated the 1.8 libtool code
On Apr 18, 2015, at 7:57 AM, Marco Atzeri mailto:marco.atz...@gmail.com>> wrote:
Should now be solved - it was a libtool compatibility issue, and I updated the
1.8 libtool code
> On Apr 18, 2015, at 7:57 AM, Marco Atzeri wrote:
>
> On 4/18/2015 1:01 PM, Jeff Squyres (jsquyres) wrote:
>> Marco --
>>
>> I'm super-late to this -- did this issue get resolved?
>>
>
> Not that
On 4/18/2015 1:01 PM, Jeff Squyres (jsquyres) wrote:
Marco --
I'm super-late to this -- did this issue get resolved?
Not that I am aware of.
I was busy on other things and I did not work further on the matter.
Suggestion for solving it ?
On Apr 7, 2015, at 5:12 PM, Marco Atzeri wrote:
On
Howard --
Does Nathan's recent infrastructure activity in Opal destructors help with this?
> On Apr 6, 2015, at 7:08 PM, Ralph Castain wrote:
>
> I think either solution would be valuable - this is something that came up a
> few months ago, but the Java team members couldn’t trace it down, an
Marco --
I'm super-late to this -- did this issue get resolved?
> On Apr 7, 2015, at 5:12 PM, Marco Atzeri wrote:
>
> On 4/7/2015 10:00 PM, Ralph Castain wrote:
>> What version of libtool do you have? We require 2.4.2 - newer versions don’t
>> necessarily work, I fear.
>>
>
> 2.4.6
>
> for
On Apr 6, 2015, at 3:07 PM, Ralph Castain wrote:
>
>> - Don't use inline functions with Clang compiler
>>
>> Without motivation/explanation that sounds like a bad thing.
>
> Some versions of clang (at least >= 3.5 -- perhaps older versions, too?) will
> warn about -finline-functions, but still
