Hi, When compiling xorg, the mesa package failed to compile. Here's my emerge info Portage 2.1.6.11 (default/linux/amd64/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.29-gentoo-r5 x86_64) ================================================================= System uname: Linux-2.6.29-gentoo-r5-x86_64-Intel-R-_Core-TM-2_Quad_CPU_@_2.66GHz-with-glibc2.2.5 Timestamp of tree: Tue, 02 Jun 2009 15:15:01 +0000 app-shells/bash: 3.2_p39 dev-lang/python: 2.5.4-r2 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.7.9-r1, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -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/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ ftp://mirror.switch.ch/mirror/gentoo/ " LDFLAGS="-Wl,-O1" MAKEOPTS="-j17" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acl acpi amd64 authdaemon automount avahi berkdb bzip2 cairo caps cdr clamav cli cracklib crypt cups curl custom-cflags dbus dri dvdr fortran ftp gd gdbm gif gnome gpm gtk hal iconv imap ioemu iommu ipv6 isdnlog jpeg libwww maildir mdnsresponder-compat memlimit midi mmx mtrr mudflap multilib mysql ncurses nls nptl nptlonly opengl openmp pae pam pcre pdf perl pppd python rdesktop readline reflection sasl session spl sse sse2 ssl ssse3 symlink sysfs tcpd threads truetype unicode xml xorg xosd xscreenserver xsm zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 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="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="intel vesa" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY Saddly the emerge failed log went away when I successfuly compiled it. The only solution I found to compile it was like this: USE="-dri" emerge mesa Know that the package compiles fine without the USE="-dri" once xorg has finished compiling the other packages. PS: Yes I did try to recompile the package with MAKEOPTS="-j1" as well but same behaviour, the only way to compile mesa on my system was the way used above. Reproducible: Always Steps to Reproduce: 1. LiveCD minimal install, build your system, emerge --update --newuse --deep world, make sure everything is up to date; emerge -e world. If ok, reboot 2. emerge xorg-server 3. emerge fails on media-libs/mesa-7.3-r1 Alright, I've made a mistake emerge xorg-server instead of xorg-x11, but nevertheless the emerge of mesa failed without the slightest error message in the log. The top most error was not of much help.
There is not much we can do without the build.log. Does it fail if you try it again with dri enabled?
(In reply to comment #1) > There is not much we can do without the build.log. Does it fail if you try it > again with dri enabled? Hi Sebastian, I'm able to compile the mesa package with the "dri" enabled once the packages needed by xorg-x11 have finished installing. I don't know if it's related with the "intel" drivers. I'm sorry for the missing log, I've first tried to solve the problem and this removed the failed emerge log. I have another system quite identical but not yet in production, I'll see when switching from the "nvidia" driver to the "intel" if this happens again when I'll recompile xorg-x11. I'll post the results if something relevant happens. Cheers
(In reply to comment #2) > (In reply to comment #1) > > There is not much we can do without the build.log. Does it fail if you try it > > again with dri enabled? > Hi Sebastian, > I'm able to compile the mesa package with the "dri" enabled once the packages > needed by xorg-x11 have finished installing. I don't know if it's related with > the "intel" drivers. > I'm sorry for the missing log, I've first tried to solve the problem and this > removed the failed emerge log. I have another system quite identical but not > yet in production, I'll see when switching from the "nvidia" driver to the > "intel" if this happens again when I'll recompile xorg-x11. > I'll post the results if something relevant happens. > Cheers Hhhmm no, mesa compiled just fine on the second system, yet it was an already running system with packages compiled, the system I had the trouble with was a new install.
Unless we know what actually went wrong, it will be very difficult for us to fix it. I'm therefore marking this bug as NEEDINFO, but do please reopen it as soon as you've got the error message and build.log available...
Created attachment 200839 [details] Build Log from Mesa-7.3r1 failure (on Sparc 64) Greetings - This is my first time ever posting a log file, but I experienced a similar failure of mesa-7.3r1 to build following an 'emerge xorg-server' on a Sun Blade 150. I am able to spend some time collecting data, but am not sure exactly what else you would need to see, so I've attached the build log (ascertained from other comments that you need to see this). This is a 'newer' gentoo machine, so it hasn't had much built on it yet, and here's what I actuall saw in the terminal when things broke down: sparc-unknown-linux-gnu-g++ -c -I../../../include -Iinclude -Iinternals -Ilibnurbs/internals -Ilibnurbs/interface -Ilibnurbs/nurbtess -O2 -mcpu=ultrasparc mtune=ultrasparc -pipe -ffast-math -fPIC -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DGLX_USE_TLS -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -DGLX_DIRECT_RENDERING -DNDEBUG -DLIBRARYBUILD libnurbs/interface/bezierEval.cc -o libnurbs/interface/bezierEval.o sparc-unknown-linux-gnu-g++: mtune=ultrasparc: No such file or directory gmake[4]: *** [libnurbs/interface/bezierEval.o] Error 1 gmake[4]: *** Waiting for unfinished jobs.... gmake[4]: Leaving directory `/var/tmp/portage/media-libs/mesa-7.3-r1/work/Mesa-7.3/src/glu/sgi' gmake[3]: *** [default] Error 1 gmake[3]: Leaving directory `/var/tmp/portage/media-libs/mesa-7.3-r1/work/Mesa-7.3/src/glu/sgi' gmake[2]: *** [default] Error 1 gmake[2]: Leaving directory `/var/tmp/portage/media-libs/mesa-7.3-r1/work/Mesa-7.3/src/glu' make[1]: *** [subdirs] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/mesa-7.3-r1/work/Mesa-7.3/src' make: *** [default] Error 1 * * ERROR: media-libs/mesa-7.3-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3065: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-libs/mesa-7.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-7.3-r1/temp/environment'. * >>> Failed to emerge media-libs/mesa-7.3-r1, Log file: >>> '/var/tmp/portage/media-libs/mesa-7.3-r1/temp/build.log' * Messages for package media-libs/mesa-7.3-r1: * * ERROR: media-libs/mesa-7.3-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3065: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-libs/mesa-7.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-7.3-r1/temp/environment'. * * GNU info directory index is up-to-date. Please feel free to let me know what else I can get that would be useful. Regards, Mike
