From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] libdrm: change to meson build system
Date: Sun, 4 Aug 2019 22:50:30 +0200 [thread overview]
Message-ID: <20190804225030.616e29fd@gmx.net> (raw)
In-Reply-To: <20190804102807.5b0d142d@windsurf.home>
On Sun, 4 Aug 2019 10:28:07 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
Hello Thomas,
> On Tue, 25 Jun 2019 22:11:27 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > - remove legacy patch
> > 0003-configure-Makefile.am-use-pkg-config-to-discover-lib.patch
> >
> > - add patch to fix meson atomic ops detection
> > 0003-meson.build-fix-intel-atomics-detection.patch
> >
> > - add patch to enable static build
> > 0004-meson.build-enable-static-build.patch
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Notes:
> > - convertion from "LIBDRM_CONF_ENV = ac_cv_prog_cc_c99='-std=gnu99'"
> > is missing (maybe meson gets it right (?) or use LIBDRM_CFLAGS
> > to force it)
>
> Applied to master, thanks. However, there is already one build failure,
> I'm not sure if it's directly related to the meson change:
>
> http://autobuild.buildroot.net/results/d15/d15ed604756cac4e4a87afca61b7a4778f293baf/build-end.log
Ups, known issue ;-) and reminds me of an old (but not yet ready for submission) patch in my
git repository fixing the issue, draft submitted ([1]) just now...
Updated version (with proper commit log, autobuild referecen etc.) will follow...
Regards,
Peter
[1] https://patchwork.ozlabs.org/patch/1141849/
>
> Best regards,
>
> Thomas
prev parent reply other threads:[~2019-08-04 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 20:11 [Buildroot] [PATCH v7] libdrm: change to meson build system Peter Seiderer
2019-08-04 8:28 ` Thomas Petazzoni
2019-08-04 20:50 ` Peter Seiderer [this message]
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=20190804225030.616e29fd@gmx.net \
--to=ps.report@gmx.net \
--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