Re: [sage-devel] How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages
On Fri, Mar 8, 2019 at 2:00 PM Jeroen Demeyer wrote: > > On 2019-03-08 10:42, Jeroen Demeyer wrote: > > (*) For some reason, the analogous C header works > > regardless of MACOSX_DEPLOYMENT_TARGET. Unfortunately, this header is > > not compatible with C++, so I really need . > > I just realized that I tried this only with g++ on Linux. With clang++ > on OS X, does work. So this avoids needing to mess with > MACOSX_DEPLOYMENT_TARGET. > > I'll also try g++ on OS X (do we still support that actually?). no, I don't think it works since OSX 10.12 or even earlier---due to changes in Apple's header files you'd need the compiler to know about "blocks", at least for some spkgs. > > -- > 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.
Re: [sage-devel] How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages
On 2019-03-08 10:42, Jeroen Demeyer wrote: (*) For some reason, the analogous C header works regardless of MACOSX_DEPLOYMENT_TARGET. Unfortunately, this header is not compatible with C++, so I really need . I just realized that I tried this only with g++ on Linux. With clang++ on OS X, does work. So this avoids needing to mess with MACOSX_DEPLOYMENT_TARGET. I'll also try g++ on OS X (do we still support that actually?). -- 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.
Re: [sage-devel] How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages
Fri 2019-03-08 11:21:09 UTC+1, Dima Pasechnik: > > I gather openblas has moved to 10.8 from 10.6, see > https://github.com/xianyi/OpenBLAS/issues/1580 > > Realistically, 10.9 is OK too, I don't think it's actually possible to > build current Sage on anything older than 10.11 or so... Current Sage actually builds perfectly fine on older macOS, in particular macOS 10.10.5 "Yosemite". Of course, Apple no longer supports Yosemite, so it gets no security upgrades and is therefore quite vulnerable, so anyone using that or older is advised to upgrade... Which reminds me we should really update the wiki page where we list our supported platforms: https://wiki.sagemath.org/SupportedPlatforms There is a link to that page from the documentation; I no longer dare to include that link in the new version announcements sent to sage-announce. -- 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.
Re: [sage-devel] How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages
I gather openblas has moved to 10.8 from 10.6, see https://github.com/xianyi/OpenBLAS/issues/1580 Realistically, 10.9 is OK too, I don't think it's actually possible to build current Sage on anything older than 10.11 or so... On Fri, Mar 8, 2019 at 9:42 AM Jeroen Demeyer wrote: > > Hello, > > While working on cysignals, I encounted an issue with > $MACOSX_DEPLOYMENT_TARGET. I have a fix, but I don't know if it's good. > It's not specific to Sage, but it will affect Sage since cysignals is a > Sage package. > > For cysignals, I'd really like to use MACOSX_DEPLOYMENT_TARGET >= 10.9 > since that enables the C++ header (*) which is needed to fix > Sage ticket #24288. The tricky part is that not only cysignals itself > should be compiled with MACOSX_DEPLOYMENT_TARGET >= 10.9 but also every > package using cysignals. > > I have a solution which adds the command-line flag > -mmacosx-version-min=10.9 when compiling cysignals: > https://github.com/sagemath/cysignals/commit/17062a64bf5672375982cf295ed93b346b55d680 > Thanks to Cython magic, this flag will be passed on to every package > that cimports cysignals. > > This solution seems to work and passes CI tests. These tests are done > using Conda, which uses a Python compiled with > MACOSX_DEPLOYMENT_TARGET=10.6, which is then used for every Python > package (analogous to CFLAGS, distutils uses the value for > MACOSX_DEPLOYMENT_TARGET which was used to compile Python). > > So my question is basically: what could possibly go wrong? One thing > which worries me is that the command-line flag -mmacosx-version-min=10.9 > overrides the environment variable MACOSX_DEPLOYMENT_TARGET. So if > somebody really wanted a higher value for MACOSX_DEPLOYMENT_TARGET than > 10.9, it wouldn't work. But I see no solution for this. > > > Jeroen. > > > (*) For some reason, the analogous C header works > regardless of MACOSX_DEPLOYMENT_TARGET. Unfortunately, this header is > not compatible with C++, so I really need . > > -- > 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.
[sage-devel] How to deal with MACOSX_DEPLOYMENT_TARGET in Python packages
Hello, While working on cysignals, I encounted an issue with $MACOSX_DEPLOYMENT_TARGET. I have a fix, but I don't know if it's good. It's not specific to Sage, but it will affect Sage since cysignals is a Sage package. For cysignals, I'd really like to use MACOSX_DEPLOYMENT_TARGET >= 10.9 since that enables the C++ header (*) which is needed to fix Sage ticket #24288. The tricky part is that not only cysignals itself should be compiled with MACOSX_DEPLOYMENT_TARGET >= 10.9 but also every package using cysignals. I have a solution which adds the command-line flag -mmacosx-version-min=10.9 when compiling cysignals: https://github.com/sagemath/cysignals/commit/17062a64bf5672375982cf295ed93b346b55d680 Thanks to Cython magic, this flag will be passed on to every package that cimports cysignals. This solution seems to work and passes CI tests. These tests are done using Conda, which uses a Python compiled with MACOSX_DEPLOYMENT_TARGET=10.6, which is then used for every Python package (analogous to CFLAGS, distutils uses the value for MACOSX_DEPLOYMENT_TARGET which was used to compile Python). So my question is basically: what could possibly go wrong? One thing which worries me is that the command-line flag -mmacosx-version-min=10.9 overrides the environment variable MACOSX_DEPLOYMENT_TARGET. So if somebody really wanted a higher value for MACOSX_DEPLOYMENT_TARGET than 10.9, it wouldn't work. But I see no solution for this. Jeroen. (*) For some reason, the analogous C header works regardless of MACOSX_DEPLOYMENT_TARGET. Unfortunately, this header is not compatible with C++, so I really need . -- 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.
