date:20231013

[Bug ld/30970] [rfe] please include HPA segelf work

2023-10-13 Thread stsp at users dot sourceforge.net

https://sourceware.org/bugzilla/show_bug.cgi?id=30970 Stas Sergeev changed: What|Removed |Added CC||nickc at redhat dot com -- You are re

[Bug ld/30970] [rfe] please include HPA segelf work

2023-10-13 Thread stsp at users dot sourceforge.net

https://sourceware.org/bugzilla/show_bug.cgi?id=30970 Stas Sergeev changed: What|Removed |Added CC||amodra at gmail dot com -- You are re

[Bug ld/30970] [rfe] please include HPA segelf work

2023-10-13 Thread stsp at users dot sourceforge.net

https://sourceware.org/bugzilla/show_bug.cgi?id=30970 Stas Sergeev changed: What|Removed |Added CC||hpa at zytor dot com -- You are recei

[Bug ld/30970] [rfe] please include HPA segelf work

2023-10-13 Thread stsp at users dot sourceforge.net

https://sourceware.org/bugzilla/show_bug.cgi?id=30970 Stas Sergeev changed: What|Removed |Added CC||hjl.tools at gmail dot com -- You are

[Bug gold/30867] merge.cc:668:27: error: ‘char16_t’ was not declared in this scope

2023-10-13 Thread vvinayag at arm dot com

https://sourceware.org/bugzilla/show_bug.cgi?id=30867 --- Comment #3 from vvinayag at arm dot com --- (In reply to Szabolcs Nagy from comment #2) > on a second thought gold likely requires > > AX_CXX_COMPILE_STDCXX(11, , mandatory) > > in its configure.ac Adding -std=gnu++11 to the binutils CXX

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread nickc at redhat dot com

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #6

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread bruno at clisp dot org

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 --- Comment #5 from Bruno Haible --- I wrote: > No, there are 3 different implementations: The mingw one, the gnulib one, > and the glibc one. Correction: There are 4 different implementations: The binutils one (bucomm.c), the mingw one, the

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread bruno at clisp dot org

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 --- Comment #4 from Bruno Haible --- (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 g

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread bruno at clisp dot org

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 --- Comment #3 from Bruno Haible --- > Given the discussion in PR30958, wouldn't it be better to sync with newer > gnulib? Yes. As indicated in my reply https://lists.gnu.org/archive/html/bug-gnulib/2023-10/msg00058.html , this problem on min

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread sterpumihai at gmail dot com

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 Sterpu Mihai changed: What|Removed |Added CC||eggert at cs dot ucla.edu -- You are

[Bug binutils/30969] ar cannot be safely invoked in parallel on windows

2023-10-13 Thread sterpumihai at gmail dot com

https://sourceware.org/bugzilla/show_bug.cgi?id=30969 --- Comment #2 from Sterpu Mihai --- Hi Sam, The issue is that, from what I see, we now have 2 different implementations. This isn't an easy out of sync case. One might even argue that glibc's implementation is the "outdated" one as it leaks