Hey!
2018-05-04 13:50 GMT+02:00 Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>:
4 mai 2018 13:44 "miqlas" <miqlas@xxxxxxxxx> a écrit:
Hi Guys,GCC5.4.0 doesn't provide
recently PulkoMandy wrote, further WebKit merge requires new GCC as
something (afaik constexpr).
It's not constexpr itself, but the use of constexpr somewhere in the C++14
standard library.
fine, but i haven't did
So i just updated the GCC7.1.0 recipe to 7.3.0, builds and packages just
much testing. It was able to compile some small projects and theresulting binaries working ok. I
know, this testing is not enough for changing a significant part likeGCC, it should be able to
build Haiku too, etc.should switch to the latest.
But in the meantime GCC released GCC8.1, so if we switch GCC, maybe we
have the following
I can update the GCC8 recipe, and test it, but to spare with my time i
questions:
- Do we want to switch to newer GCC before Beta?
Only if it doesn't break things.
As a first step I would suggest naming the new package gcc7 (or gcc8)
instead of just gcc. This way by
default people still get gcc5 (and we still build Haiku with it), but we
can start experimenting with
newer versions?
- Should we stay with the 5.x branch can we switch to the 7.x/8.x branch?
I still don't get the new gcc versionning scheme. So, I don't know. Did
they break the ABI?
the libs resides in gccX_syslibs subpackage.update and test the recipe,
If you guys can tell me, wich version preferred, i can try my best to
building Haiku with it on different hosts, report problems and so.be good idea to introduce
Yet a question: the current GCC recipes stripping the GCC libs. Would it
debuginfo packages for them?
Yes.
Let's see if HP capable to create debuginfo package for subpackage, as
Adrien.--miqlas
