DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:reply-to
	:from:date:message-id:subject:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=rHBbP5GMH502PyRV
	F5k/JucPT286oqqfmKoIn/2UChwllxRleyokuVfJ6cMJeWcEg97BkWBvJn4/vJb+
	cLl1mAmgg93ISST68DIQOD9HrcmY6hA3p862I4F9xuW88nlQ0uxT3Z5z6uuuN+kQ
	PS4vZRECRcs7iLCg0S9Jca+mDDk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <announce.6264b24c-18bd-814e-16e9-1852f3433e98@towo.net> <87pnqq536x.fsf@Rainer.invalid> <8bf901a3-5e61-fa65-651f-5bdb9dddba4b@towo.net> <20190324181931.GE3471@calimero.vinschen.de> <8b43cced-6c22-e9de-046d-0895d0bc4f81@towo.net> <87sgvarfgt.fsf@Rainer.invalid> <fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net> <87tvfoyrzx.fsf@Rainer.invalid>
In-Reply-To: <87tvfoyrzx.fsf@Rainer.invalid>
Reply-To: noloader@gmail.com
From: Jeffrey Walton <noloader@gmail.com>
Date: Wed, 27 Mar 2019 17:00:57 -0400
Message-ID: <CAH8yC8=eU1X5NbDDBkOk74SOC8kNrTqHhQCxHoSeV3a17+D7ig@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Wed, Mar 27, 2019 at 4:36 PM Achim Gratz <Stromeko@nexgo.de> wrote:
> ...
> > I removed -s as suggested by Achim, added -g as advised by Corinna,
> > but cygport still says:
> > *** Info: No debug files, skipping debuginfo subpackage
>
> Well, do not reset CFLAGS in your Makefile and cygport helpfully
> provides all the scaffolding you need.  You might have noticed I
> replaced the ":=" in your Makefile for exactly that reason.  A build
> system is supposed to be able to pre-configure CFLAGS without your
> Makefile nixing all of that effort.

Also of interest is GNU Coding Standards, 7.2.3 Variables for
Specifying Commands
(https://www.gnu.org/prep/standards/html_node/Command-Variables.html):

If there are C compiler options that must be used for proper
compilation of certain files, do not include them in CFLAGS. Users
expect to be able to specify CFLAGS freely themselves. Instead,
arrange to pass the necessary options to the C compiler independently
of CFLAGS, by writing them explicitly in the compilation commands or
by defining an implicit rule, like this:

    CFLAGS = -g
    ALL_CFLAGS = -I. $(CFLAGS)
    .c.o:
            $(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $<

Do include the ‘-g’ option in CFLAGS, because that is not required for
proper compilation. You can consider it a default that is only
recommended. If the package is set up so that it is compiled with GCC
by default, then you might as well include ‘-O’ in the default value
of CFLAGS as well.

Put CFLAGS last in the compilation command, after other variables
containing compiler options, so the user can use CFLAGS to override
the others.

Jeff

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