Bad path on removal of libatomic causing compilation failure

Anubis 1101 Anubis1101@pm.me
Sat Nov 15 07:23:20 GMT 2025


Good question, I just ran config from whatever folder it was delivered in. I thought using the -prefix command would change the directory, but it never generated the specified folder, so I'm not sure. Definitely seems like the kind of mistake someone who's not used to building projects like this would make, so hopefully it's that easy.

I'll take a look at it tomorrow, and try out your suggestion.




On Friday, November 14th, 2025 at 10:19 PM, Sam James <sam@gentoo.org> wrote:

> 
> 
> Anubis 1101 via Gcc-help gcc-help@gcc.gnu.org writes:
> 
> > The full configure line was just "./configure". The first time around, I didn't use any special modifiers.
> > I did run it a few times, and experimented with using the prefix
> > command and a few others to see if I could change things, but at best
> > it still just ran for 20 or so minutes, and then exited with "Error
> > 2".
> 
> 
> I wonder if you're building in-tree? Are you running `./configure`
> inside of your git checkout directly, or within a subdirectory you
> create?
> 
> Try this:
> $ git clone ...
> $ mkdir build && cd build
> $ ../configure && make -j$(nproc) -l$(nproc)
> 
> > I'm not even sure what you mean by patches, which hopefully means I'm not using any. I'm just using the source cloned from the official repository via Git.
> 
> 
> Yeah, indeed means none.
> 
> > > On Friday, November 14th, 2025 at 7:52 PM, Sam James sam@gentoo.org wrote:
> > > 
> > > > Anubis 1101 via Gcc-help gcc-help@gcc.gnu.org writes:
> > > > 
> > > > > I'm trying to compile GCC 15.1 for my x86 Linux machine. Everything
> > > > > seems to be going well, and it compiles happily for about 20 minutes
> > > > > or so, until it fails an rm command on libatomic.la, with the message:
> > > > > rm: cannot remove '[...]/x86_64-pc-linux-gnu/32/libatomic/../../../gcc//32/libatomic.la': No such file or directory
> > > > 
> > > > Please show us the full configure line used and whether you've applied
> > > > any patches.


More information about the Gcc-help mailing list