Building which 2.19 in a catalyst environment results in build failure as follows: config.status: creating Makefile config.status: creating maintMakefile config.status: creating tilde/Makefile config.status: creating config.h config.status: executing depfiles commands make all-recursive make[1]: Entering directory `/var/tmp/portage/sys-apps/which-2.19/work/which-2.19' Making all in tilde make[2]: Entering directory `/var/tmp/portage/sys-apps/which-2.19/work/which-2.19/tilde' source='tilde.c' object='tilde.o' libtool=no \ DEPDIR=.deps depmode=pch /bin/sh ../depcomp \ i486-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -mtune=i686 -pipe -c tilde.c In file included from tilde.c:55: xmalloc.h:29:31: error: readline/rlstdc.h: No such file or directory make[2]: *** [tilde.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-apps/which-2.19/work/which-2.19/tilde' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sys-apps/which-2.19/work/which-2.19' make: *** [all] Error 2 * * ERROR: sys-apps/which-2.19 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2080: Called die * The specific snippet of code: * emake || die "emake failed"; * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/which-2.19/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/which-2.19/temp/environment'. * Did a quick and casual look at the ebuild to determine cause and it looks like which-2.19 has an (R)DEPEND on readline which is not reflected in the ebuild. Reproducible: Always Steps to Reproduce: do a catalyst build for x86 (stable) using a current portage snapshot
*** This bug has been marked as a duplicate of bug 207151 ***
This is hitting a stable profile via catalyst and should be fixed. Reopening.
Yeah, so go argue it on the other bug; really don't need two bugs about exact same problem. Thanks. *** This bug has been marked as a duplicate of bug 207151 ***
OK, will do.
Jakub, I can't reopen 207151, and this is an open "real" bug and there should thus be a bug open about the issue. If you want, reopen 207151 and then mark this bug as a duplicate and I'll be happy.
I'll mark this as a duplicate now since I committed the fix from bug #207151 *** This bug has been marked as a duplicate of bug 207151 ***