All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] poppler: compile with -fpermissive to workaround code diagnostics errors on armv5
Date: Tue, 20 Aug 2019 09:53:11 -0700	[thread overview]
Message-ID: <CAMKF1sqqUo3haTA8RpCd+8bLb2rw2OKJjVVVPk+tbPhS--tDnA@mail.gmail.com> (raw)
In-Reply-To: <20190820164438.GB24268@localhost>

On Tue, Aug 20, 2019 at 9:44 AM Adrian Bunk <bunk@stusta.de> wrote:
>
> On Tue, Aug 20, 2019 at 09:30:36AM -0700, Khem Raj wrote:
> > On Tue, Aug 20, 2019 at 2:37 AM Hongxu Jia <hongxu.jia@windriver.com> wrote:
> > >
> > > Build on qemuarmv5 failed:
> > > ...
> > > |poppler-0.79.0/splash/SplashFont.h:69:36: error: passing '    const
> > > SplashCoord' {aka 'const FixedPoint'} as 'this' argument discards
> > > qualifiers [-fpermissive]
> > > ...
> >
> > I wonder why this warning only shows up for armv5 and not for other
> > arm subarches or
> > non-arm arches.
> >...
>
> https://gitlab.freedesktop.org/poppler/poppler/issues/821

I see. This makes sense now. I wonder if we should just disable the
support instead of keeping
it dragging along ?


  reply	other threads:[~2019-08-20 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20  9:36 [meta-oe][PATCH] poppler: compile with -fpermissive to workaround code diagnostics errors on armv5 Hongxu Jia
2019-08-20 16:30 ` Khem Raj
2019-08-20 16:44   ` Adrian Bunk
2019-08-20 16:53     ` Khem Raj [this message]
2019-08-20 20:11       ` Adrian Bunk
2019-08-21  1:27         ` Hongxu Jia

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=CAMKF1sqqUo3haTA8RpCd+8bLb2rw2OKJjVVVPk+tbPhS--tDnA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.