From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: How does make determine which shells to invoke when executing external commands?
Date: Thu, 06 Jun 2013 16:25:00 -0000 [thread overview]
Message-ID: <51B0B7E8.6000501@etr-usa.com> (raw)
In-Reply-To: <CAPzB_RxkcD1ypzHe8j9EZBfV96VSkd3=ce-dywSdzby+mWt6_A@mail.gmail.com>
On 6/5/2013 20:43, Hua Ai wrote:
> I thought this is a cygwin issue since windows
> commands were invoked.
Cygwin make should *always* be using /bin/sh to interpret commands,
unless you've overridden it with SHELL.
Type this into a Makefile:
all:
@echo Shell is $(SHELL)
Then say "make" in that directory. It should confirm my assertion.
If it tells you something different on a problem machine, say "make
--version" and verify that it says "Built for i686-pc-cygwin".
> We don't have MinGW, but we do have multiple versions of a software
> (development tools from Altera) installed on these computers, which
> all contains a copy of cygwin (different versions but all with make).
Are you *certain* Altera is shipping Cygwin GNU make and not MinGW make?
Either way, you're kind of in a bind.
If Altera is shipping MinGW GNU make, you have the conflict I originally
proposed.
If they are in fact shipping Cygwin, you have this problem:
http://www.cygwin.com/faq.html#faq.using.multiple-copies
(Items 4.19 through 4.23.)
> This makefile however was run from a standalone cygwin.
What does it say when you say "which make"?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2013-06-06 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 15:32 Hua Ai
2013-06-05 16:42 ` Warren Young
2013-06-06 2:43 ` Hua Ai
2013-06-06 10:35 ` Andrey Repin
2013-06-06 16:25 ` Warren Young [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=51B0B7E8.6000501@etr-usa.com \
--to=warren@etr-usa.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).