From: Peter Seiderer <ps.report@gmx.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC v1] package/assimp: fix namespace related compile failure
Date: Fri, 31 Dec 2021 09:18:00 +0100 [thread overview]
Message-ID: <20211231091800.629b2ad3@gmx.net> (raw)
In-Reply-To: <20211230211120.031434c7@windsurf>
Hello Thomas,
On Thu, 30 Dec 2021 21:11:20 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Thu, 30 Dec 2021 18:25:07 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Note:
> > - patch fixes the compile failure but did not find the root cause
> > and/or a good explanation why the template spezialisation failes
> > for Structure::Convert<CollectionObject> and
> > Structure::Convert<CollectionChild> (but not the other ones) and
> > why it is fixed by the patch...
>
> I see in the pull request you've submitted upstream that the issue
> appears with g++ Sourcery CodeBench Lite 2014.05-29 - 4.8.3 20140320,
> which is really a super-old toolchain. Could it be that g++ 4.8 has a
> bug? It clearly is possible, on tricky/modern C++ stuff.
Same failure today (see [1]) with:
$ ./host/bin/mips-linux-gnu-g++ --version
mips-linux-gnu-g++ (Sourcery CodeBench Lite 2016.05-8) 5.3.0
And merge request accepted upstream, see [2]...
Regards,
Peter
[1] http://autobuild.buildroot.net/results/4ed8516cb03a6447b44f2c3731b2197fd6eea9d9
[2] https://github.com/assimp/assimp/commit/a099fe7cd331a839137115db5df1733c4c1c8070
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-31 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 17:25 [Buildroot] [RFC v1] package/assimp: fix namespace related compile failure Peter Seiderer
2021-12-30 17:43 ` Peter Seiderer
2021-12-30 20:11 ` Thomas Petazzoni
2021-12-31 8:18 ` Peter Seiderer [this message]
2022-01-03 15:23 ` Thomas Petazzoni
2022-01-01 10:43 ` Yann E. MORIN
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=20211231091800.629b2ad3@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--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