From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/assimp: needs gcc >= 7
Date: Sat, 1 Jul 2023 22:52:08 +0200 [thread overview]
Message-ID: <20230701225208.59d26569@windsurf> (raw)
In-Reply-To: <20230612170110.1550878-1-bernd.kuhls@t-online.de>
On Mon, 12 Jun 2023 19:01:10 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/d6c/d6caf3c2c0fd670e70950d3e89629df39f8ce596/
>
> After adding various fixes for the autobuilder error and subsequent
> build errors this build error can only be fixed by using gcc >= 7:
>
> output/build/assimp-5.2.5/code/AssetLib/Obj/ObjFileParser.cpp:55:23:
> fatal error: string_view: No such file or directory
>
> Usage of string_view was added in version 5.2.5 by upstream commit
> https://github.com/assimp/assimp/commit/f6bcb160d08af267778fbc59b480ce5d9c52c92c
> which was added to buildroot by commit
> 7d843d9cc0064d6690cfc000e579f575e2c0cc4d
>
> Removed BR2_TOOLCHAIN_HAS_GCC_BUG_64735 which is only valid for gcc < 7
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/assimp/Config.in | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-01 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 17:01 [Buildroot] [PATCH 1/1] package/assimp: needs gcc >= 7 Bernd Kuhls
2023-07-01 20:52 ` Thomas Petazzoni via buildroot [this message]
2023-07-16 17:45 ` Peter Korsgaard
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=20230701225208.59d26569@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--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