Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Brad Smith <brad-at-comstyle.com@ffmpeg.org>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel] [PATCH] lavu/thread: add support for setting thread name on *bsd and solaris
Date: Mon, 8 Jan 2024 23:51:56 -0500
Message-ID: <9110236d-2bdb-4d5e-ab55-c8b243e5c885@comstyle.com> (raw)
In-Reply-To: <20240106172734.GH6420@pb2>

On 2024-01-06 12:27 p.m., Michael Niedermayer wrote:
> On Wed, Jan 03, 2024 at 11:19:56PM -0500, Brad Smith wrote:
>> lavu/thread: add support for setting thread name on *bsd and solaris
>>
>> FreeBSD/DragonFly/Solaris use pthread_setname_np(). OpenBSD uses pthread_set_name_np().
>>
>> Signed-off-by: Brad Smith <brad@comstyle.com>
>> ---
>>   configure          | 10 ++++++++++
>>   libavutil/thread.h | 14 ++++++++++++--
>>   2 files changed, 22 insertions(+), 2 deletions(-)
> this breaks build on linux
>
>   ./configure --enable-pthreads
> ERROR: pthreads requested but not found
>
> If you think configure made a mistake, make sure you are using the latest
> version from Git.  If the latest version fails, report the problem to the
> ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
> Include the log file "ffbuild/config.log" produced by configure as this will help
> solve the problem.

Sent a v2 diff.
_______________________________________________
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:[~2024-01-09  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  4:19 Brad Smith
2024-01-06 17:27 ` Michael Niedermayer
2024-01-09  4:51   ` Brad Smith [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=9110236d-2bdb-4d5e-ab55-c8b243e5c885@comstyle.com \
    --to=brad-at-comstyle.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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