From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/wayland: bump to version 1.18.0
Date: Tue, 28 Apr 2020 07:24:38 +0200 [thread overview]
Message-ID: <20200428072438.2f7f2b0e@windsurf.home> (raw)
In-Reply-To: <CADvTj4qqBC9QMqyxvKKVO0+yn7CsG36hSqvf1vu7CEzshaJe2Q@mail.gmail.com>
On Mon, 27 Apr 2020 22:09:43 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> > >> That means something is wrong with commit 4e0bc29933.
> > > From what I can tell that change is for fixing a different issue.
> >
> > Right! I forgot - commit 4e0bc29933 was only handling it for target. For host,
> > we would need a native-compilation.conf. I had started on that but didn't finish
> > it because I had no package to test it with. Hm, apparently I never even posted
> > the WIP on the mailing list...
> I managed to get it working properly here:
> https://patchwork.ozlabs.org/project/buildroot/patch/20200428040638.122494-1-james.hilliard1 at gmail.com/
I think Arnout wanted a native-compilation.conf instead of passing an
extra argument so that it also works with people building stuff outside
of Buildroot.
However, I don't get how this would have solved the problem as take
here: the issues we are seeing are with *target* packages, which are
looking at using the host pkg-config. Which is exactly what
4e0bc29993376613d200e892d491e31ea5a49622 was supposed to fix. So I'm
really confused.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-28 5:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 23:09 [Buildroot] [PATCH 1/1] package/wayland: bump to version 1.18.0 James Hilliard
2020-03-05 20:05 ` Thomas Petazzoni
2020-03-05 20:23 ` James Hilliard
2020-03-09 8:12 ` Arnout Vandecappelle
2020-03-24 18:19 ` James Hilliard
2020-03-25 8:02 ` Arnout Vandecappelle
2020-04-28 4:09 ` James Hilliard
2020-04-28 5:24 ` Thomas Petazzoni [this message]
2020-04-28 5:38 ` James Hilliard
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=20200428072438.2f7f2b0e@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