X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <50073394.8040901@cornell.edu> Date: Wed, 18 Jul 2012 18:07:16 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygport debug junk References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown AT cornell DOT edu - Wed Jul 18 18:07:22 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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 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. > > Try as I might, I can't seem to get rid of all of that stuff. I've tried > forcing CC=gcc in the Makefile, and some other things, but I can't seem to get > rid of all of the debug products. It's nothing having to do with the Makefile, > which is simple and doesn't include any -ggdb etc. > > Is this a change that's been made recently in cygport? Can it be easily turned > off? Or, could someone suggest where '-ggdb -O2 -pipe' etc might be coming > from? 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). 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. Ken -- 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