Sorry,
My colleague created this cygwinb19.dll as a copy from
cygwin1.dll.
Regards,
Jurgen
[EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
11/04/2003 09:14 AM
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject:cygwinb19.dll
Hello,
This is the first time I noticed, when I tried to copy cygwin1.dll,
using filename completion, I noticed that there is also a
cygwinb19.dll. Is this for backwards compatibility with
older programs ?
Regards,
Jurgen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On Thu, Sep 04, 2003 at 04:02:11PM +0200, jurgen.defurne wrote:
>Yes, Christopher, I know. I was just trying to get some more
>information or maybe a quick fix. In this case I think it is better
>that the more we know, the better we can defend ourselves against
>people who try make us pay license
successors.
Regards,
Jurgen
Christopher Faylor <[EMAIL PROTECTED]>
09/04/2003 03:50 PM
Please respond to cygwin
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject: Re: cygwinb19.dll
Classification:
On Thu, Sep 04, 2
On Thu, Sep 04, 2003 at 01:33:00PM +0200, [EMAIL PROTECTED] wrote:
>Tornado II for VxWorks, the ccmips.exe compiler. But it could be that
>the problem lies in a different direction, because we stopped all
>cygwin processes, took the directories out of the path, and we still
>get an error.
If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Recompiling IS an option, since we do have the sources, but not
| really feasible, because the compiler must be the same across all
| worldwide sites. It does work on other workstations, though. The only
| difference is that
TECTED]
"[EMAIL PROTECTED]:CygWin" <[EMAIL PROTECTED]>
cc: Jurgen Defurne/BRG/CE/[EMAIL PROTECTED]
Subject: Re: cygwinb19.dll
Classification:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Nope, did not work either. Still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Nope, did not work either. Still waiting for info from someone more
| experienced.
The "definitive" solution is of course to recompile the app with latest
cygwin headers *and* dll.
You *should* have the sources anyway... (unl
: cygwinb19.dll
Classification:
We renamed the cygwinb19.dll to get it out of the way and copied
the new one into the directory. Now it works.
Jurgen
[EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
09/04/2003 11:15 AM
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen
We renamed the cygwinb19.dll to get it out of the way and copied
the new one into the directory. Now it works.
Jurgen
[EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
09/04/2003 11:15 AM
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS
Lapo Luchini wrote:
> Let's just say that version b19 is "very very very very old" and,
> indeed, obsolete...
> But anyway the new tools shouldn't have problems if a DLL *with a
> different name* is found in the system.
>
> BT:W notcie that my answer is not authoritative, only CGF and a few of
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| 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 ?
Let's
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
13 matches
Mail list logo
