#12703: GLPK fails to build with LTO (`gcc -flto ...`)
------------------------------------------------------------------------+---
Reporter: leif |
Owner: leif
Type: defect |
Status: needs_review
Priority: minor |
Milestone: sage-5.0
Component: packages |
Resolution:
Keywords: link time optimization nm glpsol spkg upgrade update |
Work issues:
Report Upstream: Reported upstream. Developers acknowledge bug. |
Reviewers:
Authors: Leif Leonhardy |
Merged in:
Dependencies: |
Stopgaps:
------------------------------------------------------------------------+---
Old description:
> Even the latest upstream version (4.47) fails to build when link-time
> optimization (LTO, `gcc -flto ...`) is enabled.
>
> While `configure` shows an error message, it continues normally and
> doesn't exit with an error. Only later during the build, a shell syntax
> error caused by `libtool` makes the build finally fail.
>
> The solution is to re-autotoolize the package with more recent autotools.
>
> I have an spkg with updated autogenerated files which also upgrades GLPK
> within Sage to the latest stable version, 4.47.
>
> ----
>
> '''New spkg:'''
> [http://boxen.math.washington.edu/home/leif/Sage/spkgs/glpk-4.47.p0.spkg]
>
> '''md5sum:''' `820b1169551ca7da973a09a672da1560 glpk-4.47.p0.spkg`
>
> === glpk-4.47.p0 (Leif Leonhardy, March 19th 2012) ===
> * #12703: Make GLPK work with LTO (`gcc -flto ...`).
> This just involves updating the lib- and autotools files,
> but thereby upgrading to the latest version (4.47) shouldn't
> hurt either.
> Note that the `src/` directory now isn't vanilla, since upstream
> hasn't yet fixed the bug (i.e., updated these files).
> The "real" source files in contrast of course *are*.
> See "Special Update/Build Instructions" above on how to update
> the files of a fresh upstream tarball if necessary.
> * Cleaned up `spkg-install` and `spkg-check` (and this file ;-)
> * Running the test suite now uses `$MAKE` instead of `make` as well.
> * `CPPFLAGS` and `LDFLAGS` no longer get overwritten in `spkg-install`.
New description:
Even the latest upstream version (4.47) fails to build when link-time
optimization (LTO, `gcc -flto ...`) is enabled.
While `configure` shows an error message, it continues normally and
doesn't exit with an error. Only later during the build, a shell syntax
error caused by `libtool` makes the build finally fail.
The solution is to re-autotoolize the package with more recent autotools.
I have an spkg with updated autogenerated files which also upgrades GLPK
within Sage to the latest stable version, 4.47.
----
'''New spkg:'''
[http://boxen.math.washington.edu/home/leif/Sage/spkgs/glpk-4.47.p1.spkg]
'''md5sum:''' `090ee5d398582db531b27e49deab6749 glpk-4.47.p1.spkg`
=== glpk-4.47.p1 (Leif Leonhardy, March 22nd 2012) ===
* #12703: Make GLPK work with LTO (`gcc -flto ...`).
Export CPPFLAGS, since `sage-env` currently *doesn't*.
=== glpk-4.47.p0 (Leif Leonhardy, March 19th 2012) ===
* #12703: Make GLPK work with LTO (`gcc -flto ...`).
This just involves updating the lib- and autotools files,
but thereby upgrading to the latest version (4.47) shouldn't
hurt either.
Note that the `src/` directory now isn't vanilla, since upstream
hasn't yet fixed the bug (i.e., updated these files).
The "real" source files in contrast of course *are*.
See "Special Update/Build Instructions" above on how to update
the files of a fresh upstream tarball if necessary.
* Cleaned up `spkg-install` and `spkg-check` (and this file ;-)
* Running the test suite now uses `$MAKE` instead of `make` as well.
* `CPPFLAGS` and `LDFLAGS` no longer get overwritten in `spkg-install`.
--
Comment (by leif):
The new p1 spkg fixes a potential error if `CPPFLAGS` aren't exported.
(`sage-env` currently '''doesn't''' export `CPPFLAGS`, which I assumed it
also does.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12703#comment:3>
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.
