home ~ # cat /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/temp/build.log * CPV: dev-db/virtuoso-odbc-6.1.2 * REPO: gentoo * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU >>> Unpacking source... >>> Unpacking virtuoso-opensource-6.1.2.tar.gz to /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work >>> Unpacking VOS-genpatches-6.1.2.tar.bz2 to /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work >>> Source unpacked in /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work >>> Preparing source in /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work/virtuoso-opensource-6.1.2 ... * Applying various patches (bugfixes/updates) ... * 01_flatten-subdirs.patch ... [ ok ] * 02_preserve-cflags.patch ... [ ok ] * 03_ignore-misc-files.patch ... [ ok ] * Done with patching * Running eautoreconf in '/var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work/virtuoso-opensource-6.1.2' ... * Running aclocal -I binsrc/config ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal -I binsrc/config ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ ok ] * Running elibtoolize in: virtuoso-opensource-6.1.2/binsrc/config/ * Applying portage-2.2.patch ... * Applying sed-1.5.6.patch ... * Applying as-needed-2.2.6.patch ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-db/virtuoso-odbc-6.1.2/work/virtuoso-opensource-6.1.2 ... * econf: updating virtuoso-opensource-6.1.2/binsrc/config/config.sub with /usr/share/gnuconfig/config.sub * econf: updating virtuoso-opensource-6.1.2/binsrc/config/config.guess with /usr/share/gnuconfig/config.guess ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-layout=gentoo --localstatedir=/var --enable-shared --with-pthreads --without-internal-zlib --disable-static --without-iodbc configure: loading site script /usr/share/config.site configure: loading site script /usr/share/crossdev/include/site/linux checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu creating config.nice checking for Virtuoso installation layout... Gentoo checking for cpp... /usr/bin/cpp 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 style of include used by make... GNU checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3 checking whether x86_64-pc-linux-gnu-gcc and cc understand -c and -o together... yes checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking how to print strings... printf checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes checking how to run the C preprocessor... /usr/bin/cpp checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether byte ordering is bigendian... no checking for an ANSI C-conforming const... yes checking for inline... inline checking whether char is unsigned... no checking for long double with more range or precision than double... yes checking size of char... 1 checking size of short... 2 checking size of unsigned... 4 checking size of int... 4 checking size of long... 8 checking size of long long... 8 checking size of float... 4 checking size of double... 8 checking size of long double... 16 checking size of char *... 8 checking size of void *... 8 checking whether make sets $(MAKE)... (cached) yes checking whether ln -s works... yes checking for bison... bison -y checking for htmldoc... no checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for flex... /usr/bin/flex checking for gawk... /usr/bin/gawk checking for gperf... /usr/bin/gperf checking for perl... /usr/bin/perl checking for python... /usr/bin/python checking for ruby... /usr/bin/ruby checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump checking how to recognize dependent libraries... pass_all checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok checking for dlfcn.h... yes checking for objdir... .libs checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for ANSI C header files... (cached) yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking whether sys/types.h defines makedev... yes checking whether stat file-mode macros are broken... no checking whether time.h and sys/time.h may both be included... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for unistd.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking sys/timeb.h usability... yes checking sys/timeb.h presence... yes checking for sys/timeb.h... yes checking sys/sockio.h usability... no checking sys/sockio.h presence... no checking for sys/sockio.h... no checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking wctype.h usability... yes checking wctype.h presence... yes checking for wctype.h... yes checking for pwd.h... (cached) yes checking grp.h usability... yes checking grp.h presence... yes checking for grp.h... yes checking sys/mman.h usability... yes checking sys/mman.h presence... yes checking for sys/mman.h... yes checking for mode_t... yes checking for off_t... yes checking for pid_t... yes checking return type of signal handlers... void checking for size_t... yes checking for uid_t in sys/types.h... yes checking for struct stat.st_blksize... yes checking for struct stat.st_blocks... yes checking for struct stat.st_rdev... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for ptrdiff_t... yes checking for tm_gmtoff in struct tm... yes checking for tm_tzadj in struct tm... no checking for t_open in -lnsl... no checking for gethostbyname in -linet... no checking for socket in -lsocket... no checking for cos in -lm... yes checking for working memcmp... yes checking for unistd.h... (cached) yes checking for working chown... yes checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... * The ebuild phase 'configure' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. home ~ # cat /var/tmp/portage/app-admin/system-config-printer-common-1.2.4/temp/build.log * CPV: app-admin/system-config-printer-common-1.2.4 * REPO: gentoo * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU >>> Unpacking source... >>> Unpacking system-config-printer-1.2.4.tar.xz to /var/tmp/portage/app-admin/system-config-printer-common-1.2.4/work >>> Source unpacked in /var/tmp/portage/app-admin/system-config-printer-common-1.2.4/work >>> Preparing source in /var/tmp/portage/app-admin/system-config-printer-common-1.2.4/work/system-config-printer-1.2.4 ... * Applying system-config-printer-common-1.2.2-split.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/app-admin/system-config-printer-common-1.2.4/work/system-config-printer-1.2.4' ... * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running automake --add-missing --copy ... [ ok ] >>> Source prepared. ebuild-ipc timed out after 40 seconds * The ebuild phase 'prepare' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. home ~ # cat /var/tmp/portage/sci-libs/clapack-3.2.1-r3/temp/build.log * CPV: sci-libs/clapack-3.2.1-r3 * REPO: kde * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU >>> Unpacking source... >>> Unpacking clapack-3.2.1-CMAKE.tgz to /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work >>> Source unpacked in /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work >>> Preparing source in /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work/clapack-3.2.1-CMAKE ... * Applying clapack-3.2.1-noblasf2c.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work/clapack-3.2.1-CMAKE ... >>> Working in BUILD_DIR: "/var/tmp/portage/sci-libs/clapack-3.2.1-r3/work/clapack-3.2.1_build" cmake -C /var/tmp/portage/sci-libs/clapack-3.2.1-r3/temp/gentoo_common_config.cmake -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_TESTS=OFF -DCMAKE_BUILD_TYPE=Gentoo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/sci-libs/clapack-3.2.1-r3/temp/gentoo_rules.cmake /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work/clapack-3.2.1-CMAKE loading initial cache file /var/tmp/portage/sci-libs/clapack-3.2.1-r3/temp/gentoo_common_config.cmake -- The C compiler identification is GNU -- Check for working C compiler: /usr/lib/ccache/bin/x86_64-pc-linux-gnu-gcc -- Check for working C compiler: /usr/lib/ccache/bin/x86_64-pc-linux-gnu-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- <<< Gentoo configuration >>> Build type Gentoo Install path /usr Compiler flags: C -march=core2 -mtune=core2 -mcx16 -msahf -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -O2 -pipe -fPIC C++ Linker flags: Executable -Wl,-O1 -Wl,--as-needed -Wl,--sort-common Module -Wl,-O1 -Wl,--as-needed -Wl,--sort-common Shared -Wl,-O1 -Wl,--as-needed -Wl,--sort-common -- Configuring done -- Generating done -- Build files have been written to: /var/tmp/portage/sci-libs/clapack-3.2.1-r3/work/clapack-3.2.1_build >>> Source configured. ebuild-ipc timed out after 40 seconds * The ebuild phase 'configure' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly.