On Mon, 31 Jan 2022 at 14:29, Alexander Kanavin
wrote:
> On Mon, 31 Jan 2022 at 13:52, Anton Khirnov wrote:
>
>> With a separate build directory, I'm getting
>> $ strings libavutil/x86/tx_float.o |grep asm
>> src/libavutil/x86/tx_float.asm
>>
>
>
On Mon, 31 Jan 2022 at 13:52, Anton Khirnov wrote:
> With a separate build directory, I'm getting
> $ strings libavutil/x86/tx_float.o |grep asm
> src/libavutil/x86/tx_float.asm
>
The key piece is
../configure --disable-stripping
With stripping disabled and without the patch, you should see:
a
On Mon, 31 Jan 2022 at 13:52, Anton Khirnov wrote:
> > Are you using a separate build directory? This is a sample
> reproducibility
> > failure we've observed:
> >
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220118-y69m0ean/packages/diff-html/
>
> With a separate build directo
Ping :-)
Alex
On Tue, 18 Jan 2022 at 23:06, Alexander Kanavin
wrote:
> From: Alexander Kanavin
>
> Otherwise nasm writes the full host-specific paths into .o
> output, which breaks binary reproducibility.
>
> Signed-off-by: Alexander Kanavin
> ---
> libavuti
On Tue, 18 Jan 2022 at 23:32, Lynne wrote:
>
> Not what I'm seeing here in the binaries: "libavutil/x86/tx_float.asm",
> rather than a full path.
>
Are you using a separate build directory? This is a sample reproducibility
failure we've observed:
https://autobuilder.yocto.io/pub/repro-fail/oe-re
From: Alexander Kanavin
Otherwise nasm writes the full host-specific paths into .o
output, which breaks binary reproducibility.
Signed-off-by: Alexander Kanavin
---
libavutil/x86/cpuid.asm | 2 +-
libavutil/x86/emms.asm | 2 +-
libavutil/x86/fixed_dsp.asm | 2 +-
libavutil/x86
