X-Recipient:	archive-cygwin AT delorie DOT com
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
	:content-type:content-transfer-encoding; q=dns; s=default; b=J3P
	sKYNX5VQtgO+2TVJqG/vOMbNw3BNMPabfNg0XUiuH1VhRMHaC0Jz4cbmBxxdWewz
	J2dTiqnaV2cwVex8+mqcSSUT4UbKyBzOJvfmHDmlXAQaYf0kdHISm337m4oQu0vb
	OKwwLZpqZR/jpWYas9Fo+zd12C7mX/VGovNlVaHk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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
	:content-type:content-transfer-encoding; s=default; bh=5KYzEskIY
	bHjpwy73i0cuy/EZew=; b=MvAp9xDZju+iRyhMaWVFoWgp1uMehACfUMKqPdvSA
	Kh8B8Uo4Ga7FHJUjyPOn9Pv8aDhow9YLl10HYuLopv1Az4un4T8RWjEQXs5P+CIU
	krjkpv8D0BGeu5zqa+HyV6kwUdBU75RvH0d0APr0aHQ/TYx046D6sh7aokLYYrei
	XA=
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
X-Spam-SWARE-Status:	No, score=-4.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG autolearn=ham version=3.3.1
X-Received:	by 10.194.119.200 with SMTP id kw8mr14490473wjb.31.1364806454353; Mon, 01 Apr 2013 01:54:14 -0700 (PDT)
Message-ID:	<51594BDA.8070600@gmail.com>
Date:	Mon, 01 Apr 2013 09:56:58 +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:	cygport debuginfo problem: packaging fails.

    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
> 
>>>> Checking packages for missing or duplicate files
> *** Warning: Packages are missing files:
> -usr/lib/debug/usr/bin/c++-4.exe.dbg
> -usr/lib/debug/usr/bin/cpp-4.exe.dbg
> -usr/lib/debug/usr/bin/cygffi-4.dll.dbg
> -usr/lib/debug/usr/bin/cyggcc_s-1.dll.dbg

  I don't understand this.  First it's complaining that there aren't any debug
files, so it won't package them, but then they actually are there after all
and it complains they haven't been packaged.  That appears self-contradictory!

  Any idea what might be causing this?  Do I have to create -debuginfo
packages manually if I'm using the PKG_NAMES and (package)_CONTENTS variables?
 Or could it perhaps be because the PN package itself has no contents at all,
serving only as a dummy to draw in dependencies through the requires: line in
its setup.hint?  (In my cygport script, PKG_NAMES contains "${PN}" but there
is no ${PN}_CONTENTS defined anywhere.)

    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

- Raw text -