All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] modemmanager: Use a simpler workaround for the clang build
Date: Tue, 6 Aug 2019 21:37:50 +0300	[thread overview]
Message-ID: <20190806183750.GA26061@localhost> (raw)
In-Reply-To: <CAMKF1srCPKCXiAVqBcZWXPytw7dLgPVED-deVbHRrHABbGcTxg@mail.gmail.com>

On Tue, Aug 06, 2019 at 11:09:50AM -0700, Khem Raj wrote:
> On Tue, Aug 6, 2019 at 8:39 AM Adrian Bunk <bunk@stusta.de> wrote:
>...
> > @@ -33,7 +32,7 @@ PACKAGECONFIG[qmi] = "--with-qmi,--without-qmi,libqmi"
> >  EXTRA_OECONF = " \
> >      --with-udev-base-dir=${nonarch_base_libdir}/udev \
> >  "
> > -CFLAGS_append_toolchain-gcc = " -Wno-unused-but-set-variable"
> > +EXTRA_OECONF_append_toolchain-clang = " --enable-more-warnings=no"
> >
> 
> I think this will disable extra warnings but since the patch was
> anyway doing same although just for one warning
> this is fine by me.

And it's only for clang.

> I still would like to have an option to be able to
> build with default warning set and have easy way for OE devs to
> fix/report such issues to package upstream instead of masking them
> out.

If someone wants to fix or report warnings upstream, then a stable 
release that might be years behind upstream master is usually not
a good starting point - when you are upstream in OE you are also
not very enthusiastic when people send patches for Yocto 2.0 today.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      reply	other threads:[~2019-08-06 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 15:39 [meta-oe][PATCH] modemmanager: Use a simpler workaround for the clang build Adrian Bunk
2019-08-06 18:09 ` Khem Raj
2019-08-06 18:37   ` Adrian Bunk [this message]

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=20190806183750.GA26061@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.