public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@poseidon.amd64.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage3-nomultilib.spec
Date: Thu,  7 Jun 2012 22:04:07 +0000 (UTC)	[thread overview]
Message-ID: <20120607220407.AD2011436BA@poseidon.amd64.dev.gentoo.org> (raw)




>>> Emerging (69 of 119) sys-apps/less-444
>>> Installing (69 of 119) sys-apps/less-444
>>> Emerging (70 of 119) virtual/pager-0
>>> Installing (70 of 119) virtual/pager-0
>>> Emerging (71 of 119) sys-libs/gpm-1.20.6
>>> Installing (71 of 119) sys-libs/gpm-1.20.6
>>> Emerging (72 of 119) sys-libs/ncurses-5.9-r2
>>> Installing (72 of 119) sys-libs/ncurses-5.9-r2
>>> Emerging (73 of 119) sys-process/procps-3.2.8_p11
>>> Installing (73 of 119) sys-process/procps-3.2.8_p11
>>> Emerging (74 of 119) sys-apps/attr-2.4.46-r1
>>> Installing (74 of 119) sys-apps/attr-2.4.46-r1
>>> Emerging (75 of 119) sys-apps/acl-2.2.51
>>> Installing (75 of 119) sys-apps/acl-2.2.51
>>> Emerging (76 of 119) virtual/acl-0-r1
>>> Installing (76 of 119) virtual/acl-0-r1
>>> Emerging (77 of 119) sys-devel/gettext-0.18.1.1-r1
>>> Installing (77 of 119) sys-devel/gettext-0.18.1.1-r1
>>> Emerging (78 of 119) sys-apps/sed-4.2.1
>>> Installing (78 of 119) sys-apps/sed-4.2.1
>>> Emerging (79 of 119) sys-devel/bison-2.4.3
>>> Installing (79 of 119) sys-devel/bison-2.4.3
>>> Emerging (80 of 119) dev-perl/Locale-gettext-1.50.0
>>> Installing (80 of 119) dev-perl/Locale-gettext-1.50.0
>>> Emerging (81 of 119) sys-apps/help2man-1.40.8
>>> Installing (81 of 119) sys-apps/help2man-1.40.8
>>> Emerging (82 of 119) sys-devel/automake-1.11.1
>>> Installing (82 of 119) sys-devel/automake-1.11.1
>>> Emerging (83 of 119) sys-devel/libtool-2.4-r1
>>> Installing (83 of 119) sys-devel/libtool-2.4-r1
>>> Emerging (84 of 119) sys-apps/groff-1.21
>>> Installing (84 of 119) sys-apps/groff-1.21
>>> Emerging (85 of 119) sys-apps/man-1.6g
>>> Installing (85 of 119) sys-apps/man-1.6g
>>> Emerging (86 of 119) virtual/man-0
>>> Installing (86 of 119) virtual/man-0
>>> Emerging (87 of 119) sys-apps/man-pages-posix-2003a
>>> Installing (87 of 119) sys-apps/man-pages-posix-2003a
>>> Emerging (88 of 119) sys-devel/flex-2.5.35_p10
>>> Installing (88 of 119) sys-devel/flex-2.5.35_p10
>>> Emerging (89 of 119) dev-libs/glib-2.30.3
>>> Failed to emerge dev-libs/glib-2.30.3, Log file:
>>>  '/var/tmp/portage/dev-libs/glib-2.30.3/temp/build.log'
 * Package:    dev-libs/glib-2.30.3
 * Repository: gentoo
 * USE:        amd64 elibc_glibc kernel_linux static-libs userland_GNU
 * FEATURES:   ccache sandbox
`/var/tmp/portage/dev-libs/glib-2.30.3/work/pkg-config-0.26/pkg.m4' -> `/var/tmp/portage/dev-libs/glib-2.30.3/work/pkg.m4'
 * Applying glib-2.30.2-missing-decls.patch ...
 [ ok ]
 * Applying glib-2.12.12-fbsd.patch ...
 [ ok ]
 * Applying glib-2.30.3-assert-test-failure.patch ...
 [ ok ]
 * Applying glib-2.30.1-external-gdbus-codegen.patch ...
 [ ok ]
 * Applying glib-2.30.1-homedir-env.patch ...
 [ ok ]
 * Applying glib-2.30.2-machine-id.patch ...
 [ ok ]
 * Applying glib-2.30.3-closure-64bit-be.patch ...
 [ ok ]
 * Running eautoreconf in '/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3' ...
 * Running gtkdocize --copy ...
 [ !! ]

 * Failed Running gtkdocize !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-libs/glib-2.30.3/temp/gtkdocize.out

 * ERROR: dev-libs/glib-2.30.3 failed (prepare phase):
 *   Failed Running gtkdocize !
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 6148:  Called eautoreconf
 *   environment, line 1605:  Called autotools_run_tool 'gtkdocize' '--copy'
 *   environment, line 1383:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of 'emerge --info =dev-libs/glib-2.30.3',
 * the complete build log and the output of 'emerge -pqv =dev-libs/glib-2.30.3'.
 * The complete build log is located at '/var/tmp/portage/dev-libs/glib-2.30.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.30.3/temp/environment'.
 * S: '/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3'
 * Messages for package sys-libs/timezone-data-2012c:
 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.
 * Messages for package app-portage/portage-utils-0.10:
 * /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 sys-apps/baselayout-2.1-r1:
 * You should reboot the system now to get /run mounted with tmpfs!
 * Messages for package sys-libs/glibc-2.14.1-r3:
 * Generating all locales; edit /etc/locale.gen to save time/space
 * Messages for package sys-libs/gdbm-1.8.3-r4:
 * 32bit systems might have to rebuild all gdbm databases due to
 * LFS changes in the gdbm format.  You can either delete the db
 * and regenerate it from scratch, or use the converter:
 * http://bugs.gentoo.org/attachment.cgi?id=215326
 * 
 * See this comment for information on how to use it:
 * http://bugs.gentoo.org/299390#c15
 * 
 * You should be able to locate most gdbm db's on your system with:
 * find /etc /var -type f -exec file {} + | grep 'GNU dbm 1.x or ndbm database'
 * 
 * You could also try using this helper script:
 * http://bugs.gentoo.org/attachment.cgi?id=222581
 * Messages for package sys-apps/util-linux-2.20.1-r1:
 * The agetty util now clears the terminal by default.  You
 * might want to add --noclear to your /etc/inittab lines.
 * Messages for package sys-devel/gcc-4.5.3-r2:
 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.
 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml
 * Messages for package sys-apps/portage-2.1.10.49:
 * If you are an ebuild developer and you plan to commit ebuilds
 * with this system then please install dev-python/pycrypto or
 * enable the ssl USE flag for >=dev-lang/python-2.6 in order
 * to enable RMD160 hash support.
 * See bug #198398 for more information.
 * Messages for package app-misc/ca-certificates-20111025:
 * You should run update-ca-certificates manually after etc-update
 * Messages for package dev-libs/glib-2.30.3:
 * Failed Running gtkdocize !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-libs/glib-2.30.3/temp/gtkdocize.out
 * ERROR: dev-libs/glib-2.30.3 failed (prepare phase):
 *   Failed Running gtkdocize !
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 6148:  Called eautoreconf
 *   environment, line 1605:  Called autotools_run_tool 'gtkdocize' '--copy'
 *   environment, line 1383:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of 'emerge --info =dev-libs/glib-2.30.3',
 * the complete build log and the output of 'emerge -pqv =dev-libs/glib-2.30.3'.
 * The complete build log is located at '/var/tmp/portage/dev-libs/glib-2.30.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.30.3/temp/environment'.
 * S: '/var/tmp/portage/dev-libs/glib-2.30.3/work/glib-2.30.3'





















!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1207, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib64/catalyst/modules/catalyst_support.py", line 542, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build aborting due to error.

Traceback (most recent call last):
File "/usr/lib64/catalyst/catalyst", line 209, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1263, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1212, in run_local
    raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage3
Catalyst aborting....
lockfile does not exist '/release/buildroot/amd64-dev/tmp/hardened/stage3-amd64-hardened+nomultilib-20120607/.catalyst_lock'



Full build log at /tmp/catalyst-auto.29490/log/hardened_stage3-nomultilib.log



             reply	other threads:[~2012-06-07 22:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 22:04 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-24 13:52 [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage3-nomultilib.spec catalyst
2020-12-22  3:48 catalyst
2017-12-23 18:53 catalyst
2015-11-26  8:54 catalyst
2015-07-16 15:12 catalyst
2015-06-16  7:11 catalyst
2015-03-31  0:01 catalyst
2012-08-17  8:22 catalyst
2012-08-10 15:01 catalyst
2012-07-21  1:49 catalyst
2012-07-06  9:04 catalyst
2012-06-29  8:07 catalyst
2012-04-20  9:14 catalyst
2012-04-13  9:22 catalyst
2012-04-06  9:18 catalyst
2012-03-30  9:20 catalyst
2012-03-23  8:35 catalyst
2011-05-20  0:37 catalyst
2011-05-13  0:59 catalyst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120607220407.AD2011436BA@poseidon.amd64.dev.gentoo.org \
    --to=catalyst@poseidon.amd64.dev.gentoo.org \
    --cc=gentoo-releng-autobuilds@lists.gentoo.org \
    --cc=releng@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox