This is the mail archive of the cygwin@cygwin.com 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]

strange behavior regarding new cygwin 1.3.3 and cmd.exe


I've been using a make replacement called Jam for a long long time under
cygwin.

I recently upgraded to everything bleeding edge as of tonight.

Now when i type jam, i get each instantiation of CL.EXE (the vc++ cmdline
compiler) and LINK.EXE (the vc++ linker) run with all its output in a brand new
cmd.exe window.  each CL.EXE and LINK.EXE invokation pops up a new cmd.exe
window and when the cmd stops executing, it closes that new window it just
popped up.

I'm using the cygiwn xfree xterm + exceed as my X server. yesterday and
before, when i typed jam, the CL.EXE and LINK.EXE output just came to the
xterm and it worked as expected. now this output to the cmd.exe window
makes looking at compiler errors impossible, and the effect just overall
very annoying since windows are popping up and dying very quickly.

below is the output from cygcheck -r -s -v

thanks for any help.

oh yah, since cygwin upgraded to vim6, ctags is gone. its no longer
included in the vim pkg. could ctags be added to the apps in conjunction
with vim6?


-- 
                                            _________________
                                            danny@ishiboo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.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]