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
ppl library problems on Arch Linux, OpenSuse: _ZN23Parma_Polyhedra_Library13have_sse_unitE #11391
Comments
comment:1
A temporary fix for me before running `make' was to do the following: |
comment:2
It seems that with sage 4.8, this workaround doesn't work anymore. |
comment:3
Attachment: sage.output.i686.gz This is what I get when trying to compile with the workaround:
Output:
attached the full build output as sage.output.i686.workaround.gz |
comment:4
Attachment: sage.output.i686.workaround.gz just rebuilt 4.7.2 and it works, so this was introduced in 4.8 for sure. |
comment:5
I think that the following post (for OpenSuse 12.1) mentions exactly the same underlying problem: http://groups.google.com/group/sage-devel/browse_thread/thread/a7017c8f3b0a16c0 It seems that from Sage 4.8 on, the ppl (Parma Polyhedra Library) got interfaced by the Sage core. So the "workaround" to not build the ppl spkg at all ("touch spkg/installed/ppl-0.11.2.p0") simply won't work for Sage 4.8 and later (since the respective headers are needed)! As long as the ppl library included in Sage and the ppl library of the host OS do not differ too much (they seem to be "close enough" right now in the known cases Arch Linx, OpenSuse 11.4 - 12.1), one probably could use a different workaround: a) do build the ppl spkg (in order to get the header files in place) b) after that (just waiting for the "breakage" might be sufficient), replace the library binary ("libppl.so.9.0.0" or so) under $SAGE_LOCAL/lib/ with a symlink to the host OS'es libppl. For some "correct" solution, one would either have to update the ppl spkg to install a newer version of ppl, to match the one of the host OS(es) --- somewhat a "moving target" (we might end up with having to provide several different versions of ppl in the spkg). Or provide the technical foundation so that the libraries brought with Sage do not (i.e. no longer) interfere with libraries on the host OS (the ticket #10572 describes one of several ways to do so). Cheers, Georg |
comment:6
I don't know if this is a known thing, but one of Arch Linux users (going by name Snowball on AUR, the Arch Linux User Repository) posted a working solution for ppl problem on i686, and it is quite a simple change to ppl spkg:
I tested this in i686 VM of Arch Linux and can confirm that with this change to ppl spkg it works (right now Sage 4.8 still builds, but it got past pycrypto where it failed before). Unfortunately right now I don't have time to post an updated spkg, but I decided to let others know about it anyway. |
comment:7
I finished building 4.8 without any issue on current Arch Linux i686, also found some time so I decided to refresh my knowledge and package new ppl. The spkg with mentioned fix is here: https://github.com/downloads/aginiewicz/spkgs/ppl-0.11.2.p2.spkg - I hope I still remember how to package for Sage. |
comment:9
This is a duplicate of #12672 (which has the same solution for a different problem). |
comment:10
Replying to @jdemeyer:
I think it is not a duplicate. #12672 is about building the C interface of PPL, which is currently not done. Solving build problems on some platforms is an orthogonal problem, IMHO. |
comment:11
Replying to @simon-king-jena:
As I said, ticket #12672 has the same solution for a different problem. |
comment:12
Aha, now I see the comment of aginiewicz: "a working solution for ppl problem on i686, and it is quite a simple change to ppl spkg:
So, you are right, it is about building interfaces, in order to achieve something else. Since #12672 has an spkg (even though it fails on OS X because of missing m4): What shall we do? Close this ticket as a duplicate? Leave both open? Do we need an m4 spkg? |
comment:13
Replying to @simon-king-jena:
I think we should have an m4 spkg, but most people disagree (there was a mailing list post on this). |
comment:14
Please fill in your real name as Author. |
Author: Andrzej Giniewicz |
comment:16
Just got another report of this error on the mailing list. We really should fix this. |
comment:17
Would #12672 work, modulo providing an m4 spkg on OS X? |
comment:18
The difference between spkg in #12672 and spkg I posted in comment:7 (that contains fix used by Arch Linux package, i.e. is tested in production environment) is only "make install" vs "make install-strip", so I'd say yes - both spkgs fixes this and #12672 - but both would have issues with m4 on OS X. |
comment:19
Replying to @simon-king-jena:
Absolutely. Just got another report of this error on the mailing list. We really should fix this. |
Changed author from Andrzej Giniewicz to none |
Reviewer: Jeroen Demeyer |
comment:21
Fixed by #14232. |
I am using the sage 4.7 release.
I'm trying to package sage for archlinux, and the x86_64 version compiled fine. But the i686 version of the package failed with the error described here:
http://groups.google.com/group/sage-devel/browse_thread/thread/84b2f4d94d50e735
The complete install.log can be found here:
http://pkgbuild.com/~td123/install.log.gz
The relevant install.log portion (the error message) is:
http://pastie.org/pastes/1980914/text
CC: @sagetrac-aginiewicz
Component: packages: standard
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/11391
The text was updated successfully, but these errors were encountered: