All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: poky@lists.yoctoproject.org,
	andriy.danylovskyy@streamunlimited.com,
	 radek.dostal@streamunlimited.com
Subject: Re: [poky] [BUG] icecc breaks gobject-introspection do_compile on 2.7.2 and master
Date: Mon, 9 Dec 2019 11:02:29 -0800	[thread overview]
Message-ID: <CAMKF1sp+rmXSrNqXD5k0Z1oC8rKtZA5xo9-OmJLYG2sS4SwWEg@mail.gmail.com> (raw)
In-Reply-To: <20191209104222.lddk55rzv6lrwlp4@qschulz>

/tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/g-ir-scanner-qemuwrapper
/tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/tools/g-ir-compiler
-o gir/cairo-1.0.typelib gir/cairo-1.0.gir --includedir
/tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/gir
--includedir /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/gobject-introspection-1.62.0/gir


try to run above cmd manually with some verbosity

On Mon, Dec 9, 2019 at 2:42 AM Quentin Schulz
<quentin.schulz@streamunlimited.com> wrote:
>
> Hi Khem,
>
> On Fri, Dec 06, 2019 at 11:25:52AM -0800, Khem Raj wrote:
> > On Fri, Dec 6, 2019 at 2:18 AM Quentin Schulz
> > <quentin.schulz@streamunlimited.com> wrote:
> > >
> > > Hi all,
> > >
> > > I've *sometimes* encountered a build failure on gobject-introspection in
> > > warrior 2.7.2.
> > >
> > > Here is how to reproduce:
> > >
> > > git clone git://git.yoctoproject.org/poky
> > > cd poky
> > > git checkout 109ef2e5c4161a2c0ac58bede3daa48c7b4881ec #for master I tested or warrior-21.0.2
> > > source oe-init-build-env
> > > echo 'ICECC_PATH = "/usr/bin/icecc"' >> conf/local.conf
> > > echo 'INHERIT += "icecc"' >> conf/local.conf
> > > while true; do (bitbake gobject-introspection -c cleansstate && bitbake gobject-introspection -c compile) || break ; done
> > >
> > > Full log is attached, the interesting excerpt is here:
> > > [71/101] /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/g-ir-scanner-qemuwrapper /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/tools/g-ir-compiler -o gir/cairo-1.0.typelib gir/cairo-1.0.gir --includedir /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/gir --includedir /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/gobject-introspection-1.62.0/gir
> > > FAILED: gir/cairo-1.0.typelib
> > > /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/g-ir-scanner-qemuwrapper /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/tools/g-ir-compiler -o gir/cairo-1.0.typelib gir/cairo-1.0.gir --includedir /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/build/gir --includedir /tmp/poky/build/tmp/work/core2-64-poky-linux/gobject-introspection/1.62.0-r0/gobject-introspection-1.62.0/gir
> > > If the above error message is about missing .so libraries, then setting up GIR_EXTRA_LIBS_PATH in the recipe should help.
> > > (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
> > >
> >
> > if you look into logs a bit more then most probably
> > qemu-user is crashing.
> >
>
> I have attached the full Yocto do_compile log to the original mail, I
> don't see anything related to qemu-user.
>
> What do you mean with that sentence? Is there some other logs I could
> check?
>
> Thanks,
> Quentin

  reply	other threads:[~2019-12-09 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 10:18 [BUG] icecc breaks gobject-introspection do_compile on 2.7.2 and master Quentin Schulz
2019-12-06 19:25 ` [poky] " Khem Raj
2019-12-09 10:42   ` Quentin Schulz
2019-12-09 19:02     ` Khem Raj [this message]
2019-12-11 13:08       ` Quentin Schulz
2020-06-17  9:20       ` Quentin Schulz
     [not found]       ` <16194A529E0C724A.27738@lists.yoctoproject.org>
2020-06-17 10:06         ` [FIXED] " Quentin Schulz

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=CAMKF1sp+rmXSrNqXD5k0Z1oC8rKtZA5xo9-OmJLYG2sS4SwWEg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=andriy.danylovskyy@streamunlimited.com \
    --cc=poky@lists.yoctoproject.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=radek.dostal@streamunlimited.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.