guile failed to build from source in Fedora rawhide/f30
For details on the mass rebuild see:
Please fix guile at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
guile will be orphaned. Before branching of Fedora 31,
guile will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
Created attachment 1530429 [details]
file build.log too big, will only attach last 1024 bytes
Created attachment 1530430 [details]
file root.log too big, will only attach last 1024 bytes
Created attachment 1530431 [details]
This bug is quite critical because of "Rebuild for readline 8.0" (5:2.0.14-15)
Previously(5:2.0.14-14) there were not any conflicts when updating packages.
DEBUG util.py:490: BUILDSTDERR: Error:
DEBUG util.py:490: BUILDSTDERR: Problem: problem with installed package guile-:2.0.14-13.fc30.x86_64
DEBUG util.py:490: BUILDSTDERR: - package guile-5:2.0.14-13.fc30.x86_64 requires libreadline.so.7()(64bit), but none of the providers can be installed
DEBUG util.py:490: BUILDSTDERR: - cannot install both readline-8.0-2.fc30.x86_64 and readline-7.0-13.fc30.x86_64
DEBUG util.py:490: BUILDSTDERR: - package python3-libs-3.7.2-7.fc30.x86_64 requires libreadline.so.8()(64bit), but none of the providers can be installed
DEBUG util.py:490: BUILDSTDERR: - package python3-devel-3.7.2-7.fc30.x86_64 requires python3-libs(x86-64) = 3.7.2-7.fc30, but none of the providers can be installed
I can see that build failed just on 2 architectures.
Is there some plan to temporary "whitelist" known good architectures? or fix problematic architectures?
On one arch the build seems to be failing in assembler. The error is
Error: bad immediate value for offset (4096)
I guess that means some generated code is too large? Maybe adding or removing some CFLAGS would help?
After several attempts with different CFLAGS, it turned out replacing -O2 with -Os is enough to make the package build again. I'm not sure what is the proper fix, but should be good at least for now.
Thank you very much for unblocking rawhide.
Is there any other BZ which will track removing of workaround
If no; then even this BZ can be used for such purpose.
This should be reported to upstream. However, the 2.0 branch of guile doesn't seem to maintained anymore, so I'm not sure if anyone will care enough to investigate and provide a fix.
(In reply to Miroslav Lichvar from comment #8)
> This should be reported to upstream. However, the 2.0 branch of guile
> doesn't seem to maintained anymore, so I'm not sure if anyone will care
> enough to investigate and provide a fix.
Or you can try to use newer version of guile in rawhide.
And I can see that quite a log of important packages depends on it (make, autogen)
sh# dnf repoquery --whatrequires guile
Last metadata expiration check: 2:08:35 ago on Thu 21 Feb 2019 10:16:59 AM CET.
Maybe it is a time to from "Guile's legacy 2.0.x series"
to the latest stable release 2.2.4.
(In reply to Lukas Slebodnik from comment #9)
> Maybe it is a time to from "Guile's legacy 2.0.x series"
> to the latest stable release 2.2.4.
That's in the guile22 package. guile is for applications that have not been ported yet. When they are all ported, it can be dropped or possibly updated to 3.x, but it depends on how easy will be porting from 2.2 to 3.0.
Thank you very much for answers and your time.
Now it make a sense to me.