From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: link to libatomic when it's present
Date: Sat, 29 Jan 2022 21:38:38 +0100
Message-ID: <164348871880.20480.15099605110318125468@lain.red.khirnov.net> (raw)
In-Reply-To: <70dfc200-6550-fcef-6d68-ade7e400b37a@comstyle.com>
Quoting Brad Smith (2022-01-29 19:15:46)
> On 1/29/2022 4:54 AM, Hendrik Leppkes wrote:
>
> > On Sat, Jan 29, 2022 at 5:45 AM Brad Smith
> > <brad-at-comstyle.com@ffmpeg.org> wrote:
> >> libatomic is dropped by --as-needed since it is not necessary.
> >>
> > Thats what this solution relies on, and thus there is no harm in adding it.
>
> But it doesn't work, and the generated pkg-config files are contaminated
> too. I'll just
> have to patch out this broken crap locally.
You have now twice disregarded someone explaining why the test first
check with -latomic and then without, then you call this code "broken
crap" without properly explaining what breaks and why.
Consider communicating better if you want people here to take you
seriously.
--
Anton Khirnov
_______________________________________________
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".
prev parent reply other threads:[~2022-01-29 20:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 11:54 Anton Khirnov
2022-01-19 12:34 ` James Almer
2022-01-19 12:37 ` Andreas Rheinhardt
2022-01-19 12:40 ` Anton Khirnov
2022-01-19 13:16 ` James Almer
2022-01-19 13:48 ` Anton Khirnov
2022-01-19 15:23 ` James Almer
2022-01-22 6:42 ` Brad Smith
2022-01-22 9:00 ` Hendrik Leppkes
2022-01-23 19:40 ` Brad Smith
2022-01-26 11:49 ` Anton Khirnov
2022-01-29 4:44 ` Brad Smith
2022-01-29 9:54 ` Hendrik Leppkes
2022-01-29 18:15 ` Brad Smith
2022-01-29 20:38 ` Anton Khirnov [this message]
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=164348871880.20480.15099605110318125468@lain.red.khirnov.net \
--to=anton@khirnov.net \
--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