[gentoo-catalyst] I need generic solution to package non-building uder catalyst...

[lin pro]

Hi,
I have not yet managed to build a stage4 without any fatal errors when
packages are being built.

This time it is about help2man requiring Locale_gettext pearl module package.
The message in itself is very simple and clear. There is no
dev-utils/Locale_gettex  available for emerge durring the configure
phase.
Adding it to spec file does not change anything.
Rerunning catalyst with an -a switch or -p -P or -T,or even deleting
all of the catalyst/tmp directory brings no solution.

My question is hwo to tacke those problems from within catalyst. I no
that one should no intervene in the catalyst build process by hand.
how to manupulate it with config files to solve build issues?

below please find the latest fatal error which stops the spec file.

>>> Emerging (117 of 260) sys-apps/help2man-1.40.11
>>> Failed to emerge sys-apps/help2man-1.40.11, Log file:
>>>  '/var/tmp/portage/sys-apps/help2man-1.40.11/temp/build.log'
 * Package:    sys-apps/help2man-1.40.11
 * Repository: gentoo
 * Maintainer: base-system@g.o
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux multilib nls
userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Applying help2man-1.36.4-respect-LDFLAGS.patch ...
 [ ok ]
 * Applying help2man-1.38.4-linguas.patch ...
 [ ok ]
checking for perl... perl
checking for module Locale::gettext... no
checking for msgfmt... /usr/bin/msgfmt
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for library containing dlsym... -ldl
checking for library containing bindtextdomain... none required
configure: error: perl module Locale::gettext required

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/help2man-1.40.11/work/help2man-1.40.11/config.log
 * ERROR: sys-apps/help2man-1.40.11::gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 2226:  Called econf '--enable-nls'
 *   phase-helpers.sh, line  577:  Called die
 * The specific snippet of code:
 *               die "econf failed"
 *
 * If you need support, post the output of `emerge --info
'=sys-apps/help2man-1.40.11::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=sys-apps/help2man-1.40.11::gentoo'`.
 * The complete build log is located at
'/var/tmp/portage/sys-apps/help2man-1.40.11/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-apps/help2man-1.40.11/temp/environment'.
 * Working directory:
'/var/tmp/portage/sys-apps/help2man-1.40.11/work/help2man-1.40.11'
 * S: '/var/tmp/portage/sys-apps/help2man-1.40.11/work/help2man-1.40.11'

 * Messages for package media-fonts/dejavu-2.33:

 * The following fontconfig configuration files have been installed:
 *
 *   20-unhint-small-dejavu-sans-mono.conf
 *   20-unhint-small-dejavu-sans.conf
 *   20-unhint-small-dejavu-serif.conf
 *   57-dejavu-sans-mono.conf
 *   57-dejavu-sans.conf
 *   57-dejavu-serif.conf
 *
 * Use `eselect fontconfig` to enable/disable them.

 * Messages for package sci-astronomy/wcstools-3.8.7:

 * The following execs have been renamed to avoid colliding
 * with other packages:
 *  getdate -> wcsgetdate
 *  crlf    -> wcscrlf
 *  remap   -> wcsremap

 * Messages for package media-fonts/urw-fonts-2.4.9:

 * If you upgraded from urw-fonts-2.1-r2 some fonts will look a bit
 * different. Take a look at bug #208990 if interested.

 * Messages for package media-fonts/stix-fonts-1.0.0-r1:

 * The following fontconfig configuration files have been installed:
 *
 *   61-stix.conf
 *
 * Use `eselect fontconfig` to enable/disable them.

 * Messages for package app-portage/portage-utils-0.30:

 * This package will overwrite one or more files that may belong to other
 * packages (see list below).
 *
 * Detected file collision(s):
 *
 *     /etc/portage/postsync.d/q-reinitialize
 *     /etc/portage/bin/post_sync
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * None of the installed packages claim the file(s).
 *
 * Package 'app-portage/portage-utils-0.30' merged despite file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.
 * /etc/portage/postsync.d/q-reinitialize has been installed for convenience
 * If you wish for it to be automatically run at the end of every --sync:
 *    # chmod +x /etc/portage/postsync.d/q-reinitialize
 * Normally this should only take a few seconds to run but file systems
 * such as ext3 can take a lot longer.  To disable, simply do:
 *    # chmod -x /etc/portage/postsync.d/q-reinitialize

 * Messages for package x11-libs/libXi-1.7.2:

 * Some special keys and keyboard layouts may stop working.
 * To fix them, recompile xorg-server.

 * Messages for package sys-apps/help2man-1.40.11:

 * ERROR: sys-apps/help2man-1.40.11::gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 2226:  Called econf '--enable-nls'
 *   phase-helpers.sh, line  577:  Called die
 * The specific snippet of code:
 *               die "econf failed"
 *
 * If you need support, post the output of `emerge --info
'=sys-apps/help2man-1.40.11::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=sys-apps/help2man-1.40.11::gentoo'`.
 * The complete build log is located at
'/var/tmp/portage/sys-apps/help2man-1.40.11/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-apps/help2man-1.40.11/temp/environment'.
 * Working directory:
'/var/tmp/portage/sys-apps/help2man-1.40.11/work/help2man-1.40.11'
 * S: '/var/tmp/portage/sys-apps/help2man-1.40.11/work/help2man-1.40.11'

!!! catalyst: cmd() NON-zero return value from: Error in attempt to
build packages


!!! catalyst: stage4build aborting due to error.

--- Exeption running action sequence:build_packages
!!! catalyst: Error encountered during run of target stage4
Catalyst aborting....
lockfile does not exist
'/var/tmp/catalyst/tmp/default/stage4-core2-2013.12/.catalyst_lock'


As you can clearly see at the top the gettext  module is not available
for emerge at the time of building.

The spec file has this:

stage4/packages: dev-perl/Locale-gettext @astronomy


Theoretically the module should have been built before the @astronomy
set. And yet it is not there.

Let me mention that the stage4 file was modified to use the latest
snapshot 20140107.


If this was a regular system, not catalyst, I would diagnosed it
somehow. I just have no clue how to tackle it.
Could catalyst have build phases?
imagine this:
catalyst --phase stage4/packages -f specfile
catalyst --phase stage/fsscript -f specfile
catalyst --phase stage/rcadd -f specfile
catalyst --phase boot/kernel/gentoo/sources -f specfile

and so on and on.
this way one could step in,chroot into untarred 'phase', modify it and
then proceed?

this is just a thought. I am not a programmer, please do not take it
too seriously.

Thank for any input.
Ben



-- 
best regards
linforpros