Bug 934777 – dev-python/pillow-10.3.0 fails to compile

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description gresskar1 2024-06-23 16:17:23 UTC]

Created attachment 896297 [details]
emerge --info output

dev-python/pillow fails to compile

[Comment 1 gresskar1 2024-06-23 16:18:08 UTC]

Created attachment 896298 [details]
build log

[Comment 2 Michał Górny 2024-06-24 01:32:25 UTC]

I don't see any real error here.  Could you check dmesg for signs of processes crashing?

[Comment 3 gresskar1 2024-06-28 16:26:34 UTC]

(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

[Comment 4 Larry the Git Cow 2024-06-28 17:28:39 UTC]

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 <[e-mail]>
AuthorDate: 2024-06-28 17:24:57 +0000
Commit:     Sam James <[e-mail]>
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 <[e-mail]>

 dev-python/pillow/pillow-10.3.0.ebuild | 1 +
 1 file changed, 1 insertion(+)

[Comment 5 Sam James 2024-06-28 17:29:01 UTC]

Can you emerge --sync in a bit and give us a new build.log? Thanks.

[Comment 6 gresskar1 2024-06-28 17:37:30 UTC]

Created attachment 896583 [details]
Updated build.log

[Comment 7 Sam James 2024-06-28 18:03:44 UTC]

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...

[Comment 8 Brandon Schneider 2024-06-28 21:53:19 UTC]

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.

[Comment 9 Brandon Schneider 2024-06-28 21:53:35 UTC]

Created attachment 896590 [details]
Brandon's build.log

[Comment 10 Brandon Schneider 2024-06-28 21:57:58 UTC]

Just got this to build correctly, the truetype USE flag is now required it seems, which pulls in freetype as expected.

[Comment 11 Sam James 2024-06-29 08:26:50 UTC]

(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!

[Comment 12 Brandon Schneider 2024-06-29 18:04:51 UTC]

(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!