On Fri, Oct 09, 2020 at 08:09:22PM -0400, Jude DaShiell wrote: > Before I do this, would it be useful to do > emerge --config espeak in the chroot environment?
Unless you've changed anything espeak-related since the initial emerge, I don't
think `--config` will do anything. It does not have a `pkg_config` function
defined in the ebuild, so a standard run of emerge should do everything [1, 2].
Have a look at this (heavily truncated) log of the called Bash functions:
$ emerge -d --config espeak
[...]
* pkg_config() is not defined: 'espeak-1.48.04-r1.ebuild'
+ __ebuild_phase_with_hooks pkg_config
+ local x phase_name=pkg_config
+ for x in {pre_,,post_}${phase_name}
+ __ebuild_phase pre_pkg_config
+ declare -F pre_pkg_config
+ for x in {pre_,,post_}${phase_name}
+ __ebuild_phase pkg_config
+ declare -F pkg_config
+ for x in {pre_,,post_}${phase_name}
+ __ebuild_phase post_pkg_config
+ declare -F post_pkg_config
[...]
Good luck with your installation. Hope it all goes well.
[1] https://devmanual.gentoo.org/ebuild-writing/functions/pkg_config/index.html
[2] https://devmanual.gentoo.org/ebuild-writing/functions/
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
