On 2/3/22 17:43, Stephen Gallagher wrote:
On Thu, Feb 3, 2022 at 11:08 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
On 03. 02. 22 16:53, Jiri Vanek wrote:
Tag in the older gcc into your side tag, do the rebuilds, untag it?
I'm in favour of doing this as most strightforward solution.
I'm failing to judge all consequences.
There are some obstacles. It might not be just gcc that needs tagging in. It's
probably also annobin, but maybe others?
I recommend trying scratch builds and tag other packages in until it works.
When you reach more than a handful of packages that need to be downgraded this
way, consider not doing it.
yah that did not worked, Y would need to tag half of the world into my buildroot. And I guess paclages with JNI would then be unusable.
I had cleaned the buildroot with help of "jednorozec".
The consequences will practically be the same as if you have done the Java
rebuild before gcc was updated.
This might be a bit of a big hammer, but what about building with
--with-toolchain=clang instead of gcc?
Yes. That is big hammer.
We keep failing to fix hotspot for gcc12, but there was idea yesterday night, to build instead of hotposot zero on i686.
That would be huge performance cost, but may be working.
I keep building the jdk11 and 17 and adapt specfiles, but it is super slow. The full build itertion of jdk have over 6hours.
Cross fingers please!
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
