#10572: gcc/binutils wrapper
----------------------------+-----------------------------------------------
Reporter: vbraun | Owner: GeorgSWeber
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.6.2
Component: build | Keywords: gcc wrapper rpath gccwrapper spkg
Author: Volker Braun | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------------+-----------------------------------------------
Comment(by vbraun):
You can simply not use the wrapper if you have any other compiler, and
rpath/runpaths will remain broken as they are right now. In particular,
any distribution that wants to include Sage would just use their own
compiler without wrapper and install libraries in the library search path.
And upgrade their compiler if it dies while compiling pari :-)
I wrote autoconf macros to detect the linker used (Gnu/Sun/OSX), so it
should work with either linker. Anything else is a bug that I'll be happy
to fix.
In principle, other compilers could be supported by their own compiler
wrapper. Since we currently can't use any other compiler, I haven't
written any other wrapper. If the compiler/linker provides another way to
set the rpath, then we don't need any wrapper of course.
Another possibility is to write a translator from the gcc compiler
switches to some 3rd party compiler, and then use that other compiler
without Sage knowing about it. I haven't tried this, but it might be
easier than fixing all spkgs on rare hardware.
The point of translating cc->gcc is that this symlink was missing on one
of the itanium machines on skynet (iras). I fixed that bug and checked
that no other component of Sage tries to call cc. While thats clearly a
broken gcc install, it arguably doesn't hurt to override it in the wrapper
if you know that you are using gcc. Though you make a good case for not
overriding cc at all, since it might be the Solaris compiler. One question
is whether we can rely on the names of the compiler executables to be all
different, or whether there are conflicts. I know that gcc and icc don't
clash, but Solaris' cc is bound to be the same name as some other
compiler?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10572#comment:19>
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.
