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://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: | jurgen DOT defurne AT philips DOT com |
To: | cygwin AT cygwin DOT com |
Subject: | cygwinb19.dll |
MIME-Version: | 1.0 |
Message-ID: | <OFACDEA1F1.634A6952-ONC1256D97.00322748-C1256D97.0032FAEE@diamond.philips.com> |
Date: | Thu, 4 Sep 2003 11:15:08 +0200 |
Dear all, We have a product Tornado from WindRiver, which uses cygwinb19.dll. The Tornado compiler generates an access violation on the workstation which also happens to run a more recent version of Cygwin. This access violation takes place in the cygwinb19.dll. I happen to know from previous discussions that one should not have several versions of cygwin1.dll in his path. Does the same problem arise with one version of cygwinb19.dll and one version of cygwin1.dll ? Regards, Jurgen -- 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 |