mailing list of musl libc
 help / color / mirror / code / Atom feed
From: NRK <>
Subject: Re: [musl] canonicalize_file_name(3)
Date: Fri, 19 Aug 2022 19:48:33 +0600	[thread overview]
Message-ID: <20220819134833.y4kzfrb6ukpnuhbc@gen2.localdomain> (raw)
In-Reply-To: <>

On Thu, Aug 18, 2022 at 07:30:10PM +0200, Alejandro Colomar wrote:
> It relies on a glibc extension to realpath(3)

What extension are we talking about exactly?
Because `man canonicalize_file_name` states the following:

| The call canonicalize_file_name(path) is equivalent to the call:
|          realpath(path, NULL);

Calling realpath with NULL as the 2nd parameter is well defined since
POSIX-2008 [0], if that's what you were talking about.



  reply	other threads:[~2022-08-19 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 17:30 Alejandro Colomar
2022-08-19 13:48 ` NRK [this message]
2022-08-19 17:10   ` Rich Felker

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220819134833.y4kzfrb6ukpnuhbc@gen2.localdomain \ \ \

* 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

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).