mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] glib: Patch glib-2.0.pc.in to use '-isystem dir' rather than '-Idir'
Date: Fri, 30 Oct 2015 11:45:39 -0400	[thread overview]
Message-ID: <CAMwGMjx4pYQ6ASiTMSsce0iVA18KDfrFMxG2NE_R9u3PFsaNJg@mail.gmail.com> (raw)
In-Reply-To: <20151030102228.GF32176@pengutronix.de>

On Fri, Oct 30, 2015 at 6:22 AM, Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
> On Fri, Oct 16, 2015 at 10:02:59AM -0400, Jon Ringle wrote:
>> Ping...
>>
>> On Sat, Oct 3, 2015 at 9:11 AM, Jon Ringle <jon@ringle.org> wrote:
>> > On Sat, Oct 3, 2015 at 4:56 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> >> On 10/03/2015 05:06 AM, jon@ringle.org wrote:
>> >>> From: Jon Ringle <jringle@gridpoint.com>
>> >>>
>> >>> When ptxdist did a bump to glib-2.44.0, a project that uses glib and builds
>> >>> with -Werror will fail.
>> >>>
>> >>> This patch will allow projects that use -Werror to continue to build without
>> >>> error.
>> >>>
>> >>> This patch was submitted upstream:
>> >>> https://bugzilla.gnome.org/show_bug.cgi?id=756005
>
> I agree with the comments on the bug report. Also, I don't think I've seen
> these warnings with other packages that use glib. What exactly are you
> doing to trigger these warning?

It seems that it is "-Werror -Wcast-qual" that triggers the error. I'm
sending a minimal ptxdist package that demonstrates the problem

-Jon

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-10-30 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03  3:06 jon
2015-10-03  8:56 ` Marc Kleine-Budde
2015-10-03 13:11   ` Jon Ringle
2015-10-16 14:02     ` Jon Ringle
2015-10-30 10:22       ` Michael Olbrich
2015-10-30 15:45         ` Jon Ringle [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=CAMwGMjx4pYQ6ASiTMSsce0iVA18KDfrFMxG2NE_R9u3PFsaNJg@mail.gmail.com \
    --to=jon@ringle.org \
    --cc=ptxdist@pengutronix.de \
    /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