From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/bluez_utils: fix test build issues with musl
Date: Sun, 14 May 2017 16:07:54 +0200 [thread overview]
Message-ID: <20170514160754.5f2b9934@free-electrons.com> (raw)
In-Reply-To: <20170513171009.5219-3-romain.naour@gmail.com>
Hello,
On Sat, 13 May 2017 19:10:09 +0200, Romain Naour wrote:
> Add one missing header and avoid encrypt redefinition.
>
> Fixes:
> http://autobuild.buildroot.net/results/06c/06c930d9c5299b79500d018ac3fb2861ce834c7c/
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Yegor Yefremov <yegorslists@googlemail.com>
I've applied. See a few comments below though.
> diff --git a/package/bluez_utils/0005-test-avoid-conflict-with-encrypt-function.patch b/package/bluez_utils/0005-test-avoid-conflict-with-encrypt-function.patch
> new file mode 100644
> index 0000000..51ab0c1
> --- /dev/null
> +++ b/package/bluez_utils/0005-test-avoid-conflict-with-encrypt-function.patch
> @@ -0,0 +1,107 @@
> +From d8056252d0c99bfb2482f0a420dcf9a36019ddf8 Mon Sep 17 00:00:00 2001
> +From: Romain Naour <romain.naour@gmail.com>
> +Date: Sat, 13 May 2017 18:58:51 +0200
> +Subject: [PATCH 5/5] test: avoid conflict with encrypt function
Please generate patches with 'git format-patch -N' to avoid the
sequence number in the patch itself. Thanks!
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +With a musl based toolchain:
> +
> +test/l2test.c:110:12: error: ?encrypt? redeclared as different kind of symbol
> + static int encrypt = 0;
> + ^
> +In file included from test/l2test.c:34:0:
> +[...]/sysroot/usr/include/unistd.h:145:6: note: previous declaration of ?encrypt? was here
> + void encrypt(char *, int);
This encrypt thing is a bit messy, because the same issue for another
part of bluez_utils is solved in a different way in
0003-fix-compilation-issues-with-musl.patch.
Anyway the existing patches are already a bit messy. Perhaps we should
start thinking about phasing out bluez_utils? Is there a good reason to
still have bluez_utils? Are there some features or hardware devices
that work with bluez_utils and not bluez5_utils? Or does bluez5_utils
requires a recent kernel version?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-14 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 17:10 [Buildroot] [PATCH 1/3] package/bluez_utils: add missing host-pkgconf dependency Romain Naour
2017-05-13 17:10 ` [Buildroot] [PATCH 2/3] bluez_utils: add missing check dependency for test program Romain Naour
2017-05-13 20:28 ` Yann E. MORIN
2017-05-13 21:08 ` Romain Naour
2017-05-14 14:05 ` Thomas Petazzoni
2017-05-14 14:59 ` Yegor Yefremov
2017-05-15 12:43 ` Peter Korsgaard
2017-05-14 14:04 ` Thomas Petazzoni
2017-05-15 12:45 ` Peter Korsgaard
2017-05-13 17:10 ` [Buildroot] [PATCH 3/3] package/bluez_utils: fix test build issues with musl Romain Naour
2017-05-14 14:07 ` Thomas Petazzoni [this message]
2017-05-15 12:46 ` Peter Korsgaard
2017-05-13 20:29 ` [Buildroot] [PATCH 1/3] package/bluez_utils: add missing host-pkgconf dependency Yann E. MORIN
2017-05-14 13:58 ` Thomas Petazzoni
2017-05-15 12:12 ` 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=20170514160754.5f2b9934@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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