Summary: | sys-fs/shake-0.999: fails to build with sys-devel/glibc-2.17 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Bernard Cafarelli <voyageur> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/sys-fs%3Ashake-0.999%3A20130112-051212.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 448860 |
Description
Diego Elio Pettenò (RETIRED)
2013-01-13 14:41:26 UTC
Looks like glibc-2.17, as 2.17 with linux-headers-3.7 compiles OK. Looking into it Fixed in current ~arch sys-fs/shake-0.999 ebuild https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/sys-fs%3Ashake-0.999%3A20130219-093445.html Doesn't look that way to me. I can confirm failing to build at 83 percentage: http://privatepaste.com/1d5d8ffc91 using glibc-2.17 and gcc-4.7.2-r1 Actually the shake/files/shake-0.999-fix_stat_include.patch doesn't patch the source automatically per ebuild: grep sys/stat.h judge.h judge.c judge.c:#include <sys/stat.h> // stat(), umask() after manually patching, looks as should: grep sys/stat judge.h judge.c judge.h:#include <sys/stat.h> I don't know howto writing ebuild, therefore I looked up another ebuild doing files/patching. The following diff of the ebuild does patch the shake sources: --- /portable/portdir/sys-fs/shake/shake-0.999.ebuild 2013-01-21 14:01:31.000000000 +0100 +++ shake-0.999.ebuild 2013-03-16 14:31:39.471829344 +0100 @@ -19,6 +19,8 @@ S=${WORKDIR}/${PN}-fs-${PV} -src_prepare() { +src_unpack() { + unpack ${A} + cd "${S}" epatch "${FILESDIR}"/${P}-fix_stat_include.patch } And compiles well! Yes, sorry about that, I added the patch in src_prepare, but the ebuild did not have EAPI set, so it would never call it... thanks Ulenrich for hunting this down! shake-0.999 is now EAPI 5 and the patch is now applied properly |