Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] check-package: avoid false warning of useless flag
Date: Sat, 2 Dec 2017 14:54:43 +0100	[thread overview]
Message-ID: <20171202135443.GB2988@scaer> (raw)
In-Reply-To: <20171202141059.391df6c0@windsurf.lan>

Thomas, All,

On 2017-12-02 14:10 +0100, Thomas Petazzoni spake thusly:
> On Sat, 2 Dec 2017 12:03:20 +0100, Yann E. MORIN wrote:
> 
> > > Instead of increasing complexity of the script to fully detect this
> > > case, ignore the host flag set to its default value as it can be
> > > overriding a non-default value inherited from the equivalent target
> > > flag.  
> > 
> > But then we miss the cases where:
> >   - both are set to their default values,
> >   - the target one is not set and the host one is set to the default
> >     value.
> > 
> > But as you said, detecting the real false-positive would require
> > maintaining some state, which is currently not possible in the script.
> > 
> > Yet, htere is one issue I see: the script currently names issues mere
> > 'warnings' but exits with a non-zero error code as soon as at least one
> > such 'warning' is seen.
> > 
> > However, what we so far detected were really 'errors', not 'warnings',
> > while the case we are speaking about now really is a warning: it should
> > be reported, biut should not exit in error.
> 
> I'm not sure we want to go down this road, and distinguish warnings and
> errors. Either something is correct, or it's not. I prefer to have a
> clean and readable check-package output, with only things that really
> need to be fixed.

OK, but then with this change, we will now be missing actual errors,
e.g.:

    FOO_AUTORECONF = NO
    HOST_FOO_AUTORECONF = NO

Will not report the host vairant as bogus, even after the target variant
gets removed.

So we lose a false positive for a false negative.

I have to admit I am not sure which is worse/best...

Regards,
Yann E. MORIN.

> > Also I noticed that the comments do match the regexps:
> > 
> >     288: # We need HOST_ASTERISK_AUTORECONF = NO because the
> >     289: # target variant has _AUTORECONF = YES
> >     290: HOST_ASTERISK_AUTORECONF = NO
> > 
> > will report the issue twice (man URL removed):
> > 
> >     package/asterisk/asterisk.mk:288: useless default value [...]
> >     package/asterisk/asterisk.mk:290: useless default value [...]
> > 
> > Since this is the .mk parser, it could ignore the comments, I believe...
> 
> Agreed, but that's a separate issue :)
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-12-02 13:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 23:08 [Buildroot] [PATCH 0/8] Fix warnings reported by check-package Yann E. MORIN
2017-11-29 23:08 ` [Buildroot] [PATCH 1/8] package/lttng-tools: fix typo in variable name Yann E. MORIN
2017-11-30  7:58   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 2/8] package/checkpolicy: rename variable Yann E. MORIN
2017-12-01 21:55   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 3/8] package/am335x-pru-package: " Yann E. MORIN
2017-12-01 21:56   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 4/8] package/lockfile-progs: " Yann E. MORIN
2017-12-01 21:56   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 5/8] packages: remove "consecutive empty lines" Yann E. MORIN
2017-12-01 21:56   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 6/8] packages: fix trailing spaces and slash Yann E. MORIN
2017-12-01 21:57   ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 7/8] package/asterisk: add comment about a check-package false positive Yann E. MORIN
2017-11-30  8:00   ` Thomas Petazzoni
2017-11-30 11:19     ` Ricardo Martincoski
2017-11-30 12:57       ` Thomas Petazzoni
2017-12-01 22:00   ` Thomas Petazzoni
2017-12-02  4:28   ` [Buildroot] [PATCH 1/1] check-package: avoid false warning of useless flag Ricardo Martincoski
2017-12-02 11:03     ` Yann E. MORIN
2017-12-02 13:10       ` Thomas Petazzoni
2017-12-02 13:54         ` Yann E. MORIN [this message]
2017-12-02 14:08           ` Thomas Petazzoni
2017-12-03 17:48             ` Arnout Vandecappelle
2017-12-02 13:52     ` Thomas Petazzoni
2017-11-29 23:08 ` [Buildroot] [PATCH 8/8] gitlab-ci: run check-package Yann E. MORIN
2017-11-30  7:59   ` Thomas Petazzoni
2017-11-30 15:34     ` Yann E. MORIN
2017-12-01  9:54       ` Thomas Petazzoni
2017-12-01 15:23         ` Yann E. MORIN
2017-12-02  4:33       ` Ricardo Martincoski
2017-12-01 22:00   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171202135443.GB2988@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox