From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Pierre Ducroquet <pinaraf@pinaraf.info>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libcamera: fix missing comment for binutils-bug-27597
Date: Sat, 12 Feb 2022 17:49:51 +0100 [thread overview]
Message-ID: <20220212164951.GE3752867@scaer> (raw)
In-Reply-To: <20220128110542.1101197-2-giulio.benetti@benettiengineering.com>
Giulio, All,
On 2022-01-28 12:05 +0100, Giulio Benetti spake thusly:
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> package/libcamera/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libcamera/Config.in b/package/libcamera/Config.in
> index 23a0040abf..88db054975 100644
> --- a/package/libcamera/Config.in
> +++ b/package/libcamera/Config.in
> @@ -92,7 +92,7 @@ comment "lc-compliance test application needs a toolchain w/ C++, wchar, threads
>
> endif # BR2_PACKAGE_LIBCAMERA
>
> -comment "libcamera needs a toolchain w/ C++, threads, wchar, dynamic library, gcc >= 7"
> +comment "libcamera needs a toolchain w/ C++, threads, wchar, dynamic library, gcc >= 7, not binutils bug 27597"
Bug 27597 is inherently an architecture-speific bug, which is always set
for NIOS2, so there is nothing the user can do about it except switch to
another architecture...
The comments are meant for when the user has an alternative option, like
chossing a different version of a component.
In this case, there is nothing the user can do, so we don't add it to
the comment.
Regards,
Yann E. MORIN.
> depends on BR2_PACKAGE_LIBCAMERA_ARCH_SUPPORTS
> depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS || \
> !BR2_TOOLCHAIN_GCC_AT_LEAST_7 || BR2_STATIC_LIBS || !BR2_USE_WCHAR
> --
> 2.25.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-12 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 11:05 [Buildroot] [PATCH] package/kf5/kf5-kcoreaddons: add missing comment dependency for binutils-bug-27597 Giulio Benetti
2022-01-28 11:05 ` [Buildroot] [PATCH] package/libcamera: fix missing comment " Giulio Benetti
2022-02-12 16:49 ` Yann E. MORIN [this message]
2022-02-12 16:56 ` Giulio Benetti
2022-01-28 11:05 ` [Buildroot] [PATCH] package/pistache: disable package if affected by BR2_TOOLCHAIN_HAS_BINUTILS_BUG_27597 Giulio Benetti
2022-01-30 21:59 ` 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=20220212164951.GE3752867@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=pinaraf@pinaraf.info \
/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