Already done: https://trac.sagemath.org/ticket/24860

On Feb 27, 2018 22:10, "ערן אסף" <assafe...@gmail.com> wrote:

> Great. Glad that I could be of assistance.
> Should I open a ticket for this bug somewhere?
>
> 2018-02-27 19:11 GMT+02:00 Erik Bray <erik.m.b...@gmail.com>:
>
>> On Tue, Feb 27, 2018 at 5:44 PM, Erik Bray <erik.m.b...@gmail.com> wrote:
>> > On Tue, Feb 13, 2018 at 8:46 AM, ערן אסף <assafe...@gmail.com> wrote:
>> >> Ok, I figured it out after some debugging.
>> >> It turns out that /usr/include/limits.h defines LINE_MAX only if
>> >> __POSIX_VISIBLE is at least 2.
>> >> In cygwin, when one compiles using the flag -std=c++XX (here XX is any
>> >> number, in our case 11), __POSIX_VISIBLE is set to 0.
>> >> This is solved throughout most of the sage installation by using
>> >> -std=gnu++11 (e.g. see setup.py).
>> >> However, in the brial library, the makefile explicitly adds -std=c++11,
>> >> which causes this error.
>> >>
>> >> Thank you very much for your assistance,
>> >
>> > Thanks for the update on that.  As you noted, this problem has come up
>> > before and most modules are compiled on Cygwin using -std=gnu++XX
>> > where applicable.  But clearly Brial is not.  It's strange though
>> > because I should be able to reproduce the problem, but I can't.  Maybe
>> > I'm using a newer Cygwin (or an older one?) that doesn't happen to run
>> > into this specific problem.  Nevertheless this should probably be
>> > fixed...
>>
>> From the look of things this feature test was added to the limits.h
>> header relatively recently (November 2017) so indeed, I don't even
>> have that update yet on my Cygwin install.  Since this is the case in
>> newer versions we should definitely fix it.
>>
>> >> 2018-02-12 13:15 GMT+02:00 Erik Bray <erik.m.b...@gmail.com>:
>> >>>
>> >>> On Thu, Feb 8, 2018 at 1:55 PM, ערן אסף <assafe...@gmail.com> wrote:
>> >>> > Hi,
>> >>> > I have looked in https://trac.sagemath.org/wiki/Cygwin64Port and
>> also
>> >>> > installed libcrypt-devel, and now have a problem with another
>> library.
>> >>> > This happens on both the develop branch and on your develop-cygwin
>> >>> > branch.
>> >>> > The error seems to be:
>> >>> > BoolePolyRing.cc:129:18: error: 'LINE_MAX' was not declared in this
>> >>> > scope
>> >>> >                                                     char
>> >>> > str_buf[LINE_MAX];
>> >>>
>> >>> I'm not sure...   LINE_MAX is defined in limits.h, which you should
>> >>> have (/usr/include/limits.h).
>> >>>
>> >>>
>> >>> > בתאריך יום רביעי, 7 בפברואר 2018 בשעה 20:37:24 UTC+2, מאת Erik Bray:
>> >>> >>
>> >>> >> On Tue, Feb 6, 2018 at 3:50 PM, ערן אסף <assa...@gmail.com> wrote:
>> >>> >> > Hi,
>> >>> >> > I have a 64-bit windows 10 Pro operating system running on a
>> single
>> >>> >> > (Intel)
>> >>> >> > processor PC.
>> >>> >> > In order to develop for sage on it, I have installed cygwin with
>> all
>> >>> >> > required packages -
>> >>> >> > gcc, make, m4, perl, binutils, python, git,
>> perl-ExtUtils-MakeMaker,
>> >>> >> > openssl, openssl-devel, texlive, tk, tk-dev, openssh, lapack,
>> >>> >> > lapack-devel
>> >>> >> >
>> >>> >> > Then I cloned the source code, checked out, and ran the make
>> command.
>> >>> >> > When building python, I got the following error message:
>> >>> >> > Python build finished, but the necessary bits to build these
>> modules
>> >>> >> > were
>> >>> >> > not found:
>> >>> >> > _bsddb                               _curses
>> >>> >> > _curses_panel
>> >>> >> > _tkinter                              bsddb185
>> >>> >> > dl
>> >>> >> > imageop                            linuxaudiodev
>> >>> >> > nis
>> >>> >> > ossaudiodev                      spwd
>> >>> >> > sunaudiodev
>> >>> >> >  To find the necessary bits, look in setup.py in
>> detect_modules() for
>> >>> >> > the
>> >>> >> > module's name.
>> >>> >> >  Failed to build these modules:
>> >>> >> > crypt
>> >>> >>
>> >>> >> You need libcrypt-devel.   See
>> >>> >> https://trac.sagemath.org/wiki/Cygwin64Port
>> >>> >>
>> >>> >> Let me know if you run into any other problems.
>> >>> >>
>> >>> >> Best,
>> >>> >> E
>> >>> >
>> >>> > --
>> >>> > 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.
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to a topic in the
>> >>> Google Groups "sage-devel" group.
>> >>> To unsubscribe from this topic, visit
>> >>> https://groups.google.com/d/topic/sage-devel/iMN3N7pqrq8/unsubscribe.
>> >>> To unsubscribe from this group and all its topics, 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.
>> >>
>> >>
>> >> --
>> >> 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.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/sage-devel/iMN3N7pqrq8/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.
>>
>
> --
> 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.
>

-- 
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