Apparently perl was removed from @system (it is no longer in the stage3 tarballs) and either the kernel requires it or genkernel requires it to build the kernel so it should either be re-added to @system or *-sources or genkernel should RDEPEND on it.
I cannot find any traces of perl in genkernel. Re-assigning to firstname.lastname@example.org.
I do see where perl can be needed in the make process. Our kernels should depend on perl. I've talked to blueness from hardened and will work with other maintainers.
genkernel does not need perl, but all linux sources do. Its part of the build process of the linux kernel. Here's just one eg from a typical file:
make -f scripts/Makefile.build obj=arch/x86/kernel/cpu
perl /usr/src/linux-3.2.12-gentoo/arch/x86/kernel/cpu/mkcapflags.pl arch/x86/kernel/cpu/../../include/asm/cpufeature.h arch/x86/kernel/cpu/capflags.c
/bin/sh: perl: command not found
make: *** [arch/x86/kernel/cpu/capflags.c] Error 127
make: *** [arch/x86/kernel/cpu] Error 2
make: *** [arch/x86/kernel] Error 2
make: *** [arch/x86] Error 2
Okay so we have some choices as discussed in irc:
1) we could re-introduce perl into the profiles. It would best go into default/linux on the interpretation that "linux" means the linux kernel.
This solves the problem but some might argue that they don't want perl in their stage3. One can bootstrap out of our current stage3's and get perl. So please keep perl out and those who want it can re-introduce it.
2) we could make kernel-2.eclass depend on perl since presumeably if you are emerging a linux source, you want to next build it.
3) we could argue the same for genkernel. If you emerge genkernle, presumeably you want to use it to compile a kernel, so we need perl.
#2 seems the best to me because its closest to the problem. ie. I may emerge a linux source and build it without genkernel. So I still need perl.
Comments? I'm cc-ing base system to see how they feel about re-introducing perl into the profiles. One can argue that many other systems, like gnu autotools, are heavily perl dependant and maybe we should bring it back? (I personally don't think so, but others may know something I don't --- I feel a slippery slope with python and others.)
*** Bug 421521 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> genkernel does not need perl, but all linux sources do. Its part of the
> build process of the linux kernel.
> 2) we could make kernel-2.eclass depend on perl since presumeably if you are
> emerging a linux source, you want to next build it.
This seems to be the most logical solution. Please apply ASAP.
*** Bug 422719 has been marked as a duplicate of this bug. ***
*** Bug 423029 has been marked as a duplicate of this bug. ***
perl doesn't belong in @system
Created attachment 316117 [details, diff]
Adds dev-lang/perl to kernel source's RDEPEND
This should do it. Mike comments?
(In reply to comment #9)
> Created attachment 316117 [details, diff] [details, diff]
> Adds dev-lang/perl to kernel source's RDEPEND
> This should do it. Mike comments?
That'll do the trick.
I'll add it. Sounds right to me, also.
This is complete. Thanks, everyone. And thanks, Anthony, for taking point.
I am posting on behalf of a collegue (Rob Landley) with an alternate solution. He has a patch set that removes the perl requirements from the kernel build system (and hence the need not to add to RDEPEND). Perl was first introduced in 2.6.25 and has been there ever since. His patches (three of them) are available here as linux-noperl*.patch.
(In reply to comment #13)
get it merged into mainline then. while we might be able to patch gentoo-sources, it's not really something we want to maintain, and we wouldn't be patching other source pkgs like vanilla-sources.
*** Bug 435010 has been marked as a duplicate of this bug. ***