From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/2] package/openipmi: add libexecinfo optional dependency
Date: Fri, 17 Feb 2023 16:10:40 +0100 [thread overview]
Message-ID: <20230217161040.42a0c31a@windsurf> (raw)
In-Reply-To: <20221030182041.GX1058960@scaer>
Hello Yann,
On Sun, 30 Oct 2022 19:20:41 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Fabrice, All,
>
> On 2022-10-30 18:56 +0100, Fabrice Fontaine spake thusly:
> > Add libexecinfo optional dependency as upstream rejected the patch to
> > add --with-execinfo=no
>
> Indeed, they rejected it, but they suggested an alternate solution:
> check for backtrace() and whether it requires -lexecinfo.
>
> Something like:
>
> AC_SEARCH_LIBS(
> [backtrace],
> [execinfo],
> ,
> [AC_MSG_ERROR([backtrace() not found and no library provides it; maybe install libexecinfo])]
> )
>
> Regards,
> Yann E. MORIN.
Agreed, but for now, Fabrice's patch was good enough, so I applied
as-is. It will certainly be nice if Fabrice has the chance to work on a
better solution using AC_SEARCH_LIBS().
Best regards,
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
next prev parent reply other threads:[~2023-02-17 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 17:56 [Buildroot] [PATCH v2, 1/2] package/openipmi: add libexecinfo optional dependency Fabrice Fontaine
2022-10-30 17:56 ` [Buildroot] [PATCH v2, 2/2] package/openipmi: bump to version 2.0.33 Fabrice Fontaine
2022-10-30 18:20 ` [Buildroot] [PATCH v2, 1/2] package/openipmi: add libexecinfo optional dependency Yann E. MORIN
2023-02-17 15:10 ` Thomas Petazzoni via buildroot [this message]
2023-02-17 15:09 ` 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=20230217161040.42a0c31a@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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