From: Brad Smith <brad-at-comstyle.com@ffmpeg.org>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, James Almer <jamrial@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH] configure: link to libatomic when it's present
Date: Sat, 22 Jan 2022 01:42:55 -0500
Message-ID: <e76d7b2b-a4f7-469d-7bab-7c20b7d0359c@comstyle.com> (raw)
In-Reply-To: <ec759668-0de2-1e6b-1b90-fe20841a36e6@gmail.com>
On 1/19/2022 10:23 AM, James Almer wrote:
> On 1/19/2022 10:48 AM, Anton Khirnov wrote:
>> C11 atomics in some configurations (e.g. 64bit operations on ppc64 with
>> GCC) require linking to libatomic.
>>
>> Fixes #9275
>> ---
>> configure | 25 ++++++++++++++++---------
>> 1 file changed, 16 insertions(+), 9 deletions(-)
>>
>> diff --git a/configure b/configure
>> index 1413122d87..3059c154df 100755
>> --- a/configure
>> +++ b/configure
>> @@ -3794,20 +3794,20 @@ cws2fws_extralibs="zlib_extralibs"
>> # libraries, in any order
>> avcodec_deps="avutil"
>> -avcodec_suggest="libm"
>> +avcodec_suggest="libm stdatomic"
>> avdevice_deps="avformat avcodec avutil"
>> -avdevice_suggest="libm"
>> +avdevice_suggest="libm stdatomic"
>> avfilter_deps="avutil"
>> -avfilter_suggest="libm"
>> +avfilter_suggest="libm stdatomic"
>> avformat_deps="avcodec avutil"
>> -avformat_suggest="libm network zlib"
>> -avutil_suggest="clock_gettime ffnvcodec libm libdrm libmfx opencl
>> user32 vaapi vulkan videotoolbox corefoundation corevideo coremedia
>> bcrypt"
>> +avformat_suggest="libm network zlib stdatomic"
>> +avutil_suggest="clock_gettime ffnvcodec libm libdrm libmfx opencl
>> user32 vaapi vulkan videotoolbox corefoundation corevideo coremedia
>> bcrypt stdatomic"
>> postproc_deps="avutil gpl"
>> -postproc_suggest="libm"
>> +postproc_suggest="libm stdatomic"
>> swresample_deps="avutil"
>> -swresample_suggest="libm libsoxr"
>> +swresample_suggest="libm libsoxr stdatomic"
>> swscale_deps="avutil"
>> -swscale_suggest="libm"
>> +swscale_suggest="libm stdatomic"
>> avcodec_extralibs="pthreads_extralibs iconv_extralibs
>> dxva2_extralibs"
>> avfilter_extralibs="pthreads_extralibs"
>> @@ -6324,7 +6324,14 @@ check_headers asm/types.h
>> # it seems there are versions of clang in some distros that try to
>> use the
>> # gcc headers, which explodes for stdatomic
>> # so we also check that atomics actually work here
>> -check_builtin stdatomic stdatomic.h "atomic_int foo, bar =
>> ATOMIC_VAR_INIT(-1); atomic_store(&foo, 0); foo += bar"
>> +#
>> +# some configurations also require linking to libatomic, so try
>> +# both with -latomic and without
>> +for LATOMIC in "-latomic" ""; do
>> + check_builtin stdatomic
>> stdatomic.h \
>> + "atomic_int foo, bar = ATOMIC_VAR_INIT(-1);
>> atomic_store(&foo, 0); foo += bar" \
>> + $LATOMIC && eval stdatomic_extralibs="\$LATOMIC" && break
>> +done
>
> LGTM now, thanks.
>
>> check_lib advapi32 "windows.h" RegCloseKey
>> -ladvapi32
>> check_lib bcrypt "windows.h bcrypt.h" BCryptGenRandom -lbcrypt &&
Wait, this should be checking without first then with, if the first test
without fails.
_______________________________________________
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".
next prev parent reply other threads:[~2022-01-22 6:43 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 [this message]
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
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=e76d7b2b-a4f7-469d-7bab-7c20b7d0359c@comstyle.com \
--to=brad-at-comstyle.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=jamrial@gmail.com \
/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