On Fri, Nov 13, 2020 at 02:16:46AM -0000, Andy Li wrote:
Re.
https://bugzilla.redhat.com/show_bug.cgi?id=1896901
Since haxe-4.1.3-4 and nekovm-2.3.0-4, both nekovm and haxe packages contains
"/usr/lib/.build-id/b0/aed4ddf2d45372bcc79d5e95d2834f5045c09c".
The nekovm one is a symlink to "/usr/bin/neko". The haxe one to
"/usr/bin/haxelib".
Both the neko and haxelib binaries are built with libneko, with a nearly identical main.c
with the only difference of the present of neko bytecode embedded as a byte array (neko:
the byte array is null; haxelib: the byte array is the haxelib neko bytecode).
I'm not sure how to resolve it.
Please advice.
It means that the compiler identified a common compilation unit. A candidate
for moving it to a dynamic library and making it a common dependency :)
Seriously we have seen this issue when projects bundled the same Wekbit.
I don't remember what remedy was used. Maybe patching the code to differ
enough to get a different build-id hash.
-- Petr