X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DONT_USE_RAW_EMAIL_IN_BODY,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100823140705.GG6726@calimero.vinschen.de> References: <1282535618.6888.51.camel@YAAKOV04> <20100823140705.GG6726@calimero.vinschen.de> Date: Mon, 23 Aug 2010 16:34:40 +0200 Message-ID: Subject: Re: perl: Net::DNS requires Win32::IPHelper From: Reini Urban To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 2010/8/23 Corinna Vinschen : > On Aug 23 15:36, Reini Urban wrote: >> 2010/8/23 Yaakov (Cygwin/X) : >> > Reini, >> > >> > The Net::DNS module, which you ship with perl, depends on perl-libwin32 >> > (packaged separately) and Win32::IPHelper, the latter of which depends >> > on Win32::API and enum modules. =A0Win32::API needs a custom typemap f= ile >> > in order to compile on Cygwin, which AFAICS should be: >> > >> > TYPEMAP >> > HINSTANCE =A0 T_PTR >> > LPCSTR =A0 =A0 =A0T_PV >> > LPCWSTR =A0 =A0 T_PV >> >> Oh my. Net::DNS depending on Win32::API is not really helpful. >> He already has a DNS.xs it would be easy to add the IPHelper stuff to th= is xs. >> perl-libwin32 is a bit fat for a perl require line, I'll see what I >> can do to remove this cyclic dependency. >> Net::DNS is only needed for the old CPAN::Reporter. >> The new CPAN::Reporter 2.0 will use Metabase and has a entirely >> different set of deps. > > Here's a question: > > Why does the Net::DNS module, which provides only a resolver API, depend > on a Win32-related package at all? =A0Cygwin 1.7 provides a BSD compatible > resolver API (res_init, res_query, etc) which should be used, just like > on Linux. =A0Does the module erroneously treat Cygwin as Windows target? > If so, that should be fixed. Sure. It's entirely stupid for Net::DNS to treat cygwin same as MSWin32. A good catch by Yaakov. Wonder why I never had any issue with that. I'll come up with a better cygwin resolver for Net::DNS, which does not need a slow and always broken Win32::API + Win32::IPHelper. Behind my proxy using Net::DNS::Resolver::UNIX on cygwin worked okay, but I'll test again at home and bump perl then. --=20 Reini Urban -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple