Open barracuda156 opened 1 week ago
On Tuesday September 24 2024 10:43:36 Sergey Fedorov wrote:
@RJVB Is this something familiar?
Not at all.
Are you in contact with Iain? You could ask him if this could have anything to do with the fact we're using his branch.
You could try the +quick variant, which uses a non-bootstrap build that will be a lot easier to triage and maybe patch.
(FWIW, I just realised something was missing from my patch to introduce -stdlib=libc++
support, 1 single, stupid patch hunk, and I have to do a complete rebuild because the bootstrap build couldn't figure out what to do and botched itself.
Are you in contact with Iain? You could ask him if this could have anything to do with the fact we're using his branch.
Yes, though I am not sure he has dealt with riscv. Do we even need to apply Darwin-specific patches outside of Darwin?
Yes, though I am not sure he has dealt with riscv. Do we even need to apply Darwin-specific patches outside of Darwin?
Need probably not, though I haven't looked at exactly what they offer besides libc++ support. I just like to apply the same patches as much as possible in ports I have on both platforms, and I suppose Iain's goal is also to merge his changes into the main branch and if so he *should be interested to know about side-effects.
I can't really remember why I included them in my Linux build TBH. I remember I excluded them at first, and then there must have been a reason why I decided to include them.
@iains Iain, could you please take a quick look at the error above? Should I open a ticket on GCC bugzilla or it is something known and fixable locally? (This is not powerpc-related, but it uses your branch with minor patches for Linux compatibility.)
@RJVB Is this something familiar?