All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pango: fix ptest failed problem
Date: Wed, 3 Oct 2018 12:48:46 +0100	[thread overview]
Message-ID: <CAJTo0LbUR5vkvik6z9jeFvO-AQsfNwFEW+2sAa7N9E-NfrXqbQ@mail.gmail.com> (raw)
In-Reply-To: <59e55b7b641c4a19a258fedf95712464@XBOX02.axis.com>

An even simpler fix is to just remove --disable-debug.  We don't need
a build with ptest enabled to have *all* the debuggig enabled, and
it's always nice to have cast checks enabled (which --disable-debug
turns off).

Ross
On Mon, 1 Oct 2018 at 11:34, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:
>
> > -----Original Message-----
> > From: openembedded-core-bounces@lists.openembedded.org <openembedded-
> > core-bounces@lists.openembedded.org> On Behalf Of
> > changqing.li@windriver.com
> > Sent: den 30 september 2018 04:00
> > To: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH] pango: fix ptest failed problem
> >
> > From: Changqing Li <changqing.li@windriver.com>
> >
> > disable-debug will cause compiling with G_DISABLE_ASSERT, but ptest
> > need
> > it, so don't disable-debug when ptest is enabled.
> >
> > ptest fail error:
> >
> > Tests were compiled with G_DISABLE_ASSERT and are likely no-ops.
> > Aborting.
> > FAIL: pango/test-font.test (Child process exited with code 1)
> > Running test: pango/testboundaries_ucd.test
> > Tests were compiled with G_DISABLE_ASSERT and are likely no-ops.
> > Aborting.
> > FAIL: pango/testboundaries_ucd.test (Child process exited with code 1)
> > Running test: pango/testboundaries.test
> > Tests were compiled with G_DISABLE_ASSERT and are likely no-ops.
> > Aborting.
> > FAIL: pango/testboundaries.test (Child process exited with code 1)
> > Running test: pango/testattributes.test
> > Tests were compiled with G_DISABLE_ASSERT and are likely no-ops.
> > Aborting.
> >
> > Signed-off-by: Changqing Li <changqing.li@windriver.com>
> > ---
> >  meta/recipes-graphics/pango/pango_1.42.4.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-graphics/pango/pango_1.42.4.bb
> > b/meta/recipes-graphics/pango/pango_1.42.4.bb
> > index e73fd28..c680720 100644
> > --- a/meta/recipes-graphics/pango/pango_1.42.4.bb
> > +++ b/meta/recipes-graphics/pango/pango_1.42.4.bb
> > @@ -24,7 +24,7 @@ DEPENDS = "glib-2.0 glib-2.0-native fontconfig freetype virtual/libiconv cairo h
> >  PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}"
> >  PACKAGECONFIG[x11] = "--with-xft,--without-xft,virtual/libx11 libxft"
> >
> > -EXTRA_OECONF = "--disable-debug"
> > +EXTRA_OECONF = "${@bb.utils.contains('DISTRO_FEATURES', 'ptest',"","--disable-debug",d)}"
>
> The above can be written cleaner as:
>
> PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'ptest x11', d)}"
> PACKAGECONFIG[ptest] = "--enable-debug,--disable-debug"
> PACKAGECONFIG[x11] = "--with-xft,--without-xft,virtual/libx11 libxft"
>
> (I added the --enable-debug to the ptest PACKAGECONFIG for symmetry,
> even though I assume it is the default.)
>
> >  LEAD_SONAME = "libpango-1.0*"
> >  LIBV = "1.8.0"
> > --
> > 2.7.4
>
> //Peter
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


      reply	other threads:[~2018-10-03 11:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30  1:59 [PATCH] pango: fix ptest failed problem changqing.li
2018-10-01 10:33 ` Peter Kjellerstedt
2018-10-03 11:48   ` Burton, Ross [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=CAJTo0LbUR5vkvik6z9jeFvO-AQsfNwFEW+2sAa7N9E-NfrXqbQ@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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.