Bad path on removal of libatomic causing compilation failure
Segher Boessenkool
segher@kernel.crashing.org
Sun Nov 16 15:25:21 GMT 2025
Hi!
On Sun, Nov 16, 2025 at 02:55:38PM +0000, Anubis 1101 wrote:
> Just figured it out, I was in a hurry to compile it and didn't perform the basic step of creating a separate
> build directory; I tried to compile right from the source directory, and that caused the failure.
Yes, building in the source folder (or any subdirectory of it) isn't
supported.
> I agree though, it shouldn't fail. If this is such a critical problem, I feel like a simple check for it should be
> included, like "Hey, buddy, ever heard of Best Practices?".
> But, GCC is a huge project, so perhaps there's a specific reason why they don't, or perhaps it's an easy filter for
> people like me.
And yes, it would be nice if all the things that make this restriction
necessary are fixed! But we obviously are not there yet, and that was
the reason this was put in the installation instructions at all.
But, alternatively, we still do not simply check for the user following
these basic instructions (and then say "Sorry, but..." if things aren't
right). That would be an obvious improvement :-)
Segher
More information about the Gcc-help
mailing list