Summary says all, if it is set it will never get to the compile stage.
perl should be installed on all Gentoo systems
Sometimes I wonder on here if people deliberately ignore problems. SpanKY, if perl *is* installed with minimal, libtool won't compile.
whats your point ? the perl ebuild already warned you that the resulting perl would be quite, ahem, minimal more than just libtool will fail to build, tracking all of these is a waste of time
(In reply to comment #3) > more than just libtool will fail to build, tracking all of these is a waste of > time I thought the point of dependencies was to track down the required elements of a package to compile and to run it, if you ignore useflags, pkgconfig and all other sorts of required elements, why bother to call them dependencies if you assume the rest of the 'dependencies' is already installed. When people spend time making ebuilds, why would do half a job in dep tracking? I really don't see the point why anyone would leave out deps when they are pointed at them. Especially when it is so easy to reproduce (or should I say: make the error?).
in the case of the 'minimal' USE flag, it's meant for very specific use (aka embedded), not for anything else so tracking the fact that 90% of ebuilds fail due to this is a waste of time
I can live with the situation. Point made :)
Comment #1 From SpanKY : "perl should be installed on all Gentoo systems" ermm.. despite the fact that this makes quite a huge dependancy (there's already python), i have the following question : if that's so, why isn't perl included in the "system" list ?
the status of perl wrt system is irrelevant when talking about libtool libtool does not execute perl
# emerge libtool Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) sys-devel/libtool-1.5.26 to / * libtool-1.5.26.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking libtool-1.5.26.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking libtool-1.5.26.tar.gz to /var/tmp/portage/sys-devel/libtool-1.5.26/work * Applying libtool-1.5.20-use-linux-version-in-fbsd.patch ... [ ok ] * Applying libtool-1.5.10-locking.patch ... [ ok ] * Applying libtool-1.5.20-version-checking.patch ... [ ok ] * Applying libtool-1.5-filter-host-tags.patch ... [ ok ] * Applying libtool-1.5.20-override-LD_LIBRARY_PATH.patch ... [ ok ] * Generating ltmain.sh ... [ ok ] * Running autotools in '.' ... * QA Notice: 'aclocal' called by src_unpack: sys-devel/libtool-1.5.26 * Use autotools.eclass instead of calling 'aclocal' directly. /usr/bin/aclocal: /usr/bin/aclocal-1.10: /usr/bin/perl: bad interpreter: No such file or directory /usr/bin/aclocal: line 156: /usr/bin/aclocal-1.10: Success * * ERROR: sys-devel/libtool-1.5.26 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2097: Called die * The specific snippet of code: * ${p} || die "${p}"; * The die message: * aclocal * * 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-devel/libtool-1.5.26/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-1.5.26/temp/environment'. *
aclocal calls perl, not libtool. However, aclocal comes from automake. libtool has automake in RDEPEND and DEPEND (this is proper). automake depends on perl. So, perl does get properly pulled in. I'm willing to guess that you decided to unmerge a bunch of packages and are now trying to emerge a few. post the output of: emerge -puDNv world
I have no problem on my computer. As said in previous post, i just wonder, why isn't perl included in the "system" list ? I had removed perl because it's bloating my hard disk. It is in the top #5 for disk space usage, using the oh-so-useful script equery size |awk '{ print $4 " " $1}' | sed -e 's/^size(\(.*\))/\1/' | sort -n Although it seems gentoo is not usable without perl. So I just wonder.. why not perl in system ?
Because perl is properly depended on in all the packages. The "system" set is for low level packages that can not properly depend because of inter-depends that low.
Thomas: if you removed perl, then you should have removed everything that RDEPENDs on it as well. if you didnt, then you broke your system, and there is nothing wrong with the ebuilds in the tree or the package manager you're using. as Doug points out, the autotool ebuilds all have proper RDEPEND/DEPEND values wrt to perl and other autotool packages Gentoo is perfectly usable in a binary situation w/out perl
"Gentoo is perfectly usable in a binary situation w/out perl" -> yes, that was my conclusion too. Although you will need it as soon as you need to compile/install anything. Too bad, but i know it's not gentoo's fault. Thanks for the explanations. regards, Thomas
