mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com, Jeffrey Walton <noloader@gmail.com>
Subject: Re: [musl] sgetspent(3) on musl
Date: Fri, 23 May 2025 16:44:37 +0200	[thread overview]
Message-ID: <s367dsjxw56en35fnazi5g3g6hya7gzifikyntuua4m66ediyy@ulw5ynbrgi6f> (raw)
In-Reply-To: <20250523135402.GL1827@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi Rich,

On Fri, May 23, 2025 at 09:54:04AM -0400, Rich Felker wrote:
> > I'm coming back to this, because it's more problematic than I initially
> > thought.
> > 
> > In shadow, I have a function prototype *and* a function declaration for
> > this API (when compiling for musl; in glibc I rely on the libc one).
> > 
> > Now I was trying to enable -Werror=redundant-decls (among many other
> > errors), but my declaration is redundant with the musl one, and so I
> > can't enable this error.  Would you mind removing it from musl?
> > 
> > <https://github.com/shadow-maint/shadow/pull/1220#issuecomment-2676737629>
> 
> Sure thing. I have a patch, just not upstream. Will push it.

Thanks!

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2025-05-23 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 12:10 Alejandro Colomar
2024-11-29  6:11 ` Rich Felker
2024-11-29  6:35   ` Jeffrey Walton
2024-11-29 12:29     ` Alejandro Colomar
2024-11-29 12:22   ` Alejandro Colomar
     [not found]   ` <j4chwyy4onh2hs4yetqmy6fysovhrsxwdcn7svxdfuec5f6czv@3opbnluima4w>
     [not found]     ` <20250523135402.GL1827@brightrain.aerifal.cx>
2025-05-23 14:44       ` Alejandro Colomar [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=s367dsjxw56en35fnazi5g3g6hya7gzifikyntuua4m66ediyy@ulw5ynbrgi6f \
    --to=alx@kernel.org \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=noloader@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
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).