Bug 434646 – librsvg-2.36.3 fails to configure

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Alex Barker 2012-09-10 20:02:13 UTC]

>>> Emerging (1 of 1) gnome-base/librsvg-2.36.3
 * librsvg-2.36.3.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                  [ ok ]
 * introspection.m4.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                   [ ok ]
>>> Unpacking source...
>>> Unpacking librsvg-2.36.3.tar.xz to /var/tmp/portage/gnome-base/librsvg-2.36.3/work
>>> Unpacking introspection.m4.bz2 to /var/tmp/portage/gnome-base/librsvg-2.36.3/work
>>> Source unpacked in /var/tmp/portage/gnome-base/librsvg-2.36.3/work
>>> Preparing source in /var/tmp/portage/gnome-base/librsvg-2.36.3/work/librsvg-2.36.3 ...
 * Applying librsvg-2.36.0-rsvg-view-automagic.patch ...                                                       [ ok ]
 * Running eautoreconf in '/var/tmp/portage/gnome-base/librsvg-2.36.3/work/librsvg-2.36.3' ...
 * Skipping 'gtkdocize --copy' due gtkdocize not installed
 * Running libtoolize --install --copy --force --automake ...                                                  [ ok ]
 * Running aclocal ...                                                                                         [ ok ]
 * Running autoconf ...                                                                                        [ ok ]
 * Running autoheader ...                                                                                      [ ok ]
 * Running automake --add-missing --copy ...                                                                   [ !! ]

 * Failed Running automake !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/gnome-base/librsvg-2.36.3/temp/automake.out

 * ERROR: gnome-base/librsvg-2.36.3 failed (prepare phase):
 *   Failed Running automake !
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 3359:  Called eautoreconf
 *   environment, line  854:  Called eautomake
 *   environment, line  807:  Called autotools_run_tool 'automake' '--add-missing' '--copy'
 *   environment, line  612:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=gnome-base/librsvg-2.36.3'`,
 * the complete build log and the output of `emerge -pqv '=gnome-base/librsvg-2.36.3'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 214: wait: `Failed Running automake !': not a pid or valid job spec
 * The complete build log is located at '/var/tmp/portage/gnome-base/librsvg-2.36.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-base/librsvg-2.36.3/temp/environment'.
 * Working directory: '/var/tmp/portage/gnome-base/librsvg-2.36.3/work/librsvg-2.36.3'
 * S: '/var/tmp/portage/gnome-base/librsvg-2.36.3/work/librsvg-2.36.3'


Reproducible: Always

[Comment 1 Alex Barker 2012-09-10 20:02:53 UTC]

# cat /var/tmp/portage/gnome-base/librsvg-2.36.3/temp/automake.out
***** automake *****
***** PWD: /var/tmp/portage/gnome-base/librsvg-2.36.3/work/librsvg-2.36.3
***** automake --add-missing --copy

Makefile.am:255: ENABLE_VAPIGEN does not appear in AM_CONDITIONAL

[Comment 2 Moritz Schlarb 2012-09-10 20:28:03 UTC]

Confirming that on ~x86.

[Comment 3 genfool 2012-09-10 22:32:12 UTC]

same error here on ~amd64 portage   2.2.0_alpha125

[Comment 4 Alex Barker 2012-09-10 23:07:05 UTC]

I just re-synced and this appears to have fixed its self.  Can anyone else confirm?

[Comment 5 Rafał Mużyło 2012-09-11 01:12:47 UTC]

*** This bug has been marked as a duplicate of bug 434544 ***