-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Extend system package scripts to handle macports; tox.ini: Add macports environment #31505
Comments
Author: Matthias Koeppe |
Commit: |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Dependencies: #30504 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:13
No need for a |
This comment has been minimized.
This comment has been minimized.
comment:15
I don't think we need this - only 1 command is needed to prepare the build |
comment:16
The Could they run |
comment:17
Oh in fact they already do. Sorry for the noise. I'm trying this out and will report. |
comment:18
Yes, |
comment:19
For more quiet, you can use |
comment:163
The actual g++ error message is missing in what you pasted here |
comment:164
right - I thought it's some kind of Python packaging error :-)
macports comes with flint 2.9.0, so it seems there is some kind of incompatibility with our 2.8.4. |
comment:165
The problem is that |
comment:166
Replying to @mkoeppe:
that's probably what |
comment:167
No, this is the install location of macports within the tox environment. I set these variables:
but not |
comment:168
Then it's done by macports, not by tox. |
comment:169
Could you check what the macports-installed |
comment:170
there are 2 installations of python3.10 in .tox/local-macports-standard/:
The latter is the only |
Attachment: p1.gz sysconfig1 |
Attachment: p2.gz sysconf2 |
comment:171
attached are their outputs when run with (there is also python2.7.18 - hopefully we have stopped all python2's used in our build by now...) |
this is the branch from sagemath#31505, rebased over Sage 10.0 branch Resolves sagemath#31505 - Depends on sagemath#36910 (merged here) URL: sagemath#35667 Reported by: Dima Pasechnik Reviewer(s):
this is the branch from sagemath#31505, rebased over Sage 10.0 branch Resolves sagemath#31505 - Depends on sagemath#36910 (merged here) URL: sagemath#35667 Reported by: Dima Pasechnik Reviewer(s):
this is the branch from sagemath#31505, rebased over Sage 10.0 branch Resolves sagemath#31505 - Depends on sagemath#36910 (merged here) URL: sagemath#35667 Reported by: Dima Pasechnik Reviewer(s):
this is the branch from sagemath#31505, rebased over Sage 10.0 branch Resolves sagemath#31505 - Depends on sagemath#36910 (merged here) URL: sagemath#35667 Reported by: Dima Pasechnik Reviewer(s):
this is the branch from sagemath#31505, rebased over Sage 10.0 branch Resolves sagemath#31505 - Depends on sagemath#36910 (merged here) URL: sagemath#35667 Reported by: Dima Pasechnik Reviewer(s):
Based on #30504, which added MacPorts package information, we update the system package scripts to include support for MacPorts.
Current Sage builds just fine on a system with MacPorts.
To test this, we add
local-macports
environments totox.ini
:or
or
Each of these commands creates an isolated installation of MacPorts in a subdirectory of
.tox
(using https://guide.macports.org/#installing.macports.source.multiple); it will not use or modify
/opt/local
.(There is also
tox -e local-macports-optlocal-standard
, which usessudo
to install things into the default location -- use at your own risk.)Requested at
Upstream: Not yet reported upstream; Will do shortly.
CC: @slel @kliem @jhpalmieri @dimpase @seblabbe @vbraun @zlscherr
Component: porting
Author: Matthias Koeppe
Branch/Commit: u/mkoeppe/tox_ini__add_macports_environment @
476fa33
Issue created by migration from https://trac.sagemath.org/ticket/31505
The text was updated successfully, but these errors were encountered: