[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: False positive "doesn't match the target pattern" error

From: Alejandro Colomar
Subject: Re: False positive "doesn't match the target pattern" error
Date: Sat, 20 Aug 2022 17:35:55 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.1.2

Hi Dmitry,

On 8/20/22 17:32, Dmitry Goncharov wrote:
On Sat, Aug 20, 2022 at 5:52 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
I appreciate GNU Make normalize the path
by removing "./"

This is helpful in some cases, but I think it is a bad side-effect
in this case.

Is there a reason to treat './foo.x' as different from 'foo.x'?

I'd say there is: make(1) treats file names as text strings, not really file names, for most of its operations. As an example, foo/ and foo/. are different targets. I don't see why ./bar and bar should be the same. Consistency is essential; otherwise, what to expect? Why does make(1) need to special-case a leading ./ ?

If this is a bug, I can file for it.
Or, any workaround exists?

It is not clear what you need to achieve.
Can you use an explicit rule like
foo.x: foo.z
Do you need make to perform a directory search for foo.x and foo.z in
various directories? In this case i'd look for vpath.

regards, Dmitry



Alejandro Colomar

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]