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: Compilation errors not shown properly in Cygwin


At 05:22 PM 8/20/2004, you wrote:

>"Rajagopalan, Karthik" wrote:
>[...]
>> I am
>> trying to compile a C program through "Makefile" from Cygwin. This C
>> program has syntax errors which are supposed to be shown by Cygwin when
>> running  C compiler. It just indicates the following lines and stops :
>> 
>> make: *** [/cygdrive/h/test.obj] Error 1
>> 
>> If I run the C program without using "Makefile" from Cygwin, errors are
>> properly indicated.
>[...]

<snip>


>Steps to reproduce:
>- Unpack attached tgz
>- Make sure that directory with 'msdev.exe' from Visual C++ 6.0 is in
>  your PATH (usually
>  c:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\)
>- start bash in normal windows console (NOT rxvt)
>- cd to MakeTest directory
>- type 'make all'
>
>Output will NOT contain messages from msdev:
>> $ make all
>> msdev MakeTest.dsp /MAKE "MakeTest - Win32 Debug"
>> make: *** [all] Error 1
>
>- type 'make betterall'
>
>Output WILL contain messages from msdev:
>> $ make betterall
>> bash -c '{ msdev MakeTest.dsp /MAKE "MakeTest - Win32 Debug" | cat; [ "${PIPESTATUS[0]}" = 0 ]; }'
>> --------------------Configuration: MakeTest - Win32 Debug--------------------
>> Compiling...
>> MakeTest.cpp
>> d:\Sources\MakeTest\MakeTest.cpp(6) : error C2059: syntax error : '}'
>> d:\Sources\MakeTest\MakeTest.cpp(6) : warning C4508: 'main' : function should return a value; 'void' return type assumed
>> Error executing cl.exe.
>> 
>> MakeTest.exe - 1 error(s), 1 warning(s)
>
>
>I've encountered this problem long long time ago, so it's not some
>recent regression.
>
>Both invocations of msdev from Makefile display messages correctly under
>rxvt console.


Sounds like a tty thing to me.  Try adding to your CYGWIN environment 
variable 'notty' and starting a new cygwin.bat.


<snip>


>BTW: Shouldn't Cygwin and/or bash give preference to *.com over *.exe as
>windows' cmd does? Currently if you have t.exe and t.com in some
>directory in your path and you'll type 't' in shell then cygwin will
>start t.exe, and windows' cmd will start t.com.


We have our own anachronisms that we'd like to jettison.  Running 't.exe' 
when 't' is typed in is one of them.  I can't see adding to the list.  And 
changing now comes with a host of problems.  If we're ready to deal with the 
onslaught of problems such a change would make, it makes sense to get rid
of all anachronisms in this area rather than add one.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


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