Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] modem-manager: build issue
Date: Wed, 18 Apr 2018 11:33:42 -0300 (BRT)	[thread overview]
Message-ID: <1730967127.450971.1524062022318.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <CAGm1_kusSpWv2dmQyzerpouB+LUvf84jZAi6rBMyZdieUUosow@mail.gmail.com>

> From: "Yegor Yefremov" <yegorslists@googlemail.com>
> To: "buildroot" <buildroot@buildroot.org>
> Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>, "Carlos Santos" <casantos@datacom.ind.br>, "Aleksander
> Morgado" <aleksander@aleksander.es>
> Sent: Wednesday, April 18, 2018 9:32:06 AM
> Subject: modem-manager: build issue

> Current mm 1.6.12 produces following errors both when compiling an ARM
> or MIPS target:
> 
>  CC       ModemManager-mm-base-modem.o
> mm-base-manager.c: In function ?handle_set_logging?:
> mm-base-manager.c:680:15: error: assignment from incompatible pointer
> type [-Werror=incompatible-pointer-types]
>     ctx->self = g_object_ref (manager);
>               ^
> mm-base-manager.c: In function ?handle_scan_devices?:
> mm-base-manager.c:736:15: error: assignment from incompatible pointer
> type [-Werror=incompatible-pointer-types]
>     ctx->self = g_object_ref (manager);
>               ^
> mm-device.c: In function ?mm_device_get_plugin?:
> mm-device.c:628:12: error: return from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>     return (self->priv->plugin ?
> 
> So far I've seen only one build failure in our autobuilders [0]. I can
> reproduce this error building mm 1.6.12 locally with my host GCC. But
> the master branch of mm compiles without any issue. We don't seem to
> be the only ones who is affected [1], [2].
> 
> Any ideas?
> 
> [0]
> http://autobuild.buildroot.net/results/5d9e299ff12726d07e8a584a213c1d2a2e419594/
> [1]
> https://fedorapeople.org/groups/risc-v/logs/ModemManager-1.6.12-3.fc28.src.rpm/build.log
> [2]
> https://www.linuxquestions.org/questions/slackware-14/slackware-from-scratch-and-x11-4175560702/page19.html
> 
> Yegor

I'm quite busy right now but will try to reproduce the error tonight.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.? ? Christopher Hitchens

  parent reply	other threads:[~2018-04-18 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 12:32 [Buildroot] modem-manager: build issue Yegor Yefremov
2018-04-18 13:30 ` Thomas Petazzoni
2018-04-18 13:36   ` Yegor Yefremov
2018-04-18 13:51     ` Thomas Petazzoni
2018-04-18 14:33 ` Carlos Santos [this message]
2018-04-20  3:23   ` Carlos Santos
2018-04-20  6:38     ` Thomas Petazzoni
2018-04-20  7:28       ` Yegor Yefremov
2018-05-21 11:45         ` [Buildroot] [PATCH] modem-manager: remove -Werror from CFLAGS Carlos Santos
2018-05-21 15:54           ` Peter Korsgaard
2018-05-21 21:13             ` Carlos Santos
2018-05-21 21:34               ` Peter Korsgaard
2018-05-21 21:17         ` [Buildroot] [PATCH v2] " Carlos Santos

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=1730967127.450971.1524062022318.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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