This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: It's back -- "gcc: error: spawn: No such file or directory"
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 02 Jun 2014 11:41:38 -0400
- Subject: Re: It's back -- "gcc: error: spawn: No such file or directory"
- Authentication-results: sourceware.org; auth=none
- References: <1401720184 dot 12213 dot ezmlm at cygwin dot com> <2050638672 dot 499354 dot 1401722628618 dot JavaMail dot zimbra at coherentlogix dot com>
- Reply-to: cygwin at cygwin dot 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