X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.2 required=5.0	tests=AWL,BAYES_00,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: <50073E51.1090709@users.sourceforge.net>
Date: Wed, 18 Jul 2012 17:53:05 -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 debug junk
References: <vl4e081f8uq3o891d33jvli21hke0q3sfk AT 4ax DOT com> <50073394 DOT 8040901 AT cornell DOT edu>
In-Reply-To: <50073394.8040901@cornell.edu>
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-07-18 17:07, Ken Brown wrote:
> On 7/18/2012 4:57 PM, Andrew Schulman wrote:
>> My cygport is 0.10.11-1.  I haven't run cygport in a while, and now
>> I'm trying
>> to compile a new package.  When I do, by default it seems that I get
>>
>> CC = "gcc -c -ggdb -O2 -pipe
>> -fdebug-prefix-map=/home/ASchulma/dev/cygwin/wbox/wbox-5-1/build=/usr/src/debug/wbox-5-1\
>>
>> -fdebug-prefix-map=/home/ASchulma/dev/cygwin/wbox/wbox-5-1/src/wbox-5=/usr/src/debug/wbox-5-1"
>>
>> and the install target then creates a bunch of (IMO) debug junk in
>> /usr/lib/debug and /usr/src/debug.

Debuginfo is not "junk".  Like most Linux binary distros, these files 
are automatically packed into a ${PN}-debuginfo package and excluded 
from other (sub)packages without further intervention by the maintainer. 
  Users can then install gdb and these debuginfo packages to debug 
software in place, without having to install BRs and rebuild packages.

>> Is this a change that's been made recently in cygport?

http://cygwin.com/ml/cygwin-announce/2012-07/msg00000.html

>> Can it be easily turned off?

Yes, it can, as described in the manual, but the only time you should is 
if you are trying to debug a package in its build-tree (e.g. noinst 
test/example apps), and then only temporarily, e.g.:

RESTRICT=debuginfo cygport foo-1.2.3-1 build

>> I grepped through /usr/share/cygport for that, and found that
>> compilers.cygclass uses it, but I don't include that in my cygport script
>> (below).

You mean compilers.cygpart; .cygpart files are just the main cygport 
script functions broken up into manageable sections, like .c files which 
are compiled into an executable.  .cygclass files are optional "modules" 
which are imported with inherit().

> It's been discussed quite a bit on cygwin-apps.  See, for instance, the
> thread starting at
> http://cygwin.com/ml/cygwin-apps/2012-06/msg00071.html and continuing
> into July.  If you don't want to provide a debuginfo package, put
> "_CYGPORT_RESTRICT_debuginfo_=1" in your .cygport file.

Bzzzt.  Don't use internal structures.  If it's not documented in the 
manual, you shouldn't be using it in your .cygport, and anything 
starting with an underscore is purely internal.

But again, while I can't state this as policy, you really shouldn't be 
disabling debuginfo on a widespread or permanent basis.  It's a feature 
and it's there for a reason.


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