Re: Conflicting build-ids in nekovm and haxe

2023-05-07 Thread Mark Wielaard
Hi Andy, (Please do put me on CC, I do try to read all of devel list, but it is easy to miss something) On Tue, May 02, 2023 at 11:42:30AM -, Andy Li wrote: > Sorry for the late reply. I just got back to this issue. > > > In general this (should) only happen if the binaries are really > > i

Re: Conflicting build-ids in nekovm and haxe

2023-05-02 Thread Andy Li
Sorry for the late reply. I just got back to this issue. > In general this (should) only happen if the binaries are really > identical (e.g. when one of the packages build requires the other, but > instead of linking/rebuilding some sources it simply copies a binary > directly). > > The build-id

Re: Conflicting build-ids in nekovm and haxe

2020-11-15 Thread Mark Wielaard
Hi Andy, On Fri, 2020-11-13 at 02:16 +, 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

Re: Conflicting build-ids in nekovm and haxe

2020-11-13 Thread Leigh Scott
> You could try adding this to one of the spec files > > export LDFLAGS="%{?__global_ldflags} --build-id=md5" I mean export LDFLAGS="%{?__global_ldflags} -Wl,--build-id=md5" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send a

Re: Conflicting build-ids in nekovm and haxe

2020-11-13 Thread Leigh Scott
You could try adding this to one of the spec files export LDFLAGS="%{?__global_ldflags} --build-id=md5" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: h

Re: Conflicting build-ids in nekovm and haxe

2020-11-13 Thread Petr Pisar
On Fri, Nov 13, 2020 at 02:16:46AM -, 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 "

Conflicting build-ids in nekovm and haxe

2020-11-12 Thread Andy Li
Hi list, 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