Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: t123yh.xyz@gmail.com
Cc: Marcin Bis <marcin@bis.org.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bluez5_utils: fix AC_CHECK_FILE error
Date: Mon, 10 Jul 2023 18:20:12 +0200	[thread overview]
Message-ID: <20230710182012.20a5eeb4@windsurf> (raw)
In-Reply-To: <20230710135752.1849099-1-t123yh.xyz@gmail.com>

Hello Yunhao,

On Mon, 10 Jul 2023 21:57:52 +0800
t123yh.xyz@gmail.com wrote:

> From: Yunhao Tian <t123yh.xyz@gmail.com>
> 
> Commit [1] in bluez5 introuduces AC_CHECK_FILE against ell library,
> which produces the following error when configuring:
> 
>   checking for ./ell/ell.h... configure: error: cannot check for file
>   existence when cross compiling
> 
> As this check is not critical in our use case, this patch removes the
> relevant lines in configure.ac and configure to prevent errors.
> 
> [1]:
> https://github.com/bluez/bluez/commit/1106b28be85ac9586d1758839226e163e9030ee2
> 
> Signed-off-by: Yunhao Tian <t123yh.xyz@gmail.com>

Thanks a lot for this patch. However, I think there are several issues with it:

(1) We don't want to patch both configure and configure.ac, we want to
    patch only configure.ac, and use BLUEZ5_UTILS_AUTORECONF = YES

(2) AC_CHECK_FILE supports a cache variable that should allow to
    preseed the result of the check. So passing
    "ac_cv_file_${srcdir}/ell/ell.h=yes" should work-around the check,
    of course assuming the relevant quoting is added to prevent
    mis-interpretation of ${srcdir} in this context.

(3) Using AC_CHECK_FILE here is really horrible. The bluez5_utils
    configure script should be improved to use pkg-config to detect the
    external ELL library.

I think in Buildroot for now (2) would be acceptable, but (3) would
definitely be a nice contribution to upstream bluez5_utils.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-10 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 13:57 [Buildroot] [PATCH 1/1] package/bluez5_utils: fix AC_CHECK_FILE error t123yh.xyz
2023-07-10 16:20 ` Thomas Petazzoni via buildroot [this message]
     [not found]   ` <CAFQXTv28aGSj2hz+LwpcRaMgc7zkwtpF5+2QR6svxTHe8DE3Ow@mail.gmail.com>
2023-07-10 17:14     ` Thomas Petazzoni via buildroot
2023-07-10 17:33     ` Thomas Petazzoni via buildroot

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=20230710182012.20a5eeb4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=marcin@bis.org.pl \
    --cc=t123yh.xyz@gmail.com \
    --cc=thomas.petazzoni@bootlin.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