public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: Ferenc Valenta <ferenc.valenta@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Make: Issue with $(MAKE) in make includes, when make is not on the default path
Date: Mon, 24 Oct 2022 11:36:35 +0200	[thread overview]
Message-ID: <CAB8Xom9uEac3ye4A5ESX3zRYaOQUgx=YOMubKaSQu+JNfJySdQ@mail.gmail.com> (raw)
In-Reply-To: <1b887e39-0f3c-9e8c-7baa-a0ed180b8307@gmail.com>

On Sun, Oct 23, 2022 at 7:27 PM Ferenc Valenta <ferenc.valenta@gmail.com> wrote:
>
>
> Hi,
>
> Just found a possible issue with Cygwin:
> If cygwin is not on the default path, and make is started by specyfing
> the path to it (e.g., c:\cygwin64\bin\make), $(MAKE) works in the
> top-level makefile, but it does not work in make includes.
> To reproduce the issue, use these files:
>
> makefile:
> $(info $(shell $(MAKE) --version))
> include test.mak
>
> test.mak:
> $(info $(shell $(MAKE) --version))
>
> Make sure that Cygwin is not on the default path, e.g. type *path ;* to
> erase the default path entirely.
> Then start make by specifying the path to it: c:\cygwin64\bin\make
>
> The first $(MAKE) call works, the second one does not.
> If make is on the default path, both work.
>
> Best regards,
>
> --
> Ferenc Valenta / System Architect / Mentor Graphics Deutschland
>

Hi Ferenc,

I doubt this should be considered a specific Cygwin bug or a bug at all

Marco

  reply	other threads:[~2022-10-24  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 17:26 Ferenc Valenta
2022-10-24  9:36 ` marco atzeri [this message]
2022-10-24 11:21   ` Thomas Wolff

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='CAB8Xom9uEac3ye4A5ESX3zRYaOQUgx=YOMubKaSQu+JNfJySdQ@mail.gmail.com' \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=ferenc.valenta@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.
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).