Summary: | x11-libs/cairo-1.14.6 fails to compile on armv7a-hardfp-musl-vanilla | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Jones <gentoo> |
Component: | Current packages | Assignee: | Alexandre Rostovtsev (RETIRED) <tetromino> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | herrtimson, musl, tsmksubc, x11 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 430702 | ||
Attachments: | build.log.gz |
Description
Michael Jones
2016-12-09 09:23:02 UTC
Does it compile with USE="-glib"? I think this one can be closed, even though this bug was reported against an arm system. I can recall to have merged 1.14.8 a few weeks ago successfully with the latest (!) toolchain. (In reply to tt_1 from comment #2) > I think this one can be closed, even though this bug was reported against an > arm system. I can recall to have merged 1.14.8 a few weeks ago successfully > with the latest (!) toolchain. On ARM? With musl? And hardened? Yes, on arm with musl vanilla profile. Isn't that what this bug is about? The emerge --info looks as if this is a hardened profile where the device has booted into, but the compile was executed in a chroot which is what seems to be a vanilla version of the musl stage3, initially. However, 1.14.6 is not in tree anymore, so from my point of view the bug can and should be closed. (In reply to tt_1 from comment #4) > Yes, on arm with musl vanilla profile. Isn't that what this bug is about? > The emerge --info looks as if this is a hardened profile where the device > has booted into, but the compile was executed in a chroot which is what > seems to be a vanilla version of the musl stage3, initially. However, 1.14.6 > is not in tree anymore, so from my point of view the bug can and should be > closed. Right. It's just a very specific configuration, and you didn't mention that it's what you were using. Michael, can you confirm that the current stable cairo builds in your configuration? I won't be able to, sorry. I no longer have that environment setup. If I set it up again, and run into this bug again, i'll re-open the bug. |