Re: It's back -- "gcc: error: spawn: No such file or directory"

> From: "Larry Hall (Cygwin)" > Sent: Monday, June 2, 2014 12:33:44 PM > Subject: Re: It's back -- "gcc: error: spawn: No such file or directory" > On 06/02/2014 12:28 PM, David Friedman wrote: > >> as -v -o /cygdrive/c/DOCUME~1/friedman/LOC

Re: It's back -- "gcc: error: spawn: No such file or directory"

OK, that makes sense. So what I should do is run gcc with the -v option to see what it's trying to spawn (I recall that in a previous thread for this error, it was something called cc1). Here's the last few lines of the result, keeping my normal PATH: GNU C (GCC) version 4.8.3 (i686-pc-cygwin)

Re: It's back -- "gcc: error: spawn: No such file or directory"

le 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). David Friedman (re

Re: It's back -- "gcc: error: spawn: No such file or directory"

On Fri, 30 May 2014 12:51:18 -0400, Christopher Faylor wrote: > Try removing /bin from your path entirely. > cgf -- Tried it: set my path to just /usr/bin, and it still happens. dhf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Docume

It's back -- "gcc: error: spawn: No such file or directory"

I just upgraded my gcc to 4.8.3 and tried a compilation, and got the error above. I see that there's been some previous discussion of this error, including whether gcc is started from /usr/bin or /bin; tried both, no difference. See below: $ echo $PATH /usr/local/bin: /usr/bin: /bin: /usr/X11R6