| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
| From: | "Ben Wing" <ben AT 666 DOT com> |
| To: | <cygwin AT cygwin DOT com> |
| Subject: | Weird interaction between Visual C++ and Cygwin |
| Date: | Thu, 9 Dec 2004 21:09:00 -0600 |
| Message-ID: | <00c701c4de65$98db5270$210110ac@NEEEEEEE> |
| MIME-Version: | 1.0 |
If any Cygwin program is running, e.g. a compilation, Visual C++ takes an incredibly long time to start up. This has been the case for me for years. Does anyone know if there is some sort of locking contention here? -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |