Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/brltty: fix cross-compilation
Date: Wed, 22 Aug 2018 20:01:53 +0200	[thread overview]
Message-ID: <20180822200153.031820b8@gmx.net> (raw)
In-Reply-To: <20180822082832.7497-1-yann.morin.1998@free.fr>

Hello Yann,

On Wed, 22 Aug 2018 10:28:32 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> brltty has a very inventive buildsystem, where it internall runs
> ./configure for the build machine In doing so, it generates a list
> of make variables to define what the build machine supports, like
> it does for the target.
> 
> However, the build variables are generated with a convoluted sed
> script that scans the target list, and appends _FOR_BUILD to each
> target variables. Then, both lists are included from the Makefile,
> on the assumption that the build variables will not clash with the
> target variables.
> 
> Where it gets interesting, is that that sed script considers the
> variables names to match '[A-Za-z][A-Za-z0-9_]*'

Minor nit: did you mean '[A-Za-z][A-Za-z_]*' here?

Regards,
Peter

> 
> And there we see why ATSPI2_PACKAGE does not match: it contains a
> digit.
> 
> So, some build variables will inevitably override target ones.
> 
> Fix that by simply expanding the matching regexp to allow digits
> in variable names.
> 
> Fixes:
>     http://autobuild.buildroot.org/results/a37/a37782b3cfc1a96cc129db8fade20a36a7b2d470/
>     http://autobuild.buildroot.org/results/97e/97edc6a47d2140968e84b409cdc960604e5896f2/
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Mario Lang <mlang@blind.guru>
> Cc: Baruch Siach <baruch@tkos.co.il>
> ---
>  .../0004-buildsys-fix-cross-compilation.patch      | 41 ++++++++++++++++++++++
>  1 file changed, 41 insertions(+)
>  create mode 100644 package/brltty/0004-buildsys-fix-cross-compilation.patch
> 
> diff --git a/package/brltty/0004-buildsys-fix-cross-compilation.patch b/package/brltty/0004-buildsys-fix-cross-compilation.patch
> new file mode 100644
> index 0000000000..9a10d46414
> --- /dev/null
> +++ b/package/brltty/0004-buildsys-fix-cross-compilation.patch
> @@ -0,0 +1,41 @@
> +From 088666535a045dae71bd2fcc6b3a1553023106ce Mon Sep 17 00:00:00 2001
> +From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> +Date: Wed, 22 Aug 2018 10:10:19 +0200
> +Subject: [PATCH] buildsys: fix cross-compilation
> +
> +Some identifiers for includes and libs paths may contain digit, e.g.
> +X11_PACKAGE or ATSPI2_PACKAGE or GLIB2_PACKAGE...
> +
> +Also detect those identifiers when doing cros-compilation, so that the
> +_FOR_BUILD variants are really created and do not clash with the target
> +variants.
> +
> +Fixes:
> +    http://autobuild.buildroot.org/results/a37/a37782b3cfc1a96cc129db8fade20a36a7b2d470/build-end.log
> +    http://autobuild.buildroot.org/results/97e/97edc6a47d2140968e84b409cdc960604e5896f2/build-end.log
> +    [...]
> +
> +Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> +---
> +Upstram status: submitted
> +https://github.com/brltty/brltty/pull/142
> +---
> + mk4build | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/mk4build b/mk4build
> +index db90c86a9..551283825 100755
> +--- a/mk4build
> ++++ b/mk4build
> +@@ -112,7 +112,7 @@ fi
> + 
> + sedScript="${outputName}.${sedExtension}"
> + sed -n -e '
> +-s/^ *\([A-Za-z][A-Za-z_]*\) *=.*$/\1/
> ++s/^ *\([A-Za-z][A-Za-z0-9_]*\) *=.*$/\1/
> + t found
> + d
> + :found
> +-- 
> +2.14.1
> +

  parent reply	other threads:[~2018-08-22 18:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22  8:28 [Buildroot] [PATCH] package/brltty: fix cross-compilation Yann E. MORIN
2018-08-22 10:04 ` Baruch Siach
2018-08-22 20:05   ` Yann E. MORIN
2018-08-22 10:12 ` Mario Lang
2018-08-22 15:34   ` Yann E. MORIN
2018-08-22 18:01 ` Peter Seiderer [this message]
2018-08-22 20:02   ` Yann E. MORIN
2018-08-25 12:40 ` Thomas Petazzoni
2018-08-26 21:23 ` Peter Korsgaard

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=20180822200153.031820b8@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