Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta-ticket: spkg-configure: Try to use as many system packages as possible #27330

Open
embray opened this issue Feb 20, 2019 · 162 comments
Open

Comments

@embray
Copy link
Contributor

embray commented Feb 20, 2019

#24919 implemented a mechanism for checking for checking for sagelib's direct and indirect dependencies at the time of running the main ./configure script. This was already done in an ad-hoc manner for a handful of packages (e.g. gcc, git, yasm, curl), but we wanted to be able to do the same for other packages, especially those that are common on Linux-like systems.

This has now been implemented for many other packages, or is in the process of being implemented. Those packages are listed below. However, there are many others yet to be done, and this ticket will attempt to list them in some rough order of priority.

For use of Python packages: See #29023 Meta-ticket: In a python 3 build, use system Python packages

Already done

The following packages already have spkg-configure.m4 checks that are working on most or all supported platforms:

In Progress

The following packages have in-progress tickets to provide configure-time detection on the system:

Have tickets

The following packages have tickets for their conversions, but don't have working prototypes (i.e. branches) yet:

No ticket yet

Use of system Python packages

This will be be handled by #29023. Please do not add Python packages here.

The following are exceptions (because it does not run in the same Python as sage):

Testing infrastructure

Meta infrastructure

Documentation

Unfortunately there is still not good documentation for how to implement these configure-time dependency checks.

Bug-fixing

A number of bugs/deficiencies has been uncovered in spkg-configure.m4 files and related configuration, and a number of tickets opened/closed

CC: @sagetrac-tmonteil @orlitzky @timokau @kiwifb @isuruf @mezzarobba @tobihan @tobiasdiez

Component: build: configure

Keywords: sd111

Issue created by migration from https://trac.sagemath.org/ticket/27330

@embray embray added this to the sage-8.7 milestone Feb 20, 2019
@embray
Copy link
Contributor Author

embray commented Feb 20, 2019

comment:1

Note: The list of packages in the description is not yet exhaustive; please add others that are missing as you see fit and/or reprioritize. This is just a rough sketch.

@embray
Copy link
Contributor Author

embray commented Feb 21, 2019

comment:2

#27271 is the ticket for ecm.

@embray

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase
Copy link
Member

dimpase commented Feb 27, 2019

comment:8

There is also #27373, which concerns packages that change build/run environment, e.g. mpir/gmp/mpfr, that should be resolved in some way.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@embray
Copy link
Contributor Author

embray commented Mar 25, 2019

comment:13

Removing most of the rest of my open tickets out of the 8.7 milestone, which should be closed.

@embray embray removed this from the sage-8.7 milestone Mar 25, 2019
@embray embray added the pending label Mar 25, 2019
@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@dimpase

This comment has been minimized.

@orlitzky

This comment has been minimized.

@dimpase

This comment has been minimized.

@embray

This comment has been minimized.

@dimpase

This comment has been minimized.

@prirai
Copy link
Contributor

prirai commented Feb 18, 2023

I'm building Sagemath on an updated Archlinux. I have done so last year when sage was hosted on trac but didn't really notice the issues or simply ignored them.

I installed the packages mentioned here - https://doc.sagemath.org/html/en/installation/source.html#arch-linux-package-installation

However after running ./configure, I get this -

the following SPKGs did not find equivalent system packages:
eclib fflas_ffpack gengetopt givaro linbox rpy2   _develop gp2c libsemigroups perl_cpan_polymake_prereq perl_mongodb _recommended

So, I tried to install them manually like so,

sudo pacman -S eclib fflas-ffpack gengetopt givaro linbox python-rpy2 libsemigroups perl-xml-writer perl-xml-libxml perl-xml-libxslt perl-file-slurp perl-json

The perl_cpan_polymake_prereq is satisifed using perl-xml-writer perl-xml-libxml perl-xml-libxslt perl-file-slurp perl-json from main repository and perl-svg from the AUR.

source 1 - void-linux/void-packages#19090 (comment)

There are AUR packages for these - gp2c, perl-svg.

There's no equivalent however for perl_mongodb.
After installing these and running ./configure, I again get a similar issue but now the requirements have decreased. However, it still shows some of the packages that have already been installed. This might be due to spkg not being able to identify these.

notice: the following SPKGs did not find equivalent system packages:                          
                                                                                              
        eclib fflas_ffpack givaro linbox rpy2   _develop perl_mongodb _recommended

@mkoeppe
Copy link
Contributor

mkoeppe commented Feb 18, 2023

This is normal. Just continue with building Sage.

@prirai
Copy link
Contributor

prirai commented Feb 18, 2023

This is normal. Just continue with building Sage.

Yeah! The build was successful. Faster than the previous time after using export MAKE="make -j16" and export V=0.

@mkoeppe mkoeppe modified the milestones: sage-10.0, sage-10.1 Apr 30, 2023
@sheerluck
Copy link
Contributor

@mkoeppe
Copy link
Contributor

mkoeppe commented Aug 2, 2023

@sheerluck Thanks for the pointer. I've opened #36023 to track this problem.

@mkoeppe mkoeppe removed this from the sage-10.1 milestone Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants