From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [EXTERNAL] [autobuild.buildroot.net] Your build results for 2019-06-13
Date: Wed, 19 Jun 2019 08:48:51 +0200 [thread overview]
Message-ID: <20190619084851.5500ad30@windsurf> (raw)
In-Reply-To: <20190619061619.GC24143@tungsten.ozlabs.ibm.com>
Hello Sam,
On Wed, 19 Jun 2019 16:16:19 +1000
Sam Bobroff <sbobroff@linux.ibm.com> wrote:
> I tried to replicate the modem-manager build failure, but it succeeded
> (I'm using br-reproduce-build). The error is odd as well:
>
> make[4]: Entering directory '/home/buildroot/build/instance-0/output/build/modem-manager-1.10.0/libmm-glib/generated'
> GEN mm-enums-types.h
> GEN mm-errors-types.h
> GEN mm-gdbus-manager.c
> /bin/sh: line 1: /usr/bin/gdbus-codegen: No such file or directory
> GEN mm-gdbus-sim.c
> /bin/sh: line 1: /usr/bin/gdbus-codegen: No such file or directory
> GEN mm-gdbus-sms.c
> GEN mm-gdbus-call.c
> /bin/sh: line 1: /usr/bin/gdbus-codegen: No such file or directory
> Makefile:1173: recipe for target 'mm-gdbus-sim.c' failed
> make[4]: *** [mm-gdbus-sim.c] Error 127
> make[4]: *** Waiting for unfinished jobs....
> Makefile:1149: recipe for target 'mm-gdbus-manager.c' failed
> make[4]: *** [mm-gdbus-manager.c] Error 127
This issue is already fixed by
https://git.buildroot.org/buildroot/commit/?id=739c581663285db6efb3559969e9e04f873a38f7.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2019-06-19 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2t43n5cdd4-1@m0098420.ppops.net>
[not found] ` <20190619061619.GC24143@tungsten.ozlabs.ibm.com>
2019-06-19 6:48 ` Thomas Petazzoni [this message]
2019-06-20 0:19 ` [Buildroot] [EXTERNAL] [autobuild.buildroot.net] Your build results for 2019-06-13 Sam Bobroff
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=20190619084851.5500ad30@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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