I should probably also add that while sage builds with 
the spkg-configure.m4 fix, my documentation will not build unless I brew 
unlink singular.

On Wednesday, October 7, 2020 at 10:33:32 AM UTC-4 Zachary Scherr wrote:

> I was just curious as to what the status of this issue is, and if there 
> was anything I could do to help with review.  I can build rc0 using Dima's 
> suggested spkg-configure.m4 fix, but I can't build it otherwise unless I 
> brew unlink singular first. 
>
> On Friday, September 11, 2020 at 6:47:23 PM UTC-4 dim...@gmail.com wrote:
>
>> as an experiment, I hardcoded the necessary paths for using Homebrew's 
>> Singular here:
>>
>> https://trac.sagemath.org/attachment/ticket/29024/homebrew-singular-experiment.patch
>> (the part for  src/sage/libs/singular/singular.pxd is probably not 
>> needed, but anyway)
>>
>> running tests now.
>>
>> On Fri, Sep 11, 2020 at 6:15 PM Dima Pasechnik <dim...@gmail.com> wrote:
>>
>>>
>>>
>>> On Fri, Sep 11, 2020 at 3:32 PM Dima Pasechnik <dim...@gmail.com> wrote:
>>>
>>>> I think there is at least one place elsewhere in the code that assumes 
>>>> that Singular is installed in $SAGE_LOCAL
>>>>
>>>> at least I got an error of this sort while trying to build Sage's docs 
>>>> in this configuration.
>>>> I'll look into it once back at the keyboard
>>>>
>>>
>>> this problem is explained in 
>>> https://trac.sagemath.org/ticket/29024#comment:8
>>>
>>> The fix needs some programming - specifically, the code in singular.pyx 
>>> calls dlopen on SINGULAR_SO,
>>> which is computed by _get_shared_lib_filename dynamically in env.py, 
>>> and assuming that it is in SAGE_LOCAL.
>>> So this probably can instead by handled using cython_aliases from the 
>>> same module (which does compute
>>> all the needed info for Singular, it seems).
>>> Or by fixing _get_shared_lib_filename so that it also searches 
>>> elsewhere.
>>>
>>>
>>>> On Fri, 11 Sep 2020, 15:10 Zachary Scherr, <zsc...@gmail.com> wrote:
>>>>
>>>>> Hi Dima,
>>>>>
>>>>>    Thanks! Downloading spkg-configure.m4 allowed me to build 
>>>>> successfully.
>>>>>
>>>>> Best,
>>>>> Zach
>>>>>
>>>>> On Friday, September 11, 2020 at 5:45:00 AM UTC-4 dim...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> On Fri, Sep 11, 2020 at 10:11 AM Dima Pasechnik <dim...@gmail.com> 
>>>>>> wrote:
>>>>>>
>>>>>>> [sagelib-9.2.beta12] installing. Log file: 
>>>>>>> /Users/zscherr/sage/develop/logs/pkgs/sagelib-9.2.beta12.log
>>>>>>>   [sagelib-9.2.beta12] error installing, exit status 1. End of log 
>>>>>>> file:
>>>>>>>   [sagelib-9.2.beta12]   
>>>>>>> /usr/local/include/singular/Singular/libsingular.h:15:10: fatal error: 
>>>>>>> 'polys/shiftop.h' file not found
>>>>>>>   [sagelib-9.2.beta12]   #include "polys/shiftop.h"
>>>>>>>   [sagelib-9.2.beta12]            ^~~~~~~~~~~~~~~~~
>>>>>>>
>>>>>>> the include path looks funny with its "singular/Singular/"
>>>>>>> I don't know what brew does here, maybe it drops "singular/" bit?
>>>>>>>
>>>>>>
>>>>>> no, in fact it's all fine, it's just include flags that need to be 
>>>>>> adjusted.
>>>>>> Note that you still have 
>>>>>> -I/Users/zscherr/sage/develop/local/include/singular
>>>>>> in the failing gcc call, which seems to indicate you didn't use
>>>>>>
>>>>>> https://trac.sagemath.org/attachment/ticket/29024/spkg-configure.m4
>>>>>>
>>>>>> - of if you did, you didn't run
>>>>>>
>>>>>> make singular-clean
>>>>>>
>>>>>> ./bootstrap && ./configure
>>>>>>
>>>>>> after putting that file
>>>>>> in build/pkgs/singular/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Try
>>>>>>
>>>>>> CXXFLAGS="$CXXFLAGS -I//usr/local/include/singular/
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 10, 2020 at 9:20 PM Zachary Scherr <zsc...@gmail.com> 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Matthias,
>>>>>>>>
>>>>>>>>    It's attached to this message.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Zach
>>>>>>>>
>>>>>>>> On Thursday, September 10, 2020 at 1:07:27 PM UTC-4 Matthias Koeppe 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On Thursday, September 10, 2020 at 9:58:02 AM UTC-7, Zachary 
>>>>>>>>> Scherr wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Obviously this is not a big deal since I can just brew uninstall 
>>>>>>>>>> singular and then it builds successfully, but I've been wanting to 
>>>>>>>>>> contribute to sage development so I'm going to take this as an 
>>>>>>>>>> opportunity 
>>>>>>>>>> to try to track down what's going on. 
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes, this is much appreciated. So far I can't reproduce the error 
>>>>>>>>> here (after installing homebrew's singular), unfortunately. 
>>>>>>>>>
>>>>>>>>> Could you post install.log please?
>>>>>>>>>
>>>>>>>> -- 
>>>>>>>> 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+...@googlegroups.com.
>>>>>>>> To view this discussion on the web visit 
>>>>>>>> https://groups.google.com/d/msgid/sage-devel/3c9f01e9-ded6-43bd-8861-301d1e97a06an%40googlegroups.com
>>>>>>>>  
>>>>>>>> <https://groups.google.com/d/msgid/sage-devel/3c9f01e9-ded6-43bd-8861-301d1e97a06an%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>>
>>>>>>> -- 
>>>>> 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+...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/sage-devel/8ecc5952-4895-4568-a50b-0e51e3cbf183n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/sage-devel/8ecc5952-4895-4568-a50b-0e51e3cbf183n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/247786c8-23a7-45f7-8a90-b662b4df90dbn%40googlegroups.com.

Reply via email to