Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
libjpeg-turbo emerge failed?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
kbzium
Tux's lil' helper
Tux's lil' helper


Joined: 31 Jul 2012
Posts: 146

PostPosted: Sun Oct 14, 2012 4:24 pm    Post subject: libjpeg-turbo emerge failed? Reply with quote

Hi there,

I came across some major problem when installing gentoo on my laptop. The thing is I'm about to configure X server, but I must install video drivers first. So I tried several times to install ati-drivers with no luck - every time I do this it stops at media-libs/libjpeg-turbo-1.2.1: it says: "emake failed".

Same with emerge -1auDN system. I'd like to have hybrid graphics, intel HD2000 + radeon but I'm wondering if it's possible since ATI drivers cannot be installed with DRM on, and Intel HD graphics support seem to require it to work... I'm stuck.

Any ideas?
Back to top
View user's profile Send private message
phajdan.jr
Developer
Developer


Joined: 23 Mar 2006
Posts: 1767
Location: Poland

PostPosted: Sun Oct 14, 2012 5:59 pm    Post subject: Reply with quote

Please post the build log and emerge --info .
_________________
http://phajdan-jr.blogspot.com/
Back to top
View user's profile Send private message
kbzium
Tux's lil' helper
Tux's lil' helper


Joined: 31 Jul 2012
Posts: 146

PostPosted: Sun Oct 14, 2012 7:50 pm    Post subject: Reply with quote

emerge --info
Code:
Portage 2.1.11.9 (default/linux/amd64/10.0/desktop, gcc-4.5.4, glibc-2.15-r2, 3.4.9-gentoo x86_64)                                   
=================================================================                                                                     
System uname: Linux-3.4.9-gentoo-x86_64-Intel-R-_Core-TM-_i5-2410M_CPU_@_2.30GHz-with-gentoo-2.1                                     
Timestamp of tree: Sun, 14 Oct 2012 10:45:01 +0000                                                                                   
app-shells/bash:          4.2_p37
dev-lang/python:          2.7.3-r2, 3.2.3
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.11.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.5.4
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r3
sys-kernel/linux-headers: 3.4-r2 (virtual/os-headers)
sys-libs/glibc:           2.15-r2
Repositories: gentoo
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -02 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/ter
minfo"
CXXFLAGS="-march=native -02 -pipe"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--jobs 4 --load-average 16"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuil
d-head protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j5 -l16"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable
 --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cli consolekit cracklib crypt cups cxx dbus dri dts
dvd dvdr emboss encode exif fam firefox flac fortran gdbm gif gpm gtk iconv ipv6 jpeg lcms ldap libnotify mad mmx mng modules mp3 mp4
mpeg mudflap multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf png policykit ppds pppd qt3support qt4 readline sdl sessio
n spell sse sse2 sse4_1 sse4_2 ssl ssse3 startup-notification svg tcpd tiff truetype udev udisks unicode upower usb vorbis wxwidgets x
264 xcb xml xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 f
m801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix
 dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm
softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_de
fault authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_loc
k deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic nego
tiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage
tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_P
ROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore
rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev synaptics keyboard mouse" KERNEL="linux" LCD_DE
VICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-mini
mizer" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="fglrx" XTABL
ES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark i
pmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_R
SYNC_EXTRA_OPTS, USE_PYTHON


log
Code:
>>> Messages generated by process 1890 on 2012-10-14 18:52:08 CEST for package sys-libs/mtdev-1.1.2:

ERROR: unpack
Fetch failed for 'sys-libs/mtdev-1.1.2', Log file:
 'var/log/portage/sys-libs:mtdev-1.1.2:20121014-165208.log'

>>> Messages generated by process 3135 on 2012-10-14 18:54:49 CEST for package x11-libs/pixman-0.26.0:

ERROR: configure
ERROR: x11-libs/pixman-0.26.0 failed (configure phase):
  econf failed

Call stack:
         ebuild.sh, line   85:  Called src_configure
       environment, line 3503:  Called xorg-2_src_configure
       environment, line 4375:  Called autotools-utils_src_configure
       environment, line  698:  Called econf '--docdir=/usr/share/doc/pixman-0.26.0' '--enable-shared' '--disable-static' '--enable-mm
x' '--enable-sse2' '--disable-vmx' '--disable-arm-neon' '--disable-arm-iwmmxt' '--disable-gtk'
  phase-helpers.sh, line  467:  Called die
The specific snippet of code:
                        die "econf failed"

If you need support, post the output of `emerge --info '=x11-libs/pixman-0.26.0'`,
the complete build log and the output of `emerge -pqv '=x11-libs/pixman-0.26.0'`.
The complete build log is located at 'var/log/portage/x11-libs:pixman-0.26.0:20121014-165442.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/environment'.
Working directory: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0_build'
S: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0'

>>> Messages generated by process 20492 on 2012-10-14 19:01:02 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-170040.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 20492 on 2012-10-14 19:01:10 CEST for package sys-apps/pciutils-3.1.10:

LOG: postinst
The 'pcimodules' program has been replaced by 'lspci -k'

The 'network-cron' USE flag is gone; if you want a more up-to-date
pci.ids file, you should use sys-apps/hwids-99999999 (live ebuild).

>>> Messages generated by process 30648 on 2012-10-14 19:05:47 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-170522.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 14293 on 2012-10-14 19:09:25 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-170857.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 31107 on 2012-10-14 19:12:24 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-171159.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 31107 on 2012-10-14 19:12:46 CEST for package app-text/libpaper-1.1.24-r1:

LOG: postinst
run "paperconf -p letter" as root to use letter-pagesizes
or paperconf with normal user privileges.

>>> Messages generated by process 29565 on 2012-10-14 19:17:05 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-171638.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 29565 on 2012-10-14 19:17:10 CEST for package dev-db/sqlite-3.7.13:

ERROR: test
ERROR: dev-db/sqlite-3.7.13 failed (test phase):
  filter-bash-environment.py failed

Call stack:
           ebuild.sh, line 708:  Called ebuild_main 'test'
  phase-functions.sh, line 991:  Called filter_readonly_variables '--filter-features'
  phase-functions.sh, line 140:  Called die
The specific snippet of code:
        "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-e
nvironment.py failed"

If you need support, post the output of `emerge --info '=dev-db/sqlite-3.7.13'`,
the complete build log and the output of `emerge -pqv '=dev-db/sqlite-3.7.13'`.
The complete build log is located at 'var/log/portage/dev-db:sqlite-3.7.13:20121014-171643.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-db/sqlite-3.7.13/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-db/sqlite-3.7.13/temp/environment'.
Working directory: '/var/tmp/portage/dev-db/sqlite-3.7.13/work/sqlite-autoconf-3071300'
S: '/var/tmp/portage/dev-db/sqlite-3.7.13/work/sqlite-autoconf-3071300'

>>> Messages generated by process 1719 on 2012-10-14 19:30:27 CEST for package x11-drivers/ati-drivers-12.6:

WARN: pretend
You have DRM support built in to the kernel
Direct rendering will not work.

>>> Messages generated by process 1719 on 2012-10-14 19:30:27 CEST for package sys-power/acpid-2.0.16-r1:

ERROR: unpack
Fetch failed for 'sys-power/acpid-2.0.16-r1', Log file:
 'var/log/portage/sys-power:acpid-2.0.16-r1:20121014-173027.log'

>>> Messages generated by process 3908 on 2012-10-14 19:32:41 CEST for package x11-drivers/ati-drivers-12.6:

WARN: pretend
You have DRM support built in to the kernel
Direct rendering will not work.

>>> Messages generated by process 3908 on 2012-10-14 19:32:58 CEST for package sys-power/acpid-2.0.16-r1:

LOG: postinst

You may wish to read the Gentoo Linux Power Management Guide,
which can be found online at:
http://www.gentoo.org/doc/en/power-management-guide.xml


>>> Messages generated by process 3908 on 2012-10-14 19:33:11 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-173243.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 24133 on 2012-10-14 19:52:47 CEST for package x11-drivers/ati-drivers-12.6:

WARN: pretend
You have DRM support built in to the kernel
Direct rendering will not work.

>>> Messages generated by process 24133 on 2012-10-14 19:53:13 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-175248.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 1710 on 2012-10-14 20:01:17 CEST for package x11-drivers/ati-drivers-12.6:

WARN: pretend
You have DRM support built in to the kernel
Direct rendering will not work.

>>> Messages generated by process 1710 on 2012-10-14 20:01:48 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-180120.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 5159 on 2012-10-14 20:07:08 CEST for package x11-drivers/radeon-ucode-20120320:

ERROR: unpack
Fetch failed for 'x11-drivers/radeon-ucode-20120320', Log file:
 'var/log/portage/x11-drivers:radeon-ucode-20120320:20121014-180708.log'

>>> Messages generated by process 1697 on 2012-10-14 20:17:25 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-181654.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 1697 on 2012-10-14 20:22:42 CEST for package dev-perl/File-DesktopEntry-0.40.0:

ERROR: postinst
ERROR: dev-perl/File-DesktopEntry-0.40.0 failed (postinst phase):
  filter-bash-environment.py failed

Call stack:
           ebuild.sh, line 708:  Called ebuild_main 'postinst'
  phase-functions.sh, line 991:  Called filter_readonly_variables '--filter-features'
  phase-functions.sh, line 140:  Called die
The specific snippet of code:
        "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-e
nvironment.py failed"

If you need support, post the output of `emerge --info '=dev-perl/File-DesktopEntry-0.40.0'`,
the complete build log and the output of `emerge -pqv '=dev-perl/File-DesktopEntry-0.40.0'`.
The complete build log is located at 'var/log/portage/dev-perl:File-DesktopEntry-0.40.0:20121014-181719.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-perl/File-DesktopEntry-0.40.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-perl/File-DesktopEntry-0.40.0/temp/environment'.
Working directory: '/var/tmp/portage/dev-perl/File-DesktopEntry-0.40.0'
S: '/var/tmp/portage/dev-perl/File-DesktopEntry-0.40.0/work/File-DesktopEntry-0.04'

>>> Messages generated by process 32461 on 2012-10-14 20:28:17 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-182752.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 31880 on 2012-10-14 20:30:06 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-182947.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 24230 on 2012-10-14 20:32:17 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-183200.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 24230 on 2012-10-14 20:32:22 CEST for package dev-libs/glib-2.32.4-r1:

ERROR: prepare
ERROR: dev-libs/glib-2.32.4-r1 failed (prepare phase):
  filter-bash-environment.py failed

Call stack:
           ebuild.sh, line 708:  Called ebuild_main 'prepare'
  phase-functions.sh, line 991:  Called filter_readonly_variables '--filter-features'
  phase-functions.sh, line 140:  Called die
The specific snippet of code:
        "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-e
nvironment.py failed"

If you need support, post the output of `emerge --info '=dev-libs/glib-2.32.4-r1'`,
the complete build log and the output of `emerge -pqv '=dev-libs/glib-2.32.4-r1'`.
The complete build log is located at 'var/log/portage/dev-libs:glib-2.32.4-r1:20121014-183201.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-libs/glib-2.32.4-r1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.32.4-r1/temp/environment'.
Working directory: '/var/tmp/portage/dev-libs/glib-2.32.4-r1/work/glib-2.32.4'
S: '/var/tmp/portage/dev-libs/glib-2.32.4-r1/work/glib-2.32.4'

>>> Messages generated by process 13577 on 2012-10-14 20:34:31 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-183413.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 3760 on 2012-10-14 20:34:59 CEST for package media-libs/jpeg-8d:

ERROR: unpack
Fetch failed for 'media-libs/jpeg-8d', Log file:
 'var/log/portage/media-libs:jpeg-8d:20121014-183459.log'

>>> Messages generated by process 3823 on 2012-10-14 20:36:36 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-183612.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 19910 on 2012-10-14 20:42:22 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-184158.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 3553 on 2012-10-14 20:44:36 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-184412.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 18673 on 2012-10-14 20:52:15 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-185149.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 1382 on 2012-10-14 20:56:46 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-185628.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 21433 on 2012-10-14 21:07:01 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-190637.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 21433 on 2012-10-14 21:07:04 CEST for package sys-devel/gcc-4.5.4:

ERROR: other

Please include /var/tmp/portage/sys-devel/gcc-4.5.4/gcc-build-logs.tar.bz2 in your bug report


>>> Messages generated by process 25087 on 2012-10-14 22:39:54 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-203936.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 31898 on 2012-10-14 22:49:28 CEST for package x11-libs/pixman-0.26.0:

ERROR: configure
ERROR: x11-libs/pixman-0.26.0 failed (configure phase):
  econf failed

Call stack:
         ebuild.sh, line   85:  Called src_configure
       environment, line 3505:  Called xorg-2_src_configure
       environment, line 4377:  Called autotools-utils_src_configure
       environment, line  700:  Called econf '--docdir=/usr/share/doc/pixman-0.26.0' '--enable-shared' '--disable-static' '--enable-mm
x' '--enable-sse2' '--disable-vmx' '--disable-arm-neon' '--disable-arm-iwmmxt' '--disable-gtk'
  phase-helpers.sh, line  467:  Called die
The specific snippet of code:
                        die "econf failed"

If you need support, post the output of `emerge --info '=x11-libs/pixman-0.26.0'`,
the complete build log and the output of `emerge -pqv '=x11-libs/pixman-0.26.0'`.
The complete build log is located at 'var/log/portage/x11-libs:pixman-0.26.0:20121014-204921.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/environment'.
Working directory: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0_build'
S: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0'

>>> Messages generated by process 9179 on 2012-10-14 22:52:44 CEST for package x11-proto/xcb-proto-1.7.1:

WARN: postinst
Please rebuild both libxcb and xcb-util if you are upgrading from version 1.6

>>> Messages generated by process 9179 on 2012-10-14 22:57:12 CEST for package media-libs/freetype-2.4.9-r1:

LOG: postinst
The TrueType bytecode interpreter is no longer patented and thus no
longer controlled by the bindist USE flag.  Enable the auto-hinter
USE flag if you want the old USE=bindist hinting behavior.

>>> Messages generated by process 9179 on 2012-10-14 22:58:57 CEST for package x11-libs/libXi-1.6.1:

WARN: postinst
Some special keys and keyboard layouts may stop working.
To fix them, recompile xorg-server.

>>> Messages generated by process 9179 on 2012-10-14 23:00:05 CEST for package sys-apps/dbus-1.6.8:

LOG: postinst
To start the D-Bus system-wide messagebus by default
you should add it to the default runlevel :
`rc-update add dbus default`

Some applications require a session bus in addition to the system
bus. Please see `man dbus-launch` for more information.

WARN: postinst
You must restart D-Bus `/etc/init.d/dbus restart` to run
the new version of the daemon.
Don't do this while X is running because it will restart your X as well.

>>> Messages generated by process 9179 on 2012-10-14 23:00:44 CEST for package x11-misc/xdg-utils-1.1.0_rc1_p20120319:

LOG: postinst
Install x11-libs/gtk+:2 for the gtk-update-icon-cache command.

>>> Messages generated by process 9179 on 2012-10-14 23:01:14 CEST for package x11-apps/xinit-1.3.2:

WARN: postinst
If you use startx to start X instead of a login manager like gdm/kdm,
you can set the XSESSION variable to anything in /etc/X11/Sessions/ or
any executable. When you run startx, it will run this as the login session.
You can set this in a file in /etc/env.d/ for the entire system,
or set it per-user in ~/.bash_profile (or similar for other shells).
Here's an example of setting it for the whole system:
    echo XSESSION="Gnome" > /etc/env.d/90xsession
    env-update && source /etc/profile

>>> Messages generated by process 9179 on 2012-10-14 23:01:46 CEST for package media-libs/fontconfig-2.8.0-r1:

WARN: postinst
Please make fontconfig configuration changes using `eselect fontconfig`
Any changes made to /etc/fonts/fonts.conf will be overwritten.

If you need to reset your configuration to upstream defaults, delete
the directory /etc/fonts/conf.d/ and re-emerge fontconfig.

>>> Messages generated by process 9179 on 2012-10-14 23:01:58 CEST for package media-libs/mesa-8.0.4-r1:

LOG: postinst
USE="bindist" was not set. Potentially patent encumbered code was
enabled. Please see patents.txt for an explanation.

>>> Messages generated by process 9179 on 2012-10-14 23:02:08 CEST for package media-fonts/dejavu-2.33:

LOG: postinst
The following fontconfig configuration files have been installed:

  20-unhint-small-dejavu-sans-mono.conf
  20-unhint-small-dejavu-sans.conf
  20-unhint-small-dejavu-serif.conf
  57-dejavu-sans-mono.conf
  57-dejavu-sans.conf
  57-dejavu-serif.conf

Use `eselect fontconfig` to enable/disable them.

>>> Messages generated by process 9179 on 2012-10-14 23:02:28 CEST for package media-fonts/urw-fonts-2.4.9:

LOG: postinst
If you upgraded from urw-fonts-2.1-r2 some fonts will look a bit
different. Take a look at bug #208990 if interested.

>>> Messages generated by process 2419 on 2012-10-14 23:19:33 CEST for package dev-util/lafilefixer-0.5:

LOG: postinst
This simple utility will fix your .la files to not point to other .la files.
This is desirable because it will ensure your packages are not broken when
.la files are removed from other packages.

For most uses, lafilefixer --justfixit should 'just work'. This will
recurse through the most commonly used library folders and fix all .la
files it encounters.

Read lafilefixer --help for a full description of all options.

>>> Messages generated by process 2419 on 2012-10-14 23:19:42 CEST for package app-portage/portage-utils-0.10:

LOG: postinst
/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 generated by process 3887 on 2012-10-14 23:20:01 CEST for package x11-libs/pixman-0.26.0:

ERROR: configure
ERROR: x11-libs/pixman-0.26.0 failed (configure phase):
  econf failed

Call stack:
         ebuild.sh, line   85:  Called src_configure
       environment, line 3508:  Called xorg-2_src_configure
       environment, line 4380:  Called autotools-utils_src_configure
       environment, line  703:  Called econf '--docdir=/usr/share/doc/pixman-0.26.0' '--enable-shared' '--disable-static' '--enable-mm
x' '--enable-sse2' '--disable-vmx' '--disable-arm-neon' '--disable-arm-iwmmxt' '--disable-gtk'
  phase-helpers.sh, line  467:  Called die
The specific snippet of code:
                        die "econf failed"

If you need support, post the output of `emerge --info '=x11-libs/pixman-0.26.0'`,
the complete build log and the output of `emerge -pqv '=x11-libs/pixman-0.26.0'`.
The complete build log is located at 'var/log/portage/x11-libs:pixman-0.26.0:20121014-211953.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/environment'.
Working directory: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0_build'
S: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0'

>>> Messages generated by process 3887 on 2012-10-14 23:20:10 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-211949.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'

>>> Messages generated by process 3887 on 2012-10-14 23:20:19 CEST for package sys-apps/usbutils-006:

LOG: postinst
The 'network-cron' USE flag is gone; if you want a more up-to-date
usb.ids file, you should use sys-apps/hwids-99999999 (live ebuild).

>>> Messages generated by process 28071 on 2012-10-14 23:20:39 CEST for package x11-libs/pixman-0.26.0:

ERROR: configure
ERROR: x11-libs/pixman-0.26.0 failed (configure phase):
  econf failed

Call stack:
         ebuild.sh, line   85:  Called src_configure
       environment, line 3508:  Called xorg-2_src_configure
       environment, line 4380:  Called autotools-utils_src_configure
       environment, line  703:  Called econf '--docdir=/usr/share/doc/pixman-0.26.0' '--enable-shared' '--disable-static' '--enable-mm
x' '--enable-sse2' '--disable-vmx' '--disable-arm-neon' '--disable-arm-iwmmxt' '--disable-gtk'
  phase-helpers.sh, line  467:  Called die
The specific snippet of code:
                        die "econf failed"

If you need support, post the output of `emerge --info '=x11-libs/pixman-0.26.0'`,
the complete build log and the output of `emerge -pqv '=x11-libs/pixman-0.26.0'`.
The complete build log is located at 'var/log/portage/x11-libs:pixman-0.26.0:20121014-212028.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/environment'.
Working directory: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0_build'
S: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0'

>>> Messages generated by process 29916 on 2012-10-14 23:45:55 CEST for package sys-devel/gcc-4.5.4:

WARN: postinst
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 generated by process 26769 on 2012-10-14 23:46:15 CEST for package x11-libs/pixman-0.26.0:

ERROR: configure
ERROR: x11-libs/pixman-0.26.0 failed (configure phase):
  econf failed

Call stack:
         ebuild.sh, line   85:  Called src_configure
       environment, line 3508:  Called xorg-2_src_configure
       environment, line 4380:  Called autotools-utils_src_configure
       environment, line  703:  Called econf '--docdir=/usr/share/doc/pixman-0.26.0' '--enable-shared' '--disable-static' '--enable-mm
x' '--enable-sse2' '--disable-vmx' '--disable-arm-neon' '--disable-arm-iwmmxt' '--disable-gtk'
  phase-helpers.sh, line  467:  Called die
The specific snippet of code:
                        die "econf failed"

If you need support, post the output of `emerge --info '=x11-libs/pixman-0.26.0'`,
the complete build log and the output of `emerge -pqv '=x11-libs/pixman-0.26.0'`.
The complete build log is located at 'var/log/portage/x11-libs:pixman-0.26.0:20121014-214607.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/x11-libs/pixman-0.26.0/temp/environment'.
Working directory: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0_build'
S: '/var/tmp/portage/x11-libs/pixman-0.26.0/work/pixman-0.26.0'

>>> Messages generated by process 26769 on 2012-10-14 23:46:28 CEST for package media-libs/libjpeg-turbo-1.2.1:

ERROR: compile
ERROR: media-libs/libjpeg-turbo-1.2.1 failed (compile phase):
  emake failed

If you need support, post the output of `emerge --info '=media-libs/libjpeg-turbo-1.2.1'`,
the complete build log and the output of `emerge -pqv '=media-libs/libjpeg-turbo-1.2.1'`.
The complete build log is located at 'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-214606.log'.
For convenience, a symlink to the build log is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/temp/environment'.
Working directory: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'
S: '/var/tmp/portage/media-libs/libjpeg-turbo-1.2.1/work/libjpeg-turbo-1.2.1'


These two errors always come up:
Code:
>>> Failed to emerge x11-libs/pixman-0.26.0, Log file:
>>>  'var/log/portage/x11-libs:pixman-0.26.0:20121014-214607.log'
>>> Failed to emerge media-libs/libjpeg-turbo-1.2.1, Log file:
>>>  'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-214606.log'


Proszę :)
Back to top
View user's profile Send private message
phajdan.jr
Developer
Developer


Joined: 23 Mar 2006
Posts: 1767
Location: Poland

PostPosted: Sun Oct 14, 2012 7:57 pm    Post subject: Reply with quote

kbzium wrote:
These two errors always come up:
Code:
>>> Failed to emerge x11-libs/pixman-0.26.0, Log file:
>>>  'var/log/portage/x11-libs:pixman-0.26.0:20121014-214607.log'
>>> Failed to emerge media-libs/libjpeg-turbo-1.2.1, Log file:
>>>  'var/log/portage/media-libs:libjpeg-turbo-1.2.1:20121014-214606.log'


OK, please post the errors from above files. If in doubt, include more lines rather than less. Don't just post the last line that mentions the error, but include few lines above for context.
_________________
http://phajdan-jr.blogspot.com/
Back to top
View user's profile Send private message
kbzium
Tux's lil' helper
Tux's lil' helper


Joined: 31 Jul 2012
Posts: 146

PostPosted: Sun Oct 14, 2012 8:08 pm    Post subject: Reply with quote

Check it here: (its too long to post in here)

http://pastebin.com/f5EHj0Yd
Back to top
View user's profile Send private message
phajdan.jr
Developer
Developer


Joined: 23 Mar 2006
Posts: 1767
Location: Poland

PostPosted: Sun Oct 14, 2012 11:19 pm    Post subject: Reply with quote

Code:
x86_64-pc-linux-gnu-gcc: unrecognized option '-02'


Looks like you have a zero "0" in your CFLAGS instead of a big "o".

See also similar threads from the past:

http://forums.gentoo.org/viewtopic-p-6864596.html
http://forums-lb.gentoo.org/viewtopic-t-853556-start-0.html

Hopefully that can solve the failures for you! :D
_________________
http://phajdan-jr.blogspot.com/
Back to top
View user's profile Send private message
ralfeus
n00b
n00b


Joined: 28 Aug 2010
Posts: 5

PostPosted: Fri Jan 18, 2013 10:05 am    Post subject: Reply with quote

[quote="phajdan.jr"]
Code:
x86_64-pc-linux-gnu-gcc: unrecognized option '-02'


I didn't have this error, but I had rest.
I have updated nasm (emerge nasm) and after that jpeg-turbo was properly emerged.
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2128
Location: Finland

PostPosted: Fri Jan 18, 2013 10:14 am    Post subject: Reply with quote

[quote="ralfeus"]
phajdan.jr wrote:
Code:
x86_64-pc-linux-gnu-gcc: unrecognized option '-02'


I didn't have this error, but I had rest.
I have updated nasm (emerge nasm) and after that jpeg-turbo was properly emerged.


It was propably not about the upgrade, but rather nasm needed rebuilding after you upgraded gcc at some point.
It might have worked for some packages without rebuilding, but it's known that using nasm with libjpeg-turbo after gcc upgrade fails if nasm is not rebuilt.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum