Failures in libcc1 while building GCC 6.1.0 on Raspberry Pi

tmose1106 · 05-29-2016, 08:17 AM

Hello, so here is the rundown:

I am attempting to build LFS systemd on my Raspberry Pi 3. I wrote my own build scripts which you can look at HERE. Unfortunately, I am running into an issue with build GCC 6.1.0, which is similar to Chapter 6.17 in the systemd book.

So, I have included two config.logs related to the error message I saw when the build failed. I put them in a GitHub Gist HERE. I was just wondering if anyone could decipher these two logs and see what the issue may be? Or just give me some helpful advice. Thanks.

business_kid · 05-30-2016, 03:58 AM

Someone else ran into this recently. Does LFS support GCC-6.1 yet? Or are they still on 5.3?

hazel · 05-30-2016, 06:01 AM

Quote:

Originally Posted by business_kid

Someone else ran into this recently. Does LFS support GCC-6.1 yet? Or are they still on 5.3?

It's in the development version but not in stable.

tmose1106 · 05-30-2016, 07:38 AM

While it is true that GCC 6.1 is in the developement version of Linux from Scratch, I have found it to build just fine on 64-Bit PCs (using the same build scripts as well). After all, ARM processors are not even supported by LFS, so I believe compatability in LFS does not have (much) to do with the issue.

On the other hand, I have made up another Gist of the actual build error, which seems to occur on line 4143, and reads, "configure: error: C preprocessor "/lib/cpp" fails sanity check". Once again, does anyone have any experience with this issue? Are there any more logs I should make a Gist of? I would really appreciate the help.

business_kid · 05-30-2016, 08:38 AM

The stable book is still on gcc-5.3. Must be a reason ...

Code:

checking how to run the C preprocessor... /lib/cpp
configure: error: in `/gcc-6.1.0/build/armv7l-unknown-linux-gnueabihf/libgcc':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

What does config.log indicate? And how does lib/cpp behave? does it exist? They'll have pulled some basic test and it failed. Dig a bit - you have to get used to that with LFS.

tmose1106 · 05-30-2016, 09:00 AM

I beleive the stable book only gets released every few months, so that is that.

But, the config.log does inform me that /lib/cpp does not exist about four times, and then fails the sanity check. Here is another gist of the actual log in that directory. I'm just confused on how this occurs. My chapter 5 toolchain builds without error, as do all the packages in Chapter 6 up until GCC. So what does this mean? Is my toolchain actually flawed? Is the host system causing issues?

business_kid · 05-30-2016, 09:42 AM

The stable book gets released when it's ready and not before. Everything has to build cleanly.
In chapter 5, you use the base system, with whatever gcc, glibc, & kernel headers are there. Sometimes that's quite old, (e.g. stable debian installs) or non standard, (think Red Hat & friends). In chapter 6 you should be using the static system in ch. 5 to build the dynamic system in ch. 6.

A poor base system can compile a poorly functional static system in weird and wonderful ways. Have you tried approaching from CLFS instead of LFS?