It's fixed for OSX now, it's the packaging (and the necessary for OSX, as 
it turns out, update to Boehm GC package).
https://github.com/dimpase/libhomfly


On Thursday, October 12, 2017 at 10:29:46 AM UTC+1, Dima Pasechnik wrote:
>
> Now it's down to doing something with fmemopen call there, that is not 
> portable to OSX (there is no fmemopen on OSX!)
>
> How did this package get into Sage, it surely never ever worked on OSX...
>
> On Wednesday, October 11, 2017 at 11:27:07 PM UTC+1, Dima Pasechnik wrote:
>>
>> I can reproduce this linking error on OSX; I've opened #24015 
>> <https://trac.sagemath.org/ticket/24015> to track this error.
>>
>>
>> On Wednesday, October 11, 2017 at 10:31:16 AM UTC+1, Erik Bray wrote:
>>>
>>> On Tue, Oct 10, 2017 at 7:51 PM, Jesse H <jhame...@gmail.com> wrote: 
>>> > Greetings, 
>>> > 
>>> > I have been trying to use the function "homfly_polynomial()" from the 
>>> Link 
>>> > package in Sage, but it requires an optional package "libhomfly": 
>>> > http://files.sagemath.org/spkg/upstream/libhomfly/index.html. 
>>> > 
>>> > Unfortunately, when I try to install libhomfly ("sage -i libhomfly") 
>>> the 
>>> > build always fails (see attached log file). 
>>> > 
>>> > One of the dependencies for libhomfly is Boehm GC, but when I try to 
>>> install 
>>> > this package ("sage -i boehm_gc"), it is not even found on Sage's list 
>>> of 
>>> > optional packages (even though it's displayed on the 
>>> > website:
>>> http://mirrors-usa.go-parts.com/sage/sagemath/spkg/upstream/boehm_gc/index.html).
>>>  
>>>
>>> > I'm not sure if this is indeed the issue, but it's just something I 
>>> came 
>>> > across. 
>>> > 
>>> > For what it's worth, I'm running SageMath 8.0 and MacOS 10.12.6 on a 
>>> mid 
>>> > 2012 MacBook Pro with a 2.3 GHz i7 processor and 8GB RAM. 
>>> > 
>>> > Any help is much appreciated. 
>>>
>>> This looks like a bug in libhomfly.  Just looking at the sources it 
>>> has some messy handling of extern variable declarations vs. 
>>> definitions, and many global variables are actually being defined in 
>>> multiple modules.  I haven't run into this problem myself building 
>>> libhomfly but maybe my compiler is more forgiving.  Regardless it 
>>> definitely looks wrong to me.  I could see if I can reproduce on OSX 
>>> now that I have shiny new access to a big OSX machine :) 
>>>
>>> Erik 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to