Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yunhao Tian <t123yh.xyz@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/bluez5_utils: fix AC_CHECK_FILE error
Date: Mon, 10 Jul 2023 19:14:49 +0200	[thread overview]
Message-ID: <20230710191449.7fabb833@windsurf> (raw)
In-Reply-To: <CAFQXTv28aGSj2hz+LwpcRaMgc7zkwtpF5+2QR6svxTHe8DE3Ow@mail.gmail.com>

Hello Yunhao,

On Tue, 11 Jul 2023 00:39:38 +0800
Yunhao Tian <t123yh.xyz@gmail.com> wrote:

> > (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  
> Understood, thanks for pointing out!
> >
> > (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.  
> I don't think this is worth the effort. Source code package of bluez
> already comes
> with internal ell, so it is not necessary to check it in our use case.

Aaah, but then I misunderstood. I thought the issue occurred when using
an external ELL.

Then in that case, the solution is "easier": we should not use the
internal copy of ELL in bluez-utils sources, but we should use the
external one. In Buildroot, whenever possible we try to use external
libraries, to avoid having multiple copies of the same code in the
target, and also to ensure security issues/bugs only need to be fixed
in one place.

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

  parent reply	other threads:[~2023-07-10 17:15 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
     [not found]   ` <CAFQXTv28aGSj2hz+LwpcRaMgc7zkwtpF5+2QR6svxTHe8DE3Ow@mail.gmail.com>
2023-07-10 17:14     ` Thomas Petazzoni via buildroot [this message]
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=20230710191449.7fabb833@windsurf \
    --to=buildroot@buildroot.org \
    --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