From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH, next 1/1] package/libglib2: bump to version 2.62.2
Date: Thu, 14 Nov 2019 21:14:23 +0100 [thread overview]
Message-ID: <20191114211423.555413ad@gmx.net> (raw)
In-Reply-To: <CAFSsvmphUacxn59u6N4A3BYBMwCAG5FFbUvDfrPMTkRbSVvZ8g@mail.gmail.com>
Hello Adam, Thomas,
On Thu, 14 Nov 2019 08:12:47 -0800, Adam Duskett <aduskett@gmail.com> wrote:
> I believe it's triggered due to the `needs_exe_wrapper = true` in
> package/meson/cross-compilation.conf
>
> On Wed, Nov 13, 2019 at 11:45 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > On Wed, 13 Nov 2019 11:19:50 -0800
> > Adam Duskett <aduskett@gmail.com> wrote:
> >
> > > > > + # Don?t build the tests unless we can run them (either natively, in an exe wrapper, or by installing them for later use)
> > > > > +-build_tests = not meson.is_cross_build() or (meson.is_cross_build() and meson.has_exe_wrapper()) or installed_tests_enabled
> > > > > ++build_tests = installed_tests_enabled
> > > >
> > > > Why do we need to change this ? Is meson.has_exe_wrapper() true in our case ?
No, for the host build it is the 'not meson.is_cross_build()' case...
Regards,
Peter
> > > >
> > > I believe so. Without the change, the tests are triggered to build.
> > > I'm not sure where we are triggering has_exe_wrapper,
> > > but it is indeed being triggered.
> >
> > It would be good to understand what is this has_exe_wrapper thing, and
> > why we are triggering it.
> >
> > Thanks,
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2019-11-14 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:02 [Buildroot] [PATCH, next 1/1] package/libglib2: bump to version 2.62.2 aduskett at gmail.com
2019-11-12 20:53 ` Thomas Petazzoni
2019-11-13 19:19 ` Adam Duskett
2019-11-13 19:45 ` Thomas Petazzoni
2019-11-14 16:12 ` Adam Duskett
2019-11-14 20:14 ` Peter Seiderer [this message]
2019-11-14 22:52 ` Adam Duskett
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=20191114211423.555413ad@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