X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.9 required=5.0	tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG
X-Spam-Check-By: sourceware.org
Message-ID: <505CA442.1060204@users.sourceforge.net>
Date: Fri, 21 Sep 2012 12:30:42 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport debuginfo extraction
References: <loom DOT 20120921T150134-858 AT post DOT gmane DOT org>
In-Reply-To: <loom.20120921T150134-858@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 2012-09-21 08:06, Achim Gratz wrote:
> I'm re-packaging the perl module DBI::Dumper as a Cygwin package for internal
> distribution and the debuginfo package is not produced.  This is because
> /usr/src/debug stays empty, while the .dll.dbg file is produced.  I can't figure
> out what's keeping the source information from being extracted, there are
> literally dozens of other perl module packages where this works correctly.

The C extension included in DBI::Dumper is precompiled by Inline::C 
rather than the usual MakeMaker-controlled XS->C->dll dance, so the 
usual means of getting debuginfo (via the OPTIMIZE Makefile variable) 
doesn't work.  AFAICS the solution would have to be package-specific 
(although I'm not sure exactly how yet).  I wouldn't spend too much time 
trying to figure this one out though.

BTW, in the future (and this goes for everyone), if you have a question 
about cygport, it would be helpful if you attach the .cygport in 
question, even if it's not perfect, so I don't have to recreate it myself.


Yaakov


--
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