From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/matchbox-desktop: needs -ldl
Date: Sun, 8 Dec 2019 15:47:09 +0100 [thread overview]
Message-ID: <20191208154709.5f81511e@windsurf.home> (raw)
In-Reply-To: <CAPi7W83SQuDc_Adb00z0cpGrG-VM68MWkXaakxwsmEujfGTVKw@mail.gmail.com>
On Wed, 20 Nov 2019 20:06:12 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> > I'd like to understand what is really going on here, because there are
> > build more recent than this one, which do build successfully:
> > http://autobuild.buildroot.org/results/c9c/c9c02c2c6d29f447c82adf9c05c141f288de1754/
> >
> > So definitely, the autoreconf does work in some cases.
> >
> > So, can we identify the reason it fails in some caes and not in others?
> Build failures started on October 22nd so perhaps this issue is also
> linked to commit 9cc8680fe54c0b8f5008158e36e2157127f03a7e.
> There is already discussions ongoing about if for gmpc that missed -lm
> (https://patchwork.ozlabs.org/patch/1186343/) and libv4l that missed
> -latomic (https://patchwork.ozlabs.org/patch/1186541).
I did a test, and I can confirm that
http://patchwork.ozlabs.org/patch/1204728/ fixes the matchbox-desktop
build issue, and makes this patch not needed.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-08 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 9:22 [Buildroot] [PATCH 1/2] package/matchbox-desktop: remove unrecognized option Fabrice Fontaine
2019-10-30 9:22 ` [Buildroot] [PATCH 2/2] package/matchbox-desktop: needs -ldl Fabrice Fontaine
2019-11-20 18:23 ` Yann E. MORIN
2019-11-20 19:06 ` Fabrice Fontaine
2019-12-08 14:47 ` Thomas Petazzoni [this message]
2019-12-08 13:42 ` [Buildroot] [PATCH 1/2] package/matchbox-desktop: remove unrecognized option Thomas Petazzoni
2019-12-22 20:07 ` Peter Korsgaard
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=20191208154709.5f81511e@windsurf.home \
--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