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
Error installing package gcc-4.7.3.p1 on ARM boards #15702
Comments
comment:1
I don't remember if I built GCC or not. I'll still have a look at your problem, but it seems strange that GCC is not smart enough to select soft/hard floats or even build multilib. |
install.log from failing gcc build on Raspberry Pi |
comment:2
Attachment: install.log.gz Since install.log is only somewhat larger than gcc-4.7.3.p1.log I added the complete log. |
comment:3
Can you try recompiling using
(Only the value of GCC_CONFIGURE actually matters.) If that's not enough, you could try
|
comment:4
Ok, I could reproduce the error on raspbian. |
comment:5
Jean-Pierre, my RaspPi is just trying the first variant (w/o float=hard). |
Attachment: gcc-4.7.3.p1.log.gz Error log file of gcc (with: GCC_CONFIGURE="--with-fpu=vfp" ./sage -i gcc) |
comment:7
The next run was failing, too. To be clear, here is a snippet from my current spkg-install:
As I started the second run (after changing spkg-install) just by calling ./make again, Therefore I am now doing a clean build with float=hard ... PS.: The log-file is available for upload. |
Attachment: gcc-4.7.3.p1.log-hard-2.gz Latest error log with the float=hard modification. |
comment:8
Strange, it seems you failed in the same spot. In my tests:
And you don't need to modify spkg-install. On top of that you removed some options from GCC_CONFIGURE (the checinkg stuff) and that is not taken into account as the snippet you modified is within a SAGE_CHECK=yes part (and thats unset by default). |
comment:9
Jean-Pierre, I apparently did not interpret your comment:3 correctly :-/ I just restarted building gcc (with the original, unmodified spkg-install and with
entered on the terminal. Thanks for teaching me ... :-) |
Log of failed atlas build. |
comment:10
Attachment: atlas-3.10.1.p7.log.gz
After that I restarted [RunGMMSearch] Error 255 ... and thereafter some failed assertions. |
comment:11
Please don't post gzipped files on the trac server unless really necessary. |
comment:12
About the ATLAS problem, it may be gcc segfaulting because of an ICE or lack of virtual memory, but I wouldn't even try to fix that, at least not here. |
comment:13
The actual ATLAS error is:
|
comment:14
Which is no problem with the system GCC. |
comment:15
Replying to @jpflori:
It seems to do the trick. |
Changed keywords from Raspberry Pi, armv6 gcc to Raspberry Pi, armv6l gcc |
Commit: |
Branch: u/jpflori/ticket/15702 |
New commits:
|
Changed author from Wilfried Luebbe to Jean-Pierre Flori |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
Added support for armv7 (hard floats only as well). |
comment:19
After applying the patch on my RaspberryPi I could build gcc and then build the rest of Sage 6.0. But it is a positive review for resolving my original defect. |
Reviewer: Wilfried Luebbe |
Changed branch from u/jpflori/ticket/15702 to |
The starting point is
Installing GCC because a Fortran compiler is missing.
After
there are LOTS of messages like
The problem seems be a conflict between hard and soft FP (http://stackoverflow.com/questions/9753749/arm-compilation-error-vpf-registered-used-by-executable-not-object-file).
In http://trac.sagemath.org/wiki/ExoticPorts jpflori also mentions hard floats.
The problem can of course easily circumvented by
apt-get install gcc g++ gfortran
.Side remark: Since building Sage from source on Raspberry Pi already takes almost 5 days with the three compilers pre-installed (compared to 1 hour on my 4 core i750 desktop) - building gcc may NOT be the recommended way ...
But to avoid a build error even on an exotic platform and if there is a simple fix ...
CC: @jpflori
Component: build
Keywords: Raspberry Pi, armv6l gcc
Author: Jean-Pierre Flori
Branch/Commit:
9f3a73e
Reviewer: Wilfried Luebbe
Issue created by migration from https://trac.sagemath.org/ticket/15702
The text was updated successfully, but these errors were encountered: