mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Érico Nogueira" <ericonr@disroot.org>
To: <musl@lists.openwall.com>
Subject: Re: [musl] pthread_getname_np implementation
Date: Sat, 19 Dec 2020 14:42:34 -0300	[thread overview]
Message-ID: <C7WY4MPG8WO8.17Y0KDPDWDLWH@mussels> (raw)
In-Reply-To: <741a27c05e04c27e2796abbe33fc22e5@schoepfer.info>

On Sat Dec 19, 2020 at 4:23 AM -03,  wrote:
> Hi all,
>
> i'm new to this list.
>
> I'm trying to compile qt5-5.15.2 with gcc10.2 and musl-1.2.1, and after
> some hours compiling i get:
>
> platform/default/thread.cpp: In function ‘std::string
> mbgl::platform::getCurrentThreadName()’:
> platform/default/thread.cpp:14:5: error: ‘pthread_getname_np’ was
> not
> declared in this scope; did you mean ‘pthread_setname_np’?
> 14 | pthread_getname_np(pthread_self(), name, sizeof(name));
> | ^~~~~~~~~~~~~~~~~~
> | pthread_setname_np
>
> I found this thread about musl/pthread_getname_np
> https://www.openwall.com/lists/musl/2019/07/09/2 ,
> which says
> "Based on the previous discussion of this and others' comments, I think
> adding it[pthread_getname_np] is probably the right thing to do. I'll
> look at it after
> rolling the release. Ping the list again if I don't get around to it
> soon."
> So here is the ping :-)
>
> If there's another way around to get qt5 to compile, that's of course
> also ok for me.

You can patch it out [1]

[1] https://github.com/void-linux/void-packages/blob/e64dd67f43c409d2b2db08214084e842d92ad620/srcpkgs/qt5/patches/0014-musl-set_thread_name_np.patch

Implementing it in musl shouldn't be terribly hard either, I think.

>
> Thanks,
>
> Johannes


  reply	other threads:[~2020-12-19 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  7:23 musl
2020-12-19 17:42 ` Érico Nogueira [this message]
2020-12-20 11:15   ` musl

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=C7WY4MPG8WO8.17Y0KDPDWDLWH@mussels \
    --to=ericonr@disroot.org \
    --cc=musl@lists.openwall.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).