From: Jon Turney <jon.turney@dronecode.org.uk>
To: Ronald Hoogenboom <RHoogenboom@irdeto.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: makedepend does not honor UNC path for -I and -Y
Date: Sun, 6 Feb 2022 16:47:56 +0000 [thread overview]
Message-ID: <52f465fd-1e35-4205-81b7-8a362b771c90@dronecode.org.uk> (raw)
In-Reply-To: <AS4PR07MB852964A556F11077692DA09BCD279@AS4PR07MB8529.eurprd07.prod.outlook.com>
On 02/02/2022 17:02, Ronald Hoogenboom wrote:
> cygwin makedepend collapses the double-slash UNC path prefix to one single slash. It fails to find headers via such search paths.
>
> Cygwin 3.2.0-1 on windows server 2012 R2
> makedepend 1.0.6
Thanks for reporting this.
I suspect that this is an upstream bug in makedepend, in that it does
some canonicalization on paths, and assumes that '//' is the same as '/'
everywhere in a path, which isn't true for an initial '//' (but happens
to work on Linux, etc.)
See SUSv4 Base specifications, section 4.13 "Pathname Resolution" ([1],
registration required):
"If a pathname begins with two successive <slash> characters, the first
component following the leading <slash> characters may be interpreted in
an implementation-defined manner, although more than two leading <slash>
characters shall be treated as a single <slash> character."
Unfortunately, you're probably going to have to fix this yourself, if
it's causing you problems.
Fortunately, makedepend is relatively small (See [2]).
[1]
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13
[2] https://gitlab.freedesktop.org/xorg/util/makedepend
next prev parent reply other threads:[~2022-02-06 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 17:02 Ronald Hoogenboom
2022-02-06 16:47 ` Jon Turney [this message]
2022-02-07 8:59 ` Ronald Hoogenboom
2022-02-08 13:27 ` Jon Turney
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=52f465fd-1e35-4205-81b7-8a362b771c90@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=RHoogenboom@irdeto.com \
--cc=cygwin@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).