The glibc ebuild always ignores the nostrip FEATURES flag, but it shouldn't be ignored; there are a number of valid reasons *not* to strip glibc. I have no idea why stripping is forced enabled regardless of the nostrip FEATURES flag... This should probably be fixed. Reproducible: Always
From the glibc ebuild... # we'll handle stripping ourself #46186 RESTRICT="nostrip multilib-pkg-force"
As said above, NOTABUG.
Would you be able to attach a modified ebuild for glibc that does not perform any stripping? I tried to modify the ebuild myself but it seemed to still strip everything. I really need to get a non stripped glibc. Thank you.
We won't do it; it breaks things. Read the referenced bug and bunch of others. Do not mess with toolchain stuff.
Just to be clear, you're saying that if the glibc is *NOT* stripped, then this causes bugs? I need to build a glibc that is *NOT* stripped so that I can use some tools which require symbol information from glibc.
I'm going to reopen this again because I believe the glibc ebuild should obey the nostrip keyword. I very much doubt that not stripping the resulting binaries and libraries would cause any problems. In fact, it's usually the opposite; stripping binaries and libraries can lead to problems. Regardless, the ebuild should obey the nostrip keyword as nostrip is not enabled by default, and anyone who does enable it usually has good reason to do so.
Never mind, it turned out to be a silly spelling error in make.conf so nostrip never got applied, and thus my changes to the ebuild wouldn't take effect anyway. I'll close this now.
