This is the mail archive of the
mailing list for the Cygwin project.
RE: Problem with gcc
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 11 Jul 2006 11:17:20 +0100
- Subject: RE: Problem with gcc
On 11 July 2006 11:02, Guenther Sohler wrote:
> Hallo Dave,
> I already tried so, but I was not able to see the problem from the output.
> it is:
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/cc1.exe -quiet -v -D__GNUC__=3
> -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=3 -D__CYGWIN32__ -D__CYGWIN__
> -D__unix__ - D__unix -idirafter
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../include/w3api -idirafter
> lib/../../include/w32api a.c -quiet -dumpbase a.c -auxbase a -version -o
All looks sensible. Did the .s file get created? We can't be sure whether
/that/ command failed, or whether the next step failed before it even printed
out the command-line invocation (like perhaps because it couldn't find as).
> Documentation says, that -### does the same like -v but doesnt execute.
> -### displays even one more line, but obviously it does not create any
That makes sense; you're using -c, so it just generates the source file and
> So it seems, the last command noted does not work correctly, but no idea why
My first guess is that either gcc or binutils didn't install properly; you
could fix that by re-running setup.exe, making sure both gcc and binutils are
selected for 'reinstall', and try again.
If that isn't it, we'd need to check your overall installation. Run
"cygcheck -svr >cygcheck.out" in a bash shell, and send the resulting file -
as an *attachment*, please! - to the list.
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html