This is the mail archive of the cygwin-apps@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]
Other format:	[Raw text]

Re: Can upset handle more than one prev: tag?

From: "Max Bowsher" <maxb at ukf dot net>
To: "Reini Urban" <rurban at x-ray dot at>,<cygwin-apps at cygwin dot com>
Date: Tue, 24 Aug 2004 21:43:33 +0100
Subject: Re: Can upset handle more than one prev: tag?
References: <901745662219.20040824153633@familiehaase.de> <20040824153714.GA10974@coe.casa.cgf.cx> <1131759122053.20040824192052@familiehaase.de> <412B924F.3080404@x-ray.at>

Reini Urban wrote:

Shouldn't we then provide a cygperl5_8.dll symlinked to cygperl5_8_5.dll
also (in linux fashion), and apps should link against cygperl5_8.dll
resp. a more generic libperl.dll.a then?
otherwise you'll have to recompile all dependent apps.

You are forgetting something. The Windows runtime linker (understandably) doesn't understand Cygwin symlinks. From what I've heard, perl tries to stay ABI-compatible throughout x.y.*, so the DLL should be named cygperl5_8.dll

Max.

Follow-Ups:
- Re: Can upset handle more than one prev: tag?
  - From: Reini Urban

References:
- Can upset handle more than one prev: tag?
  - From: Gerrit P. Haase
- Re: Can upset handle more than one prev: tag?
  - From: Christopher Faylor
- Re: Can upset handle more than one prev: tag?
  - From: Gerrit P. Haase
- Re: Can upset handle more than one prev: tag?
  - From: Reini Urban

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