[sage-devel] Help needed with adding user packages as optional/experimental packages

2021-01-13 Thread Matthias Koeppe


Meta-ticket https://trac.sagemath.org/ticket/31164 proposes to add user 
packages, such as those listed at  
https://wiki.sagemath.org/SageMathExternalPackages, to the Sage 
distribution as "pip" packages. This has the following benefits:

   - They will be automatically included in our reference manual and Sage 
   website (https://trac.sagemath.org/ticket/29655).
   - We have GitHub Actions workflows in place 
   (tox-optional.yml, tox-experimental.yml), which will automatically try to 
   build the packages on each beta release. This provides continuous 
   integration that will allow us to catch unintended breaking changes during 
   the Sage development cycle.

Help is needed with this task. 
- If a package listed at https://wiki.sagemath.org/SageMathExternalPackages is 
outdated (does not work with a current version of Sage), it will be helpful 
to add a note to the wiki page and to notify the package authors.
- If a package seems to work with current Sage, help by creating a ticket 
for the inclusion in Sage and list the ticket in meta-ticket 
https://trac.sagemath.org/ticket/31164
- If a significant package is neither listed in build/pkgs/ nor in the wiki 
page, please add it. 





-- 
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/3c9e4024-2175-47b2-8d5a-5c2173366d90n%40googlegroups.com.


[sage-devel] Purpose of SAGE_MACOSX_DEPLOYMENT_TARGET

2021-01-13 Thread Zachary Scherr
I've been trying to help out with getting sage to work properly on Mac, and 
I was curious if anyone can explain the purpose of 
SAGE_MACOSX_DEPLOYMENT_TARGET to me.

I don't know autoconf at all, but I find that if I configure with 
--with-system-python3=no
then SAGE_MACOSX_DEPLOYMENT_TARGET gets set to "legacy".  This is 
presumably because of the lines

AS_IF([test x$sage_spkg_install_python3 = xno],
  [PYTHON_FOR_VENV="$ac_cv_path_PYTHON3"],
  [SAGE_MACOSX_DEPLOYMENT_TARGET=legacy])
AC_SUBST([PYTHON_FOR_VENV])
AC_SUBST([SAGE_MACOSX_DEPLOYMENT_TARGET])

located in build/pkgs/python3/spkg-configure.m4.

As far as I can tell, this leads to all sorts of warnings when doctesting 
sage.  Specifically, I get lots of warnings like:

ld: warning: dylib (/usr/local/lib/libmpfr.dylib) was built for newer 
macOS version (10.15) than being linked (10.9)
ld: warning: dylib (/usr/local/lib/libgmp.dylib) was built for newer 
macOS version (10.15) than being linked (10.9)
ld: warning: dylib (/usr/local/lib/libgmpxx.dylib) was built for newer 
macOS version (10.15) than being linked (10.9)
ld: warning: dylib (/usr/local/lib/libgsl.dylib) was built for newer 
macOS version (10.15) than being linked (10.9)
ld: warning: dylib (/usr/local/lib/libntl.dylib) was built for newer 
macOS version (10.15) than being linked (10.9)

now I believe that this is caused by src/bin/sage-env which has the 
following code:

if [ "$UNAME" = "Darwin" ]; then
  export MACOSX_VERSION=`uname -r | awk -F. '{print $1}'`
  case "$SAGE_MACOSX_DEPLOYMENT_TARGET" in
  legacy)
# legacy behavior of the Sage distribution.
# set MACOSX_DEPLOYMENT_TARGET -- if set incorrectly, this can
# cause lots of random "Abort trap" issues on OSX. see trac
# #7095 for an example.
if [ $MACOSX_VERSION -ge 14 ]; then
# various packages have still have issues with
# two digit OS X versions
MACOSX_DEPLOYMENT_TARGET=10.9
else
MACOSX_DEPLOYMENT_TARGET=10.$[$MACOSX_VERSION-4]
fi
export MACOSX_DEPLOYMENT_TARGET
;;
  "")
# Do nothing
;;
  *)
# A fixed version set at configure time.
export MACOSX_DEPLOYMENT_TARGET=$SAGE_MACOSX_DEPLOYMENT_TARGET
;;
  esac

and I'm trying to understand where all of this is coming from.  The trac 
ticket this references is 11 years old and so I'm not sure it's an issue 
any more.

-- 
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/19afd68d-be22-4a98-a3e7-c694fc6135a8n%40googlegroups.com.