delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2019/03/27/17:01:41

X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=cABbIJFVzDGAm+tLGD31FW
TXeTc=; b=fmRqKHN30l8GT+OGK20yG84gVbrTigH0+iU/dxC1cUIql3bqbf+aVg
8ZATfMAuLSIUC9Sj8OfkImixjNudB+OTYOfqydIMmA6ted1mNZLbYSWVZSJlYv5r
mo65y/N6UoFFOwWiyC8cBU1Pp7LBvIkCWeuGiFu7TZMr9atXTVJZo=
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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_NUMSUBJECT,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=HX-Google-DKIM-Signature:reply-to, co, 2.9.9, Gratz
X-HELO: mail-it1-f179.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:content-transfer-encoding; bh=VCNis4T1wXQD8gyFI3Kaa6t5N3k+21E/ftkIRUgfFBE=; b=hbmp+bO4j5/gg7KlQMW9Lc1B69X0iEg87dNIksakDtLR/SwZ84ZfhFdoPVFJtIiYXn 1s1VHpAwxA07kHaGdLRA0/HupS8+MTjLnyYm8zd4suCM39D3yPjo6bRlSPBO5A4Fh9XN f3Ob7KAbd1mMNiHMNin01DW3detz9gAMUJuEo706qRHoWX8To/pRHlTdBGI1zhyRcOMD RrEE8osOfsXVN/XbR8Gdh3XQAdFqaknagB061Ek9MSYmEKMu6oFF6CdxEdP647asIqrx HcwJwAkFC7Bv4JcFvI7dHEHh1vGn337ip69H0kDSbXGjfwtnK4cFDsPwa+jFGoXjebbG hTaA==
MIME-Version: 1.0
References: <announce DOT 6264b24c-18bd-814e-16e9-1852f3433e98 AT towo DOT net> <87pnqq536x DOT fsf AT Rainer DOT invalid> <8bf901a3-5e61-fa65-651f-5bdb9dddba4b AT towo DOT net> <20190324181931 DOT GE3471 AT calimero DOT vinschen DOT de> <8b43cced-6c22-e9de-046d-0895d0bc4f81 AT towo DOT net> <87sgvarfgt DOT fsf AT Rainer DOT invalid> <fe281b79-3ba1-0352-b73e-ab858d068d30 AT towo DOT net> <87tvfoyrzx DOT fsf AT Rainer DOT invalid>
In-Reply-To: <87tvfoyrzx.fsf@Rainer.invalid>
Reply-To: noloader AT gmail DOT com
From: Jeffrey Walton <noloader AT gmail DOT 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 AT cygwin DOT com
X-IsSubscribed: yes
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x2RL1dZ2025633

On Wed, Mar 27, 2019 at 4:36 PM Achim Gratz <Stromeko AT nexgo DOT 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


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019