[gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage3.spec

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] [x86-auto] Catalyst fatal build error - stage3.spec
Date: Tue, 27 Dec 2011 09:05:06 +0000 (UTC)	[thread overview]
Message-ID: <20111227090507.047F5143802@poseidon.amd64.dev.gentoo.org> (raw)

ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0
ls: ignoring invalid width in environment variable COLUMNS: 0

THIS PACKAGE SEEMS TO BE INCOMPLETE.

You have the option of continuing the configuration process, despite the
distinct possibility that your kit is damaged, by typing 'y'es.  If you
do, don't blame me if something goes wrong.  I advise you to type 'n'o
and contact the author (perlbug@perl.org).

Continue? [n] ABORTING...
 * ERROR: dev-lang/perl-5.12.4-r1 failed (configure phase):
 *   Unable to configure
 * 
 * Call stack:
 *     ebuild.sh, line  75:  Called src_configure
 *   environment, line 2697:  Called die
 * The specific snippet of code:
 *       sh Configure -des -Duseshrplib -Darchname="${myarch}" -Dcc="$(tc-getCC)" -Doptimize="${CFLAGS}" -Dldflags="${LDFLAGS}" -Dprefix='/usr' -Dsiteprefix='/usr' -Dvendorprefix='/usr' -Dscriptdir='/usr/bin' -Dprivlib="${PRIV_LIB}" -Darchlib="${ARCH_LIB}" -Dsitelib="${SITE_LIB}" -Dsitearch="${SITE_ARCH}" -Dvendorlib="${VENDOR_LIB}" -Dvendorarch="${VENDOR_ARCH}" -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/share/man/man1 -Dsiteman3dir=/usr/share/man/man3 -Dvendorman1dir=/usr/share/man/man1 -Dvendorman3dir=/usr/share/man/man3 -Dman1ext='1' -Dman3ext='3pm' -Dlibperl="${LIBPERL}" -Dlocincpth=' ' -Duselargefiles -Dd_semctl_semun -Dcf_by='Gentoo' -Dmyhostname='localhost' -Dperladmin='root@localhost' -Dinstallusrbinperl='n' -Ud_csh -Uusenm "${myconf[@]}" || die "Unable to configure"
 * 
 * If you need support, post the output of 'emerge --info =dev-lang/perl-5.12.4-r1',
 * the complete build log and the output of 'emerge -pqv =dev-lang/perl-5.12.4-r1'.
 * The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.12.4-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.12.4-r1/temp/environment'.
 * S: '/var/tmp/portage/dev-lang/perl-5.12.4-r1/work/perl-5.12.4'

 * Messages for package sys-libs/timezone-data-2011l:

 * You do not have TIMEZONE set in /etc/timezone.
 * Skipping auto-update of /etc/localtime.

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

 * /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-libs/glibc-2.13-r4:

 * Generating all locales; edit /etc/locale.gen to save time/space

 * Messages for package sys-fs/udev-164-r2:

 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * 
 * udev-164 does not support Linux kernel before version 2.6.25!
 * For a reliable udev, use at least kernel 2.6.27
 * 
 * If after the udev update removable devices or CD/DVD drives
 * stop working, try re-emerging HAL before filling a bug report
 * 
 * persistent-net does assigning fixed names to network devices.
 * If you have problems with the persistent-net rules,
 * just delete the rules file
 * 	rm /etc/udev/rules.d/70-persistent-net.rules
 * and then reboot.
 * 
 * This may however number your devices in a different way than they are now.
 * 
 * If you build an initramfs including udev, then please
 * make sure that the /sbin/udevadm binary gets included,
 * and your scripts changed to use it,as it replaces the
 * old helper apps udevinfo, udevtrigger, ...
 * 
 * mount options for directory /dev are no longer
 * set in /etc/udev/udev.conf, but in /etc/fstab
 * as for other directories.
 * 
 * If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
 * then please migrate over to using the device names
 * /dev/md*, /dev/loop* and /dev/ram*.
 * The devfs-compat rules have been removed.
 * For reference see Bug #269359.
 * 
 * Rules for /dev/hd* devices have been removed
 * Please migrate to libata.
 * 
 * For more information on udev on Gentoo, writing udev rules, and
 *          fixing known issues visit:
 *          http://www.gentoo.org/doc/en/udev-guide.xml

 * 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 dev-lang/perl-5.12.4-r1:

 * ERROR: dev-lang/perl-5.12.4-r1 failed (configure phase):
 *   Unable to configure
 * 
 * Call stack:
 *     ebuild.sh, line  75:  Called src_configure
 *   environment, line 2697:  Called die
 * The specific snippet of code:
 *       sh Configure -des -Duseshrplib -Darchname="${myarch}" -Dcc="$(tc-getCC)" -Doptimize="${CFLAGS}" -Dldflags="${LDFLAGS}" -Dprefix='/usr' -Dsiteprefix='/usr' -Dvendorprefix='/usr' -Dscriptdir='/usr/bin' -Dprivlib="${PRIV_LIB}" -Darchlib="${ARCH_LIB}" -Dsitelib="${SITE_LIB}" -Dsitearch="${SITE_ARCH}" -Dvendorlib="${VENDOR_LIB}" -Dvendorarch="${VENDOR_ARCH}" -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/share/man/man1 -Dsiteman3dir=/usr/share/man/man3 -Dvendorman1dir=/usr/share/man/man1 -Dvendorman3dir=/usr/share/man/man3 -Dman1ext='1' -Dman3ext='3pm' -Dlibperl="${LIBPERL}" -Dlocincpth=' ' -Duselargefiles -Dd_semctl_semun -Dcf_by='Gentoo' -Dmyhostname='localhost' -Dperladmin='root@localhost' -Dinstallusrbinperl='n' -Ud_csh -Uusenm "${myconf[@]}" || die "Unable to configure"
 * 
 * If you need support, post the output of 'emerge --info =dev-lang/perl-5.12.4-r1',
 * the complete build log and the output of 'emerge -pqv =dev-lang/perl-5.12.4-r1'.
 * The complete build log is located at '/var/tmp/portage/dev-lang/perl-5.12.4-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/perl-5.12.4-r1/temp/environment'.
 * S: '/var/tmp/portage/dev-lang/perl-5.12.4-r1/work/perl-5.12.4'

!!! 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/x86-dev/tmp/default/stage3-i486-20111227/.catalyst_lock'

Full build log at /tmp/catalyst-auto.11109/log/stage3.log

next             reply	other threads:[~2011-12-27  9:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27  9:05 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15  2:57 [gentoo-releng-autobuilds] [x86-auto] Catalyst fatal build error - stage3.spec catalyst
2020-05-13  4:40 catalyst
2020-03-17 14:07 catalyst
2018-04-18  4:11 catalyst
2018-04-11  4:12 catalyst
2018-04-04  4:11 catalyst
2018-02-21  4:27 catalyst
2018-02-14  4:33 catalyst
2018-02-07  5:21 catalyst
2018-01-31  5:39 catalyst
2018-01-17  5:14 catalyst
2018-01-10  3:43 catalyst
2018-01-03  5:23 catalyst
2017-12-27 23:08 catalyst
2017-12-27  5:42 catalyst
2017-12-20  5:40 catalyst
2015-11-25  5:49 catalyst
2015-07-29  6:05 catalyst
2015-03-18  5:28 catalyst
2014-12-10  6:38 catalyst
2012-08-28 10:46 catalyst
2012-01-17 11:08 catalyst
2011-12-20  9:06 catalyst
2011-05-10  9:04 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=20111227090507.047F5143802@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