[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/30969] ar cannot be safely invoked in parallel on windows
From: |
bruno at clisp dot org |
Subject: |
[Bug binutils/30969] ar cannot be safely invoked in parallel on windows |
Date: |
Fri, 13 Oct 2023 13:53:15 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=30969
--- Comment #4 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Sterpu Mihai from comment #2)
> The issue is that, from what I see, we now have 2 different implementations.
No, there are 3 different implementations: The mingw one, the gnulib one, and
the glibc one.
The binaries that you are running use the mingw implementation. All your
argumentation about the gnulib code vs. the glibc code is therefore pointless.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/30969] New: ar cannot be safely invoked in parallel on windows, sterpumihai at gmail dot com, 2023/10/12
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, sam at gentoo dot org, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, sam at gentoo dot org, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, sterpumihai at gmail dot com, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, sterpumihai at gmail dot com, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, bruno at clisp dot org, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows,
bruno at clisp dot org <=
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, bruno at clisp dot org, 2023/10/13
- [Bug binutils/30969] ar cannot be safely invoked in parallel on windows, nickc at redhat dot com, 2023/10/13