Opened 9 years ago
Last modified 5 years ago
#13044 closed defect
ecl chokes when CC or CXX contains space — at Version 19
Reported by: | ohanar | Owned by: | GeorgSWeber |
---|---|---|---|
Priority: | major | Milestone: | sage-7.2 |
Component: | packages: standard | Keywords: | sd40.5 |
Cc: | Merged in: | ||
Authors: | R. Andrew Ohana, Erik Bray | Reviewers: | |
Report Upstream: | Fixed upstream, but not in a stable release. | Work issues: | |
Branch: | u/embray/issue-13044 | Commit: | c9f77c6dc61f6d3684716df620706f05a0604b64 |
Dependencies: | Stopgaps: |
Description (last modified by )
Currently ecl completely fails to build when CC or CXX contains a space. This hacks around this issue by making temporary wrappers for CC and CXX.
Change History (19)
comment:1 Changed 9 years ago by
- Description modified (diff)
- Status changed from new to needs_review
comment:2 Changed 9 years ago by
- Description modified (diff)
- Summary changed from ccache chokes on ecl to ecl chokes when CC or CXX contains space
comment:3 Changed 9 years ago by
comment:4 Changed 9 years ago by
- Component changed from build to packages
comment:5 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:6 Changed 7 years ago by
- Status changed from needs_review to needs_info
Is this still needed?
comment:7 Changed 7 years ago by
- Status changed from needs_info to needs_review
Yes, it is still needed.
comment:8 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:9 Changed 7 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:10 Changed 7 years ago by
- Status changed from needs_review to needs_work
This needs to be converted to a new-style package, for the ECL version we currently use.
comment:11 Changed 7 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:12 Changed 5 years ago by
I can confirm this is still an issue--sage build breaks on ecl when CC=ccache gcc
--obviously this can be worked around easily enough, but setting CC
like that is not uncommon either, and only seems to be a problem with ecl.
Would this be worth patching in ecl (both upstream and in sage)?
comment:13 Changed 5 years ago by
The updated spkg mentioned in this ticket is a 404 now.
comment:14 Changed 5 years ago by
Current upstream is https://common-lisp.net/project/ecl/
Also ecl-16.0.0
has been released and it would be nice to upgrade. It would be worth checking if it is still an issue in the latest release.
comment:15 Changed 5 years ago by
There is a similar bug that I've just run into, but in Python, when compiling the Cython sources. I've never run into this before strangely, but maybe have just worked on fewer projects with cpp generated from Cython: https://bugs.python.org/issue8027
I will check if the ecl issue is fixed upstream.
comment:16 Changed 5 years ago by
FYI this bug still exists upstream, or at least in ecl-16.0.0. I will see if I can come up with a patch.
comment:17 Changed 5 years ago by
- Report Upstream changed from N/A to Reported upstream. No feedback yet.
Submitted a patch to upstream: https://gitlab.com/embeddable-common-lisp/ecl/merge_requests/20
comment:18 Changed 5 years ago by
- Branch set to u/embray/issue-13044
- Commit set to c9f77c6dc61f6d3684716df620706f05a0604b64
- Status changed from needs_work to needs_review
Added the patch to the spkg. It applies to the current version of the spkg with a bit of fuzz.
If I understand correctly I should also update the patch version, and upload a new source package? Not sure exactly how to go about that though.
New commits:
c9f77c6 | Add patch to ecl for building when CC=ccache gcc (or the like) from https://gitlab.com/embeddable-common-lisp/ecl/merge_requests/20
|
comment:19 Changed 5 years ago by
- Description modified (diff)
- Milestone changed from sage-6.4 to sage-7.2
I can verify that our current ECL chokes with "
env CC='nice gcc' ./spkg -i ecl...
" and that your spkg fixes it. Perhaps it would be nice to put something into the generatedecl_cc
so we know whence it came: maybe a comment like# ECL chokes when CC contains spaces; this script works around that. See #13044.
Then it would be easier to remove this workaround when ECL is updated.Also, I tried
env CXX='nice g++' ./sage -f ecl...
with the old version and it worked fine. Perhaps we shouldn't also createecl_cxx
since ECL is not using a C++ compiler.Also
^2
, we should send this upstream.