From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/meson: fix malformed cross-compilation.conf.in
Date: Mon, 1 Jan 2018 14:02:29 +0100 [thread overview]
Message-ID: <20180101130229.GA2999@scaer> (raw)
In-Reply-To: <CAFSsvmr21N+7tTGDY-qXQ7zhD1C2-QKBOKxPWuZdB-6QPHSeZg@mail.gmail.com>
Adam, All,
On 2017-12-31 16:04 -0500, Adam Duskett spake thusly:
> On Sat, Dec 30, 2017 at 4:56 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Currently, meson will set the c_link_args and the cpp_link_args to the
> > value of TARGET_LDFLAGS, even when it's not defined.
> >
> > This creates a malformed array ["",] which will break any package
> > building using meson/ninja.
> >
> > We fix that by using an empty replacement when the corresponding values
> > are empty.
> >
> > Reported-by: Adam Duskett <Adamduskett@outlook.com>
> > Signed-off-by: Adam Duskett <Adamduskett@outlook.com>
> > [yann.morin.1998 at free.fr: alternate implementation, suggested by Thomas]
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> > package/meson/meson.mk | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/package/meson/meson.mk b/package/meson/meson.mk
> > index 55ce84da07..d55c3c7c00 100644
> > --- a/package/meson/meson.mk
> > +++ b/package/meson/meson.mk
> > @@ -16,15 +16,19 @@ HOST_MESON_NEEDS_HOST_PYTHON = python3
> > HOST_MESON_TARGET_ENDIAN = $(call LOWERCASE,$(BR2_ENDIAN))
> > HOST_MESON_TARGET_CPU = $(call qstrip,$(BR2_GCC_TARGET_CPU))
> >
> > +HOST_MESON_SED_CFLAGS = $(if $(TARGET_CFLAGS),`printf '"%s"$(comma) ' $(TARGET_CFLAGS)`)
> > +HOST_MESON_SED_LDFLAGS = $(if $(TARGET_LDFLAGS),`printf '"%s"$(comma) ' $(TARGET_LDFLAGS)`)
> > +HOST_MESON_SED_CXXFLAGS = $(if $(TARGET_CXXFLAGS),`printf '"%s"$(comma) ' $(TARGET_CXXFLAGS)`)
> > +
> > define HOST_MESON_INSTALL_CROSS_CONF
> > mkdir -p $(HOST_DIR)/etc/meson
> > sed -e "s%@TARGET_CROSS@%$(TARGET_CROSS)%g" \
> > -e "s%@TARGET_ARCH@%$(ARCH)%g" \
> > -e "s%@TARGET_CPU@%$(HOST_MESON_TARGET_CPU)%g" \
> > -e "s%@TARGET_ENDIAN@%$(HOST_MESON_TARGET_ENDIAN)%g" \
> > - -e "s%@TARGET_CFLAGS@%`printf '"%s", ' $(TARGET_CFLAGS)`%g" \
> > - -e "s%@TARGET_LDFLAGS@%`printf '"%s", ' $(TARGET_LDFLAGS)`%g" \
> > - -e "s%@TARGET_CXXFLAGS@%`printf '"%s", ' $(TARGET_CXXFLAGS)`%g" \
> > + -e "s%@TARGET_CFLAGS@%$(HOST_MESON_SED_CFLAGS)%g" \
> > + -e "s%@TARGET_LDFLAGS@%$(HOST_MESON_SED_LDFLAGS)%g" \
> > + -e "s%@TARGET_CXXFLAGS@%$(HOST_MESON_SED_CXXFLAGS)%g" \
> > -e "s%@HOST_DIR@%$(HOST_DIR)%g" \
> > $(HOST_MESON_PKGDIR)/cross-compilation.conf.in \
> > > $(HOST_DIR)/etc/meson/cross-compilation.conf
> Tested and works well. This needs to be pushed before I can send a
> systemd patch.
To report testing success, one just replies with something like (with no
indentation):
Tested-by: You you at there
This way this gets picked up by patchwork, and reported as such:
https://patchwork.ozlabs.org/project/buildroot/list/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-01-01 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 9:56 [Buildroot] [PATCHv2] package/meson: fix malformed cross-compilation.conf.in Yann E. MORIN
2017-12-31 21:04 ` Adam Duskett
2018-01-01 13:02 ` Yann E. MORIN [this message]
2018-01-01 15:17 ` Adam Duskett
2018-01-01 22:05 ` Thomas Petazzoni
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=20180101130229.GA2999@scaer \
--to=yann.morin.1998@free.fr \
--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