|
From: | JD |
Subject: | [Gm2] Previous problem with build on Raspberry Pi has returned |
Date: | Mon, 21 Apr 2014 20:15:38 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
Gaius, After my long run, reaching the point where you thought "it was running the compiler to find out the builtin types and functions", I didn't do any debugging as I noticed that my filesystem was corrupt and almost full. I've re-installed Raspbian, then installed libmpfr-dev libgmp-dev libmpc-dev flex & dejagnu. I couldn't find a gcc-multilib - this could be my problem. I copied the directories asm, bits, gnu & sys to /usr/include. I linked the 3 'crt' files to ~/GM2/scratch-area/build-4.7.3/./gcc/ as before. On the next run I realised something ridiculous about my previous attempts. After linking the crt files I was at first just re-running make. You advised me to re-run configure as well, so I started at the top again. This meant that everything below GM2 was deleted, including the linked crt files. But even so it ran and ran - for 7 days! Why? Now, though, my RPi has become a lot more sensible and it consistently fails if the crt files are not where expected. I now ensure they are available by putting in commands to create the gcc directory immediately after the configure and then linking the files. The failure I cannot overcome is the same or similar as one I reported before the re-install (see V90 issue 4): usr/bin/ld: error: ./libgcc_s.so.1.tmp uses VFP register arguments, pr-support_s.o does notOn my original runs this failure also disappeared after a while and the build ran almost to the end as you know. The only change I thought might have an effect now is in the configure options: I changed disable-multilib to enable-multilib and added enable-multiarch . No difference. Any ideas? Regards, John |
[Prev in Thread] | Current Thread | [Next in Thread] |