Summary: | dev-python/pillow-10.3.0 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gresskar1 |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | brandon, gresskar1, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info output
build log Updated build.log Brandon's emerge --info Brandon's build.log |
Created attachment 896298 [details]
build log
I don't see any real error here. Could you check dmesg for signs of processes crashing? (In reply to Michał Górny from comment #2) > I don't see any real error here. Could you check dmesg for signs of > processes crashing? Nothing interesting from dmesg The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aee3b8bed7c291a7749dede729be27da8b716287 commit aee3b8bed7c291a7749dede729be27da8b716287 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-06-28 17:24:57 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-06-28 17:24:57 +0000 dev-python/pillow: make build_ext more verbose This should help with diagnosing odd build failures as it'll print its "configure" style tests etc. Bug: https://bugs.gentoo.org/934777 Signed-off-by: Sam James <sam@gentoo.org> dev-python/pillow/pillow-10.3.0.ebuild | 1 + 1 file changed, 1 insertion(+) Can you emerge --sync in a bit and give us a new build.log? Thanks. Created attachment 896583 [details]
Updated build.log
Thanks. You're on musl and it looks like it's using find_library-style nonsense at https://github.com/python-pillow/Pillow/blob/main/setup.py#L154. They have a hack for musl but I wouldn't be surprised if it doesn't work with our stub ldconfig on musl... Created attachment 896589 [details]
Brandon's emerge --info
I'm hitting this too trying to emerge virt-manager, however I'm on x86-64. I see this error with the package: `ValueError: Conflicting options: --vendor-raqm and --disable-raqm`
I'm attaching my emerge info and my build.log, if you want me to create a new ticket I can.
Created attachment 896590 [details]
Brandon's build.log
Just got this to build correctly, the truetype USE flag is now required it seems, which pulls in freetype as expected. (In reply to Brandon Schneider from comment #8) > Created attachment 896589 [details] > Brandon's emerge --info > > I'm hitting this too trying to emerge virt-manager, however I'm on x86-64. I > see this error with the package: `ValueError: Conflicting options: > --vendor-raqm and --disable-raqm` > > I'm attaching my emerge info and my build.log, if you want me to create a > new ticket I can. That issue is bug 935124, now fixed, sorry! (In reply to Sam James from comment #11) > (In reply to Brandon Schneider from comment #8) > > Created attachment 896589 [details] > > Brandon's emerge --info > > > > I'm hitting this too trying to emerge virt-manager, however I'm on x86-64. I > > see this error with the package: `ValueError: Conflicting options: > > --vendor-raqm and --disable-raqm` > > > > I'm attaching my emerge info and my build.log, if you want me to create a > > new ticket I can. > > That issue is bug 935124, now fixed, sorry! Thanks Sam! I appreciate it! |
Created attachment 896297 [details] emerge --info output dev-python/pillow fails to compile