All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksander Morgado <aleksander@aleksander.es>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-12-09
Date: Tue, 10 Dec 2019 20:47:29 +0100	[thread overview]
Message-ID: <CAAP7ucKJ53nK=8gAzes-GB-C24dVOD+U7cokhTpzMyVhZo=80Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ4jsaceHWQxOBT=mCgLF1YFhp=BMjCJAs-Vnobs+=PSuAeFTw@mail.gmail.com>

Hey Carlos,

On Tue, 10 Dec 2019, 19:20 Carlos Santos, <unixmania@gmail.com> wrote:

> On Tue, Dec 10, 2019 at 4:18 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>
> >     arm      |      modem-manager-1.12.0      | NOK |
> http://autobuild.buildroot.net/results/0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a
> |
>
> This should have been solved by
>
>     https://patchwork.ozlabs.org/patch/1186596/
>
> which was left behind.
>
> Even with that patch applied it fails with...
>


Is there any way I can reproduce that build locally? Not sure how to
exactly reproduce the build with the same toolchain and build options.

Looks like the libmm-glib linker include isn't in the right place when
building some of the tools. I could probably send more patches attempting
to fix this, but I'd be much easier to reproduce locally.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191210/13c97fb3/attachment.html>

  reply	other threads:[~2019-12-10 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  7:18 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-12-09 Thomas Petazzoni
2019-12-10 18:20 ` Carlos Santos
2019-12-10 19:47   ` Aleksander Morgado [this message]
2019-12-10 20:26     ` Thomas Petazzoni
2019-12-11 15:06       ` Aleksander Morgado

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='CAAP7ucKJ53nK=8gAzes-GB-C24dVOD+U7cokhTpzMyVhZo=80Q@mail.gmail.com' \
    --to=aleksander@aleksander.es \
    --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 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.