This is the mail archive of the
mailing list for the Cygwin project.
Re: another "C compiler cannot create executables"
- From: Randall R Schulz <rrschulz at cris dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 17 Aug 2002 13:55:58 -0700
- Subject: Re: another "C compiler cannot create executables"
"As" is the assembler. It's part of the "binutils" package. If you don't
have "as," it's probably because you didn't select the "binutils" package
It has been a common design element in Unix compilers for decades for the
code generator to produce assembly, not machine code. Then a separate pass
by the assembler produces object code.
When in doubt about missing tools, go here: <http://cygwin.com/packages/>
to check which package contains a particular binary. Unfortunately, with a
name as short as "as," you get many spurious hits. In this case, the
summary text for each package in the listing might be a better source of
The GNU assembler, linker and binary utilities
Mountain View, CA USA
At 12:25 2002-08-17, Fernando Martins wrote:
I've the same symptom as Piyush Kacha but the cause seems different:
configure:2422: checking for C compiler default output
configure:2425: gcc -D_WIN32 conftest.c >&5
gcc: installation problem, cannot exec `as': No such file or directory
configure:2428: $? = 1
configure: failed program was:
What's 'as'? Doesn't seem to be a package. What can I do?
Maybe related, the previous version of gcc (2.95.3-5) was GPFing (for
unknown reason to me) and that's why I upgraded.
Any help appreciated,
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html