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/gcc/spkg-configure.m4: Fix SAGE_BROKEN_GCC test #31097
Comments
comment:1
I think the fix could be to just take out the |
Author: Matthias Koeppe |
Commit: |
comment:3
... please test ... New commits:
|
comment:5
Strange. Even with this ticket included I get
https://github.com/tobiasdiez/sage/runs/1595724994?check_suite_focus=true |
comment:6
You forgot to run |
comment:7
I don't think so, it's under "Install dependencies". |
comment:8
You need to change |
comment:9
Or better, go through tox instead of doing things from scratch again |
comment:10
Thanks! That worked. However, now I get:
so detection is not yet working. |
comment:11
False alarm. It is working for me now! The changes look good to me as well, but I would prefer if somebody else also has a look. |
Changed reviewer from https://github.com/kliem/sage/pull/32/checks to Tobias Diez, ... https://github.com/kliem/sage/pull/32/checks |
Changed reviewer from Tobias Diez, ... https://github.com/kliem/sage/pull/32/checks to Tobias Diez, Jonathan Kliem |
comment:12
I agree, that this locks good. |
comment:13
Thanks! |
Changed branch from u/mkoeppe/build_pkgs_gcc_spkg_configure_m4__fix_sage_broken_gcc_test to |
Code in
build/pkgs/gcc/spkg-configure.m4
, last modified in #30128, tries to use theconfigure
-generated filesrc/bin/sage-env-config
as part of theSAGE_BROKEN_GCC
test.As observed in #30845, this fails on builds from a distclean source tree into a
SAGE_LOCAL
that has an installedg++
.CC: @dimpase @orlitzky @tobiasdiez @kliem
Component: build
Author: Matthias Koeppe
Branch/Commit:
1cf3de4
Reviewer: Tobias Diez, Jonathan Kliem
Issue created by migration from https://trac.sagemath.org/ticket/31097
The text was updated successfully, but these errors were encountered: