I'm upgrading my system and know that mktemp is now in coreutils so I removed mktemp and then did an emerge system knowing that coreutils would get upgraded and the new version would include the new mktemp. The problem is that portage made itself the first package to get upgraded and missed coreutils and mktemp so I got the following error: >>> Emerging (1 of 59) sys-apps/portage-2.1.5_rc10 to / * portage-2.1.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * portage-2.1.5_rc10.patch.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking portage-2.1.4.tar.bz2 ;-) ... [ ok ] * checking portage-2.1.5_rc10.patch.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking portage-2.1.4.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.1.5_rc10/work >>> Unpacking portage-2.1.5_rc10.patch.bz2 to /var/tmp/portage/sys-apps/portage-2.1.5_rc10/work * Applying portage-2.1.5_rc10.patch ... [ ok ] * Setting portage.VERSION to 2.1.5_rc10 ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/sys-apps/portage-2.1.5_rc10/work/portage-2.1.4 ... xmlto xhtml portage.docbook /usr/bin/xmlto: line 130: mktemp: command not found /usr/bin/xmlto: line 133: : No such file or directory /usr/bin/xmlto: line 290: mktemp: command not found make: *** [xhtml] Error 1 * * ERROR: sys-apps/portage-2.1.5_rc10 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2195: Called die * The specific snippet of code: * make xhtml xhtml-nochunks || die "failed to make docs"; * The die message: * failed to make docs * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-apps:portage-2.1.5_rc10:20080511-110045.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.1.5_rc10/temp/environment'. We are in need of a bit of {,R}DEPEND lovin' here gentlemen. :) Kindest regards to the portage team; they certainly deserve it.
(In reply to comment #0) > I removed mktemp and then did an emerge system knowing that coreutils would > get upgraded and the new version would include the new mktemp. After removing mktemp you should immediately upgrade coreutils. Otherwise many packages might fail to build. Portage doesn't need mktemp. mktemp is used by xmlto, which is used when Portage is being installed with USE="doc".
The solution was easy enough: emerge -av coreutils Then emerge -av system As confirmed by Arfrever in the preceding comment. My point was that portage should maybe help people through such things.
mktemp is part of system and always will be
