mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alastair Houghton <ahoughton@apple.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] __MUSL__ macro
Date: Fri, 07 Jul 2023 14:14:30 +0100	[thread overview]
Message-ID: <054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com> (raw)
In-Reply-To: <20230707124722.GE4163@brightrain.aerifal.cx>

On 7 Jul 2023, at 13:47, Rich Felker <dalias@libc.org> wrote:
> 
> pthread_mutex_t is not a value type. It's an object. You cannot

[snip]

This is a somewhat irrelevant distraction and I rather wish I hadn’t mentioned that as an example of odd behaviour.  I’m well aware that you cannot copy or assign `pthread_mutex_t` values in general (and I understand the reasons why).

Please can we instead focus on the issue of whether or not musl should have `__MUSL__` and `__MUSL_MINOR__`.

Kind regards,

Alastair.


  reply	other threads:[~2023-07-07 13:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 10:48 Alastair Houghton
2023-07-06 12:17 ` Alex Xu
2023-07-06 16:26   ` Szabolcs Nagy
2023-07-07  7:14   ` Alastair Houghton
2023-07-07  7:30     ` A. Wilcox
2023-07-07  8:24       ` Alastair Houghton
2023-07-07 11:20     ` Laurent Bercot
2023-07-07 11:45     ` Jeffrey Walton
2023-07-07 13:53     ` Rich Felker
2023-07-07 14:18       ` Alastair Houghton
2023-07-07 12:47 ` Rich Felker
2023-07-07 13:14   ` Alastair Houghton [this message]
2023-07-07 14:19     ` Markus Wichmann
2023-07-07 14:26       ` Markus Wichmann
2023-07-07 14:46       ` Alastair Houghton
2023-07-07 15:02       ` Andrew Bell
2023-07-07 15:19         ` Markus Wichmann
2023-07-07 15:24           ` Andrew Bell
2023-07-07 15:34           ` Alastair Houghton
2023-07-07 15:45             ` Rich Felker
2023-07-07 15:58               ` Alastair Houghton
2023-07-07 15:05     ` i262jq

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=054B1907-817E-496D-9F83-7FBE7AB0111A@apple.com \
    --to=ahoughton@apple.com \
    --cc=dalias@libc.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).