From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: It's back -- "gcc: error: spawn: No such file or directory"
Date: Mon, 02 Jun 2014 15:41:00 -0000 [thread overview]
Message-ID: <538C9B32.3060503@cygwin.com> (raw)
In-Reply-To: <2050638672.499354.1401722628618.JavaMail.zimbra@coherentlogix.com>
On 06/02/2014 11:23 AM, David Friedman wrote:
> Tried that too (set PATH to just /bin) - same result.
>
> Where is spawn normally located? Is it possible that the library file
> that normally contains it is actually missing, mis-located or corrupted, so that
> spawn can't be found? Is there a workaround, possibly involving fork() and
> exec()? I gather that spawn() is not POSIX-compliant (CMIIW - correct me if
> I'm wrong).
You're misinterpreting the error message (it's a common problem with the
way the error messages are constructed). spawn is not missing. It's the
context. Whatever 'gcc' is trying to spawn is the thing it cannot find.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
next prev parent reply other threads:[~2014-06-02 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401720184.12213.ezmlm@cygwin.com>
2014-06-02 15:23 ` David Friedman
2014-06-02 15:41 ` Larry Hall (Cygwin) [this message]
[not found] <1244589943.501250.1401725538999.JavaMail.zimbra@coherentlogix.com>
2014-06-02 16:28 ` David Friedman
2014-06-02 17:33 ` Larry Hall (Cygwin)
2014-06-02 19:19 ` David Friedman
2014-06-02 20:08 ` Larry Hall (Cygwin)
[not found] <598735007.458570.1401466053450.JavaMail.zimbra@coherentlogix.com>
2014-05-30 16:51 ` David Friedman
2014-05-30 18:27 ` Christopher Faylor
2014-05-31 19:15 ` Andrey Repin
2014-05-30 22:44 ` David Friedman
2014-05-31 0:01 ` Chris J. Breisch
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=538C9B32.3060503@cygwin.com \
--to=reply-to-list-only-lh@cygwin.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).