cygport debug junk
Wed Jul 18 22:07:00 GMT 2012
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
> 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
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin