public inbox for gentoo-releng-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: catalyst@hake.hppa.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa2.0/stage3.spec
Date: Mon, 04 Jun 2012 11:06:45 -0400	[thread overview]
Message-ID: <20120604150648.C466EE07F8@pigeon.gentoo.org> (raw)




checking for readline/history.h... yes
checking for readline in -lreadline... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libpcre.pc
config.status: creating libpcre16.pc
config.status: creating libpcreposix.pc
config.status: creating libpcrecpp.pc
config.status: creating pcre-config
config.status: creating pcre.h
config.status: creating pcre_stringpiece.h
config.status: creating pcrecpparg.h
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing script-chmod commands
config.status: executing delete-old-chartables commands

pcre-8.30 configuration summary:

    Install prefix .................. : /usr
    C preprocessor .................. : hppa2.0-unknown-linux-gnu-gcc -E
    C compiler ...................... : hppa2.0-unknown-linux-gnu-gcc
    C++ preprocessor ................ : hppa2.0-unknown-linux-gnu-g++ -E
    C++ compiler .................... : hppa2.0-unknown-linux-gnu-g++
    Linker .......................... : /usr/hppa2.0-unknown-linux-gnu/bin/ld
    C preprocessor flags ............ : 
    C compiler flags ................ : -O2 -pipe -march=2.0
    C++ compiler flags .............. : -O2 -pipe
    Linker flags .................... : -Wl,-O1 -Wl,--as-needed
    Extra libraries ................. : 

    Build 8 bit pcre library ........ : yes
    Build 16 bit pcre library ....... : no
    Build C++ library ............... : yes
    Enable JIT compiling support .... : yes
    Enable UTF-8/16 support ......... : yes
    Unicode properties .............. : yes
    Newline char/sequence ........... : lf
    \R matches only ANYCRLF ......... : no
    EBCDIC coding ................... : no
    Rebuild char tables ............. : no
    Use stack recursion ............. : yes
    POSIX mem threshold ............. : 10
    Internal link size .............. : 2
    Match limit ..................... : 10000000
    Match limit recursion ........... : 8192
    Build shared libs ............... : yes
    Build static libs ............... : no
    Use JIT in pcregrep ............. : yes
    Buffer size for pcregrep ........ : 20480
    Link pcregrep with libz ......... : yes
    Link pcregrep with libbz2 ....... : yes
    Link pcretest with libreadline .. : yes

rm -f pcre_chartables.c
ln -s ./pcre_chartables.c.dist pcre_chartables.c
make  all-am
make[1]: Entering directory `/var/tmp/portage/dev-libs/libpcre-8.30-r2/work/pcre-8.30'
  CC     pcre_byte_order.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_byte_order.lo pcre_byte_order.c
  CC     pcre_compile.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_compile.lo pcre_compile.c
  CC     pcre_config.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_config.lo pcre_config.c
  CC     pcre_dfa_exec.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_dfa_exec.lo pcre_dfa_exec.c
  CC     pcre_exec.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_exec.lo pcre_exec.c
  CC     pcre_fullinfo.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_fullinfo.lo pcre_fullinfo.c
  CC     pcre_get.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_get.lo pcre_get.c
  CC     pcre_globals.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_globals.lo pcre_globals.c
  CC     pcre_jit_compile.lo
/bin/sh ./libtool --silent --tag=CC   --mode=compile hppa2.0-unknown-linux-gnu-gcc -DHAVE_CONFIG_H -I.     -O2 -pipe -march=2.0 -c -o pcre_jit_compile.lo pcre_jit_compile.c
pcre_jit_compile.c:65:2: error: #error Unsupported architecture
make[1]: *** [pcre_jit_compile.lo] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-libs/libpcre-8.30-r2/work/pcre-8.30'
make: *** [all] Error 2
 * ERROR: dev-libs/libpcre-8.30-r2 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of 'emerge --info =dev-libs/libpcre-8.30-r2',
 * the complete build log and the output of 'emerge -pqv =dev-libs/libpcre-8.30-r2'.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libpcre-8.30-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libpcre-8.30-r2/temp/environment'.
 * S: '/var/tmp/portage/dev-libs/libpcre-8.30-r2/work/pcre-8.30'

 * 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.8:

 * /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-apps/coreutils-8.14:

 * Make sure you run 'hash -r' in your active shells.
 * You should also re-source your shell settings for LS_COLORS
 *   changes, such as: source /etc/profile

 * 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 sys-apps/man-pages-3.40:

 * If you don't have a makewhatis cronjob, then you
 * should update the whatis database yourself:
 *  # makewhatis -u

 * Messages for package dev-libs/libpcre-8.30-r2:

 * ERROR: dev-libs/libpcre-8.30-r2 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of 'emerge --info =dev-libs/libpcre-8.30-r2',
 * the complete build log and the output of 'emerge -pqv =dev-libs/libpcre-8.30-r2'.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libpcre-8.30-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libpcre-8.30-r2/temp/environment'.
 * S: '/var/tmp/portage/dev-libs/libpcre-8.30-r2/work/pcre-8.30'

!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1196, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/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/lib/catalyst/catalyst", line 206, in build_target
    mytarget.run()
File "modules/generic_stage_target.py", line 1256, in run
    apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1201, 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 '/usr/local/catalyst/tmp/default/stage3-hppa2.0-20120601/.catalyst_lock'



Full build log at /tmp/catalyst-auto.15813/log/hppa2.0_stage3.log



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 15:06 catalyst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-26 12:06 [gentoo-releng-autobuilds] [hppa-auto] Catalyst fatal build error - hppa2.0/stage3.spec catalyst
2018-02-23  3:33 catalyst
2018-04-08 19:45 catalyst
2018-06-09 17:26 catalyst
2018-07-18  6:30 catalyst
2018-08-03 17:16 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=20120604150648.C466EE07F8@pigeon.gentoo.org \
    --to=catalyst@hake.hppa.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