X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <472F7034.4070708@etr-usa.com> Date: Mon, 05 Nov 2007 12:34:12 -0700 From: Warren Young User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Cygwin-L Subject: Re: Wish Setup would accept my Perl References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Michael Kairys wrote: > I wish Setup could recognize that I already have a Perl installation... The two may be compatible at the Perl source level, for the most part[*], but I doubt they're binary compatible. A lot of Perl modules contain parts compiled from C and linked into the interpreter dynamically at need. Unless you can mix these modules, I don't think you can expect Cygwin to consider ActiveState's distribution compatible. If a Cygwin package needs Perl, it's fair for setup.exe to demand a Cygwinnish Perl to support it. For all setup.exe knows, it's an absolute requirement. [*] I also doubt they're 100% compatible at the source level, what with the various extensions each could be enabling that the other doesn't. -- 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/