-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
build/pkgs/python3/spkg-install: Install valgrind-python.supp in $SAGE_LOCAL, not in $SAGE_SRC #29062
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
Author: Matthias Koeppe |
comment:3
Makes sense to me, although I don't know about adding the Debian-specific paths. How standard is |
comment:4
my Fedora box has |
comment:5
Replying to @dimpase:
OK I'll add that. |
comment:6
Replying to @embray:
As far as I can see,
A follow-up ticket. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
Ready for review |
comment:11
How can this be tested? |
comment:12
Check that sage-valgrind works without error in a fresh build from a distclean source, both in a python2 and python3 build. |
This comment has been minimized.
This comment has been minimized.
comment:14
this is what I see on py3 on Debian 10
Is this what's expected? PS. |
comment:15
Yes, looks right. |
comment:16
I'll run a whole build of this branch on py2, just to be sure. |
comment:17
On py2 it does not seem to get installed in the right place:
In install log I see
and the same with files And then
Is this branch missing needed py2 changes? |
comment:18
This all looks fine... Are you using |
comment:19
Does the |
comment:20
Replying to @mkoeppe:
no. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:22
Thanks for catching this. |
comment:23
have you fixed the problem? I only see a change in |
comment:24
Py2 has a symlink to the same script |
comment:25
Replying to @mkoeppe:
this is evil :-) |
comment:26
Wasn't me :) |
comment:27
OK, good, this works for py2. I'll double-check for py3 - the previous check might have been faulty due to incomplete cleaning... |
comment:28
Thanks! |
Reviewer: Dima Pasechnik |
comment:29
looks good. |
comment:30
Thanks for reviewing! |
Changed branch from public/29062-valgrind-python-to-SAGE-LOCAL to |
valgrind-python.supp
is supplied by the Python source code tarball. Currently ourspkg-install
copies it to$SAGE_SRC/ext
, from where it is copied to$SAGE_LOCAL/share/sage/ext/
.In preparation for #27824 - spkg-configure.m4 for python3:
spkg-install
to install the file in$SAGE_LOCAL/lib/valgrind/
instead.sage -valgrind
more flexible in where it expects the file.This change also has the side effect of removing a peculiar use of
SAGE_EXTCODE
during building. This simplifies #21785.Related old tickets:
CC: @dimpase @embray @rwst @jhpalmieri @jdemeyer @vbraun
Component: build
Author: Matthias Koeppe
Branch/Commit:
e01a340
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29062
The text was updated successfully, but these errors were encountered: