bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/28885] dlltool broke in 2.38


From: bshanks at codeweavers dot com
Subject: [Bug binutils/28885] dlltool broke in 2.38
Date: Thu, 10 Mar 2022 22:12:22 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=28885

Brendan Shanks <bshanks at codeweavers dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bshanks at codeweavers dot com

--- Comment #1 from Brendan Shanks <bshanks at codeweavers dot com> ---
I think the problem is that multiple instances of dlltool may use the same
temporary file names depending on the files being built.

With fdeee5d59dca41e3c70c399a939105e39a4b4282, the temporary file prefix will
be taken from the .def file, and the .def files may not have unique names. For
example, in mingw-w64-crt/lib64, d3dcompiler_{33,34,35,36}.def all have the
same LIBRARY name inside: "D3DCompiler.dll" [1].

I've also seen this bug when building Wine (on both Linux and macOS), where
multiple dlltools may be launched at the same time to build delay-load and
cross libraries for the same DLL (using the same .spec as input). 

I'm not sure of the best fix for this: maybe add a command-line option to use a
deterministic tmp_prefix, with the caveat that parallel builds may fail?

(As an aside, I'm not sure why one would want deterministic tmp file names.
Maybe for reproducible builds?)


[1]:
https://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/mingw-w64-crt/lib64/d3dcompiler_33.def

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]