Try removing /bin from your path entirely.
I'd rather suggest removing /usr/bin
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 31.05.2014, 22:59
_
Tried that too (set PATH to just /bin) - same result.
Where is spawn normally located? Is it possible that the library file that
normally
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
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)
On 06/02/2014 12:28 PM, David Friedman wrote:
snip
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
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:
snip
as -v -o /cygdrive/c/DOCUME~1/friedman/LOCALS~1/Temp/ccASOmoc.o
/cygdrive/c/DOCUME~1/friedman
On 06/02/2014 03:19 PM, David Friedman wrote:
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:
snip
as -v -o /cygdrive/c/DOCUME~1/friedman/LOCALS~1
Greetings, Christopher Faylor!
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
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:
On Fri, May 30, 2014 at 11:19:37AM -0500, David Friedman wrote:
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
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/
David Friedman wrote:
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
And you have tried gcc -v? Or even gcc -v -Wl,--verbose, to see what
it's
11 matches
Mail list logo
