cygport debug junk

cygport debug junk

[Andrew Schulman]

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

Thanks,
Andrew.

#
# cygport script for wbox
# by Andrew E. Schulman, 2012-07-18
#

DESCRIPTION="HTTP testing tool and configuration-less HTTP server"
HOMEPAGE="http://www.hping.org/wbox"
SRC_URI="http://www.hping.org/wbox/wbox-${PV}.tar.gz"

src_compile ()
{
    cd "${B}"
    lndirs
    cygmake
}

src_install ()
{
    cd "${B}"
    dobin wbox
    doman wbox.1.gz

    dodir /usr/share/doc/${PN}
    dosym ../Cygwin/${PN}.README /usr/share/doc/${PN}/README.Cygwin
}


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

Re: cygport debug junk

[Ken Brown]

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

Re: cygport debug junk

[Yaakov (Cygwin/X)]

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

Re: cygport debug junk

[Ken Brown]

On 7/18/2012 6:53 PM, Yaakov (Cygwin/X) wrote:
> 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.

Sorry, I didn't realize that.

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

I disabled it for my recent texlive release, simply because texlive is 
so huge already that I didn't want to add to it.  Do you think that was 
the wrong decision?

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

Re: cygport debug junk

[Yaakov (Cygwin/X)]

On 2012-07-18 20:26, Ken Brown wrote:
> On 7/18/2012 6:53 PM, Yaakov (Cygwin/X) wrote:
>> 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.
>
> I disabled it for my recent texlive release, simply because texlive is
> so huge already that I didn't want to add to it.  Do you think that was
> the wrong decision?

Note that only the core texlive package will have debuginfo; the 
texlive-collection-* packages are just data, so there won't be debuginfo 
information anyway (and cygport only tries to make a debuginfo package 
where the debuginfo actually exists).  And while the texlive source 
package is huge, the amount of compiled code therein is a small fraction 
of that, so I don't think the debuginfo package would be really all that 
large (especially relative to the entire size of TeX).

So I'd say next time you build texlive, go ahead and enable debuginfo, 
but don't feel that you have to rebuild texlive immediately because of it.


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

Re: cygport debug junk

[Andrew Schulman]

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

Sorry for the pejorative :)

> >> Is this a change that's been made recently in cygport?
> 
> http://cygwin.com/ml/cygwin-announce/2012-07/msg00000.html

OK, thanks for the clarification.  I'll go along with it.  So is it now expected
to upload a debuginfo package at every package update, along with the binary and
source packages?  For packages built with cygport, that is.

Thanks,
Andrew.


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

Re: cygport debug junk

[Andrew Schulman]

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

One disadvantage of this is that it makes the 'list' command less useful.  I
used to be able to copy the output of 'cygport list' and paste it directly into
the README.Cygwin file, which is supposed to include a file listing of the
binary package.  Now I have to edit the output to remove the debug files.

If the intent of 'list' is to show the contents of the binary package, then I
suggest that it automatically remove the debug files from the listing.

Thanks,
Andrew.


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

Re: cygport debug junk

[Yaakov (Cygwin/X)]

On 2012-07-19 12:29, Andrew Schulman wrote:
>> 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.
>
> One disadvantage of this is that it makes the 'list' command less useful.  I
> used to be able to copy the output of 'cygport list' and paste it directly into
> the README.Cygwin file, which is supposed to include a file listing of the
> binary package.  Now I have to edit the output to remove the debug files.
>
> If the intent of 'list' is to show the contents of the binary package, then I
> suggest that it automatically remove the debug files from the listing.

Good point; fixed in git master.


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