From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Gwenhael Goavec-Merou <gwenj@trabucayre.com>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0
Date: Fri, 9 Dec 2022 23:30:09 +0100 [thread overview]
Message-ID: <20221209233009.6b003e99@windsurf> (raw)
In-Reply-To: <1670597027-3905-1-git-send-email-gwenj@trabucayre.com>
Hello,
On Fri, 9 Dec 2022 15:43:47 +0100
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:
> Since commit 5a15095f65c655356989c91e52da1746cd96f41b gnuradio requires
> gcc >= 9.3.0
This commit does not have any justification about the gcc 9.3.0
requirement. It seems to have been bumped to 9.3.0 just because Ubuntu
20.04 LTS uses 9.3.0.
So I would suggest to patch out this silly version check, and really
base the gcc version needed by gnuradio on actual issues.
In any case, we need to patch out, because we can't express a
dependency on >= 9.3.0 in Buildroot, we can only express a dependency
on >= 9.x.
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:[~2022-12-09 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 14:43 [Buildroot] [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0 Gwenhael Goavec-Merou
2022-12-09 15:27 ` Thomas Petazzoni via buildroot
2022-12-09 15:32 ` Gwenhael Goavec-Merou
[not found] ` <20221209163756.118bd1d5@x230_1.trabucayre.com>
2022-12-09 16:10 ` Thomas Petazzoni via buildroot
2022-12-10 4:38 ` Bagas Sanjaya
2022-12-09 22:30 ` Thomas Petazzoni via buildroot [this message]
2022-12-10 10:02 ` [Buildroot] Specific toolchain components version support (was Re: [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0) Bagas Sanjaya
2022-12-10 16:28 ` Gwenhael Goavec-Merou
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=20221209233009.6b003e99@windsurf \
--to=buildroot@buildroot.org \
--cc=gwenhael.goavec-merou@trabucayre.com \
--cc=gwenj@trabucayre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.