DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=l5L4xlFYSZXg44loEbBJVfDWCPulYxH91M8EcO5lXlR
	SK51Y2ab9lwVxC0r49rxuW7DhuajBw1gNhgznK4LGWjC0cpNYDWmwO1JvIpicfVu
	rwI1NiVLUjUFP9rs2vW1sUn3lkPi3PRmhz9OVOW2H3gLA6Wu4axqVHtgnYzbGgCw
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <515A2D12.7070303@gmail.com>
Date: Tue, 02 Apr 2013 01:57:54 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: cygport debuginfo problem: packaging fails.
References: <51594BDA DOT 8070600 AT gmail DOT com>
In-Reply-To: <51594BDA.8070600@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 01/04/2013 09:56, Dave Korn wrote:
>     Hi Yaakov et al.,
> 
>   I'm confused by the output from cygport (0.11.3) when building GCC.  During
> the packaging step, after the final binary package from PKG_NAMES has been
> tarballed, I see:
> 
>> *** Info: No debug files, skipping debuginfo subpackage

  OK, so this means that ${D}/usr/src/debug does not exist, and that's because
nothing was installed there by __prepdebugsrc().  That has something to do
with the fact that none of my source files got listed in ${T}/.dbgsrc.out, and
I think that in turn is because objdumping the built exes doesn't reveal any
paths to source files that begin with '/usr/src/debug'.

  That seems to be because no -fdebug-prefix-map options got added during the
build stage.  Or rather, the options did get added, but that was before
/usr/bin/cygport included my .cygport script, which went and unset them again.
 I'm not sure why I originally included that any more, I left a comment about
how setting them in the environment "confuses auto-detection process during
gcc build stages", which isn't as clear as I now wish, so I guess I'll just
delete that bit and try again.  Looks like the problem is my fault, anyway;
pardon the noise.

    cheers,
      DaveK


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