host: ubuntu 20.04
lfs version : 11.1
in section 6.18. GCC-11.2.0 - Pass 2 , compile the gcc failed.
some errors just like this:
the env:

I take it that's in the make stage, but I don't know.

I'd go back to the beginning of the Binutils package at least (6.17) removing any source dirs and creating new ones. You have to get this right, because everything stands or falls on this. It's also where you find out if you passed over an error in chapters 5 or 6. You have to sort this, and be prepared to go back to the start of chapter 5 to do it.

I can't make much sense of that except that errors shouldn't be there. If it doesn't bale out, let it keep going. It may post warnings & continue. Errors should stop it. Normally when a compile pukes, hit up-arrow & return; it will repeat the make, skip to and show the error, & then bale out. Post that sequence, including your instruction.

This is a lark because ubuntu has your (root) password. And you may have auto-update: you haven't said what gcc you are compiling with or even if it's llvm instead.

Did you try CFLAGS="$CFLAGS -Wno-fpermissive" like the message suggested?

You are compiling GCC-11.2.0. I will share my recipe knowlege. I can compile gcc-10.x with 4.x or 10.x without using -Wno-fpermissive, so I think you have something deeper wrong. But that doesn't mean you can't get away with trying some CFLAGS.

But what compiler are you compiling it with? gcc-6? gcc-10? (and are your headers clean if your in ubuntu not building a whole chain from scratch?)

(ps, GCC-12 has a built-in can't remove feature that downloads during compile from unknown source websites. think about it!)

config.h usally is like "#define HAVE_FOO 1", it doesn't usually do things gcc/include/ does like typedef globally. (i'm not sure on gcc-11.x)

#define ptrdiff_t int

there is a subtly here that ./configure compiles while checking (which sometimes makes compile errors by using malformed tests) that aren't errors for gcc.

You need more of the log posted. Where is config.h?

Did you find it in gcc-11.0-build/ ? Did you attempt building in gcc-11.0 despite it says not to?

sh ./configure 2>&1 >log1 2>&1

and configure keeps it's own log of tests, that should be looked at also

NOW that happened in pass-2 which is not a simple matter. So doubly so you should a build log saying what directory that make(1) is entering and leaving (Q: what part of pass-2).

At this stage in compilation, he'd be using the Pass 1 gcc compiled earlier in chapter 5
I think that's probably bad advice. The recommendation is to follow the Book carefully, at least in your first build. Adding your own flags is usually not a good idea unless you really know what you are doing.

The LFS version being used is slightly out of date but it's only a point release difference so that's unlikely to be the cause of the problem.

Ubuntu isn't considered to be a very good LFS host. Did you ensure before starting that your awk was gawk and not mawk, and your system shell is bash and not dash? All the Debian family use mawk and dash and they aren't recommended. Also, given that Ubuntu is fairly bleeding edge and you are using an older LFS book, did you check that your host compilation tools are not too recent?

1 members found this post helpful.