This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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)
        compiled by GNU C version 4.8.3, GMP version 6.0.0, MPFR version 3.1.2, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: a39cfdacc7868ff2412ca54ce8f22425
COLLECT_GCC_OPTIONS='-v' '-o' 'QC_enc_dec.exe' '-mtune=generic' '-march=i686'
 as -v -o /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/cc05Tigm.o /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/ccgnoAu9.s
GNU assembler version 2.23.2 (mingw32) using BFD version (GNU Binutils) 2.23.2
Assembler messages:
Fatal error: can't create /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/cc05Tigm.o: No such file or directory

Interestingly, the error message now is different. But with my PATH set to either just /bin or just /usr/bin I get this:

GNU C (GCC) version 4.8.3 (i686-pc-cygwin)
        compiled by GNU C version 4.8.3, GMP version 6.0.0, MPFR version 3.1.2, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: a39cfdacc7868ff2412ca54ce8f22425
COLLECT_GCC_OPTIONS='-v' '-o' 'QC_enc_dec.exe' '-mtune=generic' '-march=i686'
 as -v -o /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/ccASOmoc.o /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/ccGXQsYR.s
gcc: error: spawn: No such file or directory

Does "as" mean the assembler? If it's not in /bin or /usr/bin, where is it?

- dhf

----- Original Message -----
From: "Larry Hall (Cygwin)"

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

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]