#13689: Rebuild GCC when Sage has been moved
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: defect | Status: new
Priority: blocker | Milestone: sage-5.4.1
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Description changed by jdemeyer:
Old description:
> It seems `sage-location` does not properly fix GCC. In particular, the
> output of `gcc -print-search-dirs` (which is used by `libtool` for
> example) is wrong after relocating Sage.
>
> This can give problems in the following scenario:
> 1. install Sage from source, including Sage's GCC
> 2. relocate Sage
> 3. rebuild PPL
> 4. rebuild !LinBox
>
> The obvious solution is to rebuild GCC when needed.
>
> Blocker because it breaks upgrading in certain cases.
New description:
It seems the old version of `sage-location` does not properly fix GCC,
leading to problems with upgrading in the following scenario:
1. install sage-5.3 from source, including Sage's GCC
2. relocate Sage
3. rebuild PPL
4. rebuild !LinBox
The `sage-location` in `sage-5.4.1.rc0` does things properly, but that's
not sufficient for upgrading.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13689#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
