Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "Adam C. Foltzer" <acfoltzer@galois.com>,
	Ross Burton <ross.burton@intel.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 1/3] meson: update Meson devtool to 0.40.1
Date: Wed, 7 Jun 2017 21:44:32 +0000	[thread overview]
Message-ID: <8806ffa9be8f4516b3f29cc1be0ceaf3@XBOX02.axis.com> (raw)
In-Reply-To: <20170605172321.12557-1-acfoltzer@galois.com>

> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> Adam C. Foltzer
> Sent: den 5 juni 2017 19:23
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] [meta-oe][PATCH 1/3] meson: update Meson devtool to
> 0.40.1
> 
> Signed-off-by: Adam C. Foltzer <acfoltzer@galois.com>
> ---
>  meta-oe/recipes-devtools/meson/{meson_0.37.1.bb => meson_0.40.1.bb} |
> 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta-oe/recipes-devtools/meson/{meson_0.37.1.bb =>
> meson_0.40.1.bb} (88%)
> 
> diff --git a/meta-oe/recipes-devtools/meson/meson_0.37.1.bb b/meta-
> oe/recipes-devtools/meson/meson_0.40.1.bb
> similarity index 88%
> rename from meta-oe/recipes-devtools/meson/meson_0.37.1.bb
> rename to meta-oe/recipes-devtools/meson/meson_0.40.1.bb
> index dbbea64..fd96b42 100644
> --- a/meta-oe/recipes-devtools/meson/meson_0.37.1.bb
> +++ b/meta-oe/recipes-devtools/meson/meson_0.40.1.bb
> @@ -9,7 +9,7 @@ SRC_URI = " \
>      file://native_bindir.patch \
>  "
> 
> -SRCREV = "3d4bfdcb22314ea7db45a5b075f8b2a9c1498aab"
> +SRCREV = "b25d3e4d3f2b4d37029a507cc089bdde643c6240"
> 
>  S = "${WORKDIR}/git"
> 
> --
> 2.9.4

When I updated the meson recipe to 0.37.1, I did not update it to the 
latest version at the time (0.38 something if I remember correctly)
because the latter version failed to build shared libraries if building 
with PIE had been enabled by including security_flags.inc. I had 
planned to look into that, but never got around to it. If you have not 
tried building with PIE enabled, you should try that as it probably 
still causes build problems with 0.40.1...

My guess is that the problem stems from the fact that security_flags.inc 
adds -pie (which is a linker flag) to SECURITY_CFLAGS rather than 
SECURITY_LDFLAGS...

//Peter



  parent reply	other threads:[~2017-06-07 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 17:23 [meta-oe][PATCH 1/3] meson: update Meson devtool to 0.40.1 Adam C. Foltzer
2017-06-05 17:23 ` [meta-oe][PATCH 2/3] meson: fix build/host confusion for bbclass Adam C. Foltzer
2017-06-16 11:19   ` Linus Svensson
2017-06-26 13:07     ` Burton, Ross
2017-06-05 17:23 ` [meta-oe][PATCH 3/3] meson: add LDFLAGS to bbclass C/C++ link arguments Adam C. Foltzer
2017-06-07 21:48   ` Peter Kjellerstedt
2017-06-08 17:34     ` [meta-oe][PATCH v2] meson: add LDFLAGS to bbclass C/C++ link Adam C. Foltzer
2017-06-08 17:34       ` [meta-oe][PATCH v2] meson: add LDFLAGS to bbclass C/C++ link arguments Adam C. Foltzer
2017-06-08 17:44         ` Khem Raj
2017-06-08 17:50           ` Adam Foltzer
2017-06-26 12:58         ` Burton, Ross
2017-06-07 21:44 ` Peter Kjellerstedt [this message]
2017-06-09  8:43   ` -pie in SECURITY_CFLAGS (was: Re: [meta-oe][PATCH 1/3] meson: update Meson devtool to 0.40.1) Patrick Ohly
2017-06-09 13:24     ` Khem Raj
2017-06-09 14:34       ` Patrick Ohly
2017-06-09 17:32         ` Patrick Ohly
2017-06-12  7:04           ` Patrick Ohly
2017-06-12 14:47             ` Khem Raj
2017-06-12 18:23               ` Peter Kjellerstedt
2017-06-12 18:50                 ` Khem Raj
2017-06-08 19:47 ` [meta-oe][PATCH 1/3] meson: update Meson devtool to 0.40.1 Martin Jansa

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=8806ffa9be8f4516b3f29cc1be0ceaf3@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=acfoltzer@galois.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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