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
Fix build issue with libpng #25818
Comments
comment:2
Fixing this (and in some cases also not fixing it) seems to break giac, which is linking with That would explain some of the spurious patchbot build failures I've been seeing. |
comment:3
Hmm, it seems we need to patch giac. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Adds a patch to giac to ensure that it links against Amusingly, almost the correct incantation, albeit a bit misspelled, was already in its |
Upstream: Not yet reported upstream; Will do shortly. |
comment:7
I e-mailed the upstream patch to Bernard Parisse. |
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet. |
comment:8
I guess?
|
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release. |
Reviewer: Julian Rüth |
comment:10
Several patchbots appear to be in some kind of broken state. I don't think it's due to this ticket; rather their owners should probably reset them. |
comment:11
I believe this issue can reasonably be addressed for Sage 8.4. |
Changed branch from u/embray/build/libpng/symlinks to |
I just noticed this small bug in the DESTDIR build support for libpng. This might explain why I and others sometimes have build problems surrounding libpng.
This symlink should get deleted before it's installed in
$SAGE_LOCAL
. Otherwise it takes a re-installation of libpng in order to force the symlink to be removed.Upstream: Fixed upstream, but not in a stable release.
Component: packages: standard
Author: Erik Bray
Branch/Commit:
afb74b9
Reviewer: Julian Rüth
Issue created by migration from https://trac.sagemath.org/ticket/25818
The text was updated successfully, but these errors were encountered: