Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
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: Mon, 31 Jan 2022 14:05:57 +0100
Message-ID: <CANNYZj9ySjerpuyjLM36HFMFRcnTAf50mKUH6K3n53PfQcFi2g@mail.gmail.com> (raw)
In-Reply-To: <164363350306.23111.4039910706733379234@lain.red.khirnov.net>

On Mon, 31 Jan 2022 at 13:52, Anton Khirnov <anton@khirnov.net> 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 directory, I'm getting
> $ strings libavutil/x86/tx_float.o |grep asm
> src/libavutil/x86/tx_float.asm
>

Thanks, I'm trying to get it to reproduce outside of yocto - there's
something in that build environment that does cause .asm include filenames
to be written into the .o. Will write back when I have a reproducer.

Alex
_______________________________________________
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-31 13:06 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
2022-01-18 22:38   ` Alexander Kanavin
2022-01-31 12:51     ` Anton Khirnov
2022-01-31 13:05       ` Alexander Kanavin [this message]
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=CANNYZj9ySjerpuyjLM36HFMFRcnTAf50mKUH6K3n53PfQcFi2g@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --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