Created attachment 493814 [details] ppc64le-stage2.log.xz ACCEPT_KEYWORDS="ppc64" after previously installing some unkeywording packages. I will need more time to go back through and regenerate the RAP with manually keyworded packages.
If you are needed ACCEPT_KEYWORDS="ppc64", that means you haven't created linux-standalone profile for ppc64 correctly. Could you show which part of bootstrap-rap.sh you modified and what profile you created?
*** Bug 630564 has been marked as a duplicate of this bug. ***
Is it a CentOS host and do you have package glibc-devel installed?
The profile was set to "../../usr/portage/profiles/prefix/linux-standalone/ppc64/." I have also attempted a bootstrap with it set to "../../usr/portage/profiles/prefix/linux/ppc64/." It is just the case I chose that syntax to describe the ACCEPT_KEYWORDS in use. In older reports I had to set it to "**" to get this far. Bootstrap-rap.sh is unmodified. Likewise, no profile was created. The host runs CentOS 7. I can't tell for certain whether glibc-devel is installed, but "/usr/include/gnu/stubs-64-v2.h" exists. Should it matter what the host has installed? As long as a compiler (i.e. most distribution's build-essential package) is available I don't see why bootstrap-rap.sh should fail. Is glibc for the RAP not built before GCC?
(In reply to R030t1 from comment #4) > The profile was set to > "../../usr/portage/profiles/prefix/linux-standalone/ppc64/." I have also > attempted a bootstrap with it set to > "../../usr/portage/profiles/prefix/linux/ppc64/." It is just the case I > chose that syntax to describe the ACCEPT_KEYWORDS in use. In older reports I > had to set it to "**" to get this far. > > Bootstrap-rap.sh is unmodified. Likewise, no profile was created. profiles/prefix/linux-standalone/ppc64/ is big endian, completely different ABI from ppc64le. We don't have ppc64le RAP profile, you need to create one by yourself and test it before we push one into the repository. > The host runs CentOS 7. I can't tell for certain whether glibc-devel is > installed If you do a bit of study, you will find the command is `rpm -ql glibc-devel`.
I added a CHOST to my profile's make.defaults of "powerpc64le-unknown-linux-gnu" and now compilation fails in stage 3. I suppose this issue is closed now, but I am confused as to why the compiler was generating usable binaries. I was able to find if glibc-headers was installed but the corresponding header was not there.
