Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavutil: include assembly with full path from source root
Date: Tue, 18 Jan 2022 23:31:50 +0100 (CET)
Message-ID: <MtjJKpo--7-2@lynne.ee> (raw)
In-Reply-To: <20220118220629.2108825-1-alex@linutronix.de>

18 Jan 2022, 23:06 by alex.kanavin@gmail.com:

> From: Alexander Kanavin <alex.kanavin@gmail.com>
>
> Otherwise nasm writes the full host-specific paths into .o
> output, which breaks binary reproducibility.
>
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
>  libavutil/x86/cpuid.asm      | 2 +-
>  libavutil/x86/emms.asm       | 2 +-
>  libavutil/x86/fixed_dsp.asm  | 2 +-
>  libavutil/x86/float_dsp.asm  | 2 +-
>  libavutil/x86/lls.asm        | 2 +-
>  libavutil/x86/pixelutils.asm | 2 +-
>  libavutil/x86/tx_float.asm   | 2 +-
>  7 files changed, 7 insertions(+), 7 deletions(-)
>

Not what I'm seeing here in the binaries: "libavutil/x86/tx_float.asm",
rather than a full path.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-01-18 22:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 22:06 Alexander Kanavin
2022-01-18 22:31 ` Lynne [this message]
2022-01-18 22:38   ` Alexander Kanavin
2022-01-31 12:51     ` Anton Khirnov
2022-01-31 13:05       ` Alexander Kanavin
2022-01-31 13:29       ` Alexander Kanavin
2022-02-07 11:24         ` Alexander Kanavin
2022-02-08  9:52           ` Anton Khirnov
2022-01-26 11:42 ` Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MtjJKpo--7-2@lynne.ee \
    --to=dev@lynne.ee \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git