The following ebuilds are found to have broken autotools handling, as they run libtoolize directly (they never should, instead they should call eautoreconf in autotools.eclass, read http://www.gentoo.org/proj/en/qa/autofailure.xml for more information): ./media-gfx/pixie/pixie-1.5.1.ebuild: libtoolize --force --copy || die ./media-gfx/pixie/pixie-1.6.2.ebuild: libtoolize --force --copy || die Please cleanup the ebuilds by asking for stable marking, removing obsolete ebuilds with no relevant keywords, or porting the fixes in newer versions (if presents) to properly handle autotools. Thanks, Diego
1.6.2 removed. Arch teams, please stabilise media-gfx/pixie-1.6.3 so we can get rid of 1.5.1.
D'oh! /me gets more coffee
fails here: i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I.. -O2 -march=prescott -pipe -fomit-frame-pointer -MT renderer.lo -MD -MP -MF .deps/renderer.Tpo -c renderer.cpp -fPIC -DPIC -o .libs/renderer.o renderer.cpp: In member function 'CShaderInstance* CRendererContext::getShader(const char*, int, int, char**, void**)': renderer.cpp:746: error: 'parseShader' was not declared in this scope make[3]: *** [renderer.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... mv -f .deps/init.Tpo .deps/init.Plo Gentoo Base System version 1.12.6 Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r4, 2.6.19.1 i686) ================================================================= System uname: 2.6.19.1 i686 Genuine Intel(R) CPU T2300 @ 1.66GHz Last Sync: Fri, 12 Jan 2007 19:30:01 +0000 ccache version 2.4 [disabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.3.5-r3, 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--nospinner" FEATURES="autoconfig collision-protect distlocks metadata-transfer parallel-fetch sandbox sfperms strict test userfetch userpriv usersandbox" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://gentoo.inode.at/" LINGUAS="en de en_GB de_CH" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/pack ages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa alsa_cards_ali5451 alsa_cards_als4000 alsa_cards_atiixp alsa_cards_atiixp-modem alsa_cards_bt87x alsa_cards_ca0106 alsa_cards_cmipci alsa_cards_emu10k1x alsa_cards_ens1370 alsa _cards_ens1371 alsa_cards_es1938 alsa_cards_es1968 alsa_cards_fm801 alsa_cards_hda-intel alsa_cards_intel8x0 alsa_cards_intel8x0m alsa_cards_maestro3 alsa_cards_trident alsa_cards_usb-audio alsa_cards_via8 2xx alsa_cards_via82xx-modem alsa_cards_ymfpci alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugin s_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugin s_shm alsa_pcm_plugins_softvol apache2 asf berkdb bitmap-fonts cairo cdr cdrom cli cracklib crypt cups dbus divx dlloader dri dts dvd dvdr dvdread eds elibc_glibc emboss encode fam ffmpeg firefox flac fort ran gdbm gif gnome gpm gstreamer gtk hal iconv input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kde kdeenablefinal kernel_linux ldap libg++ linguas_de linguas_de_CH linguas_en linguas_en_G B mad mikmod mmx mono mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection rtsp ruby samba sdl session smp spell spl sse sse2 sse3 ssl svg tcpd test tetex theora threads truetype truetype-fonts type1-fonts udev unicode userland_GNU vcd video_cards_fbdev video_cards_i810 video_cards_vesa vorbis win32codecs wxwindows x264 xine xml xorg xpri nt xv xvid zlib" Unset: CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #3) > fails here: > i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I.. -O2 -march=prescott > -pipe -fomit-frame-pointer -MT renderer.lo -MD -MP -MF .deps/renderer.Tpo -c > renderer.cpp -fPIC -DPIC -o .libs/renderer.o > renderer.cpp: In member function 'CShaderInstance* > CRendererContext::getShader(const char*, int, int, char**, void**)': > renderer.cpp:746: error: 'parseShader' was not declared in this scope > make[3]: *** [renderer.lo] Error 1 > make[3]: *** Waiting for unfinished jobs.... > mv -f .deps/init.Tpo .deps/init.Plo Same on ppc. Plus it ate all my memory and swap too.
ppc doesn't have a stable version. I'll have a look tomorrow anyway.
remove x86 as nothing moved here, adding treecleaners to decide what to do.
Sparc, please stabilize this. I know i put it today in the tree, but older versions are broken and unsupported and eat a lot of ram while compiling. Removing ppc from cc as they don't have it stable.
sparc stable.
The 2.0 series is not mature which is why I didn't add it when I added 1.7.6 last month. 2.0.1 had some serious issues. Okan addressed those in 2.0.2, but I don't think it is wise to ignore policy and push something directly into stable like that. 1.7.6 does work and should've been the ones pushed to stable. I've readded 1.7.6 and stabilized it on x86 and sparc. I've also fixed the DEPEND in 2.0.2 to include fltk and cleaned up the ebuild and revbumped it because of the new USE flag. I've pushed it back into ~arch.
(In reply to comment #9) > 1.7.6 does work and should've been the ones pushed to stable. Does work? If by does work you mean this is an app to test kernel OOM killer, then yeah it works perfectly (Bug 153650). Please, stop stabilizing utter junk.
(In reply to comment #9) > I've pushed it back into ~arch. No, you've nuked all keywords and did stick KEYWORDS="-*" there instead without telling anyone... CCing ppc as well.
x86 done
There is no need to stabilize 2.x as it is not stable. 1.7.6 has been in portage for a month and compiles fine for systems with low memory. I just got done compiling it on my sparc with 512M. For those who are having issues using -j2 and whatnot (as was the case in the bug you reported), I am forcing -j1 now in that ebuild. Yes I did put 2.0 back in -* because I hadn't tested it and it's not stable. I restored 1.7.6 as that is what people should be using for stable, and 2.0.2-r1 is now in ~arch as I am done testing it. As for "not telling anybody", I've been emailing armin76 about this, so please don't start making assumptions about that which you do not know.
(In reply to comment #13) > Yes I did put 2.0 back in -* because I hadn't tested it and it's not stable. I > restored 1.7.6 as that is what people should be using for stable, and 2.0.2-r1 > is now in ~arch as I am done testing it. > > As for "not telling anybody", I've been emailing armin76 about this, so please > don't start making assumptions about that which you do not know. How exactly is all the above relevant? You simply do not drop keywords for no reason on version bump, period. If you actually have some valid reason to drop them, then you file a re-keywording bug for the arches you've dropped. [1] You also do not stabilize anything on arches you are non member of, such as x86 [2] [1] http://devmanual.gentoo.org/keywording/index.html [2] http://www.gentoo.org/proj/en/base/x86/ And finally, repeatedly reverting particular arch's keywording and causing perpetual downgrades is a sure way to piss both arch teams and users off.
(In reply to comment #14) > You also do not stabilize anything on arches you are non member of, such as x86 Stay cool, everybody. So what is the current state? We got off that bug as 1.6.3 was not builiding at all, then there was a bump to 1.7 which went straight to stable I suppose. If 1.7 is ok with autotools and would be working, I would have no problem to leave 1.7 in stable....BUT eradicator, as I see you are no member of x86 team, so you should not stable packages on your own. File a bug to us and we will handle it. Next BUT: When emerging, pixie 1.7.6 is eating all my memory on following line: i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I.. -O2 -MT execute.lo -MD -MP -MF .deps/execute.Tpo -c execute.cpp -fPIC -DPIC -o .libs/execute.o With all USE flags enabled. So it is not stable. Portage 2.1.2.2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r5 i686) ================================================================= System uname: 2.6.19-gentoo-r5 i686 AMD Athlon(tm) XP 2500+ Gentoo Base System release 1.12.9 Timestamp of tree: Thu, 15 Mar 2007 06:20:01 +0000 dev-java/java-config: 1.3.7, 2.0.31 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /opt/openjms/config /usr/NX/etc /usr/NX/home /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/spool/PBS /var/vpopmail/domains /var/vpopmail/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/php/apache1-php4/ext-active/ /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php4/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php4/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php4/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo/" LANG="de_DE@euro" LC_ALL="de_DE.utf8" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.informatik.rwth-aachen.de/gentoo-portage" USE="3dnow 3dnowext X Xaw3d a52 alsa apache artworkextra asf audiofile bash-completion beagle berkdb bidi bitmap-fonts bootsplash branding bzip2 cairo cdda cddb cdparanoia cdr cli cracklib crypt css cups curl custom-cflags dbus dga directfb divx4linux dts dvd dvdr dvdread dvi eds emacs emboss encode esd evo exif expat fam fat fbcon ffmpeg firefox fortran ftp gb gcj gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml hal iconv icq idn imagemagick imap isdnlog java javamail javascript jikes jpeg jpeg2k kde ldap leim libg++ mad maildir matroska mbox mhash midi mikmod mime mmx mmxext mng mono mp3 mpeg mpeg2 mule mysql nautilus ncurses nforce2 nls nocardbus nptl nptlonly nsplugin nvidia objc ogg opengl pam pcre pdf perl plotutils pmu png ppds pppd preview-latex print python qt3 qt4 quicktime readline reflection reiserfs samba sdk session slang spell spl sse ssl svg svga t1lib tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts unicode usb vcd videos vorbis win32codecs wmf wxwindows x86 xine xml xorg xosd xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 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 mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="radeon vesa fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Yes, the bug was with 1.6. I added 1.7.6 a month ago (into ~arch). It was not pushed straight into stable. Check the ChangeLog if you don't believe me. Then a few days ago, someone other than me added 2.0.2 and requested it be added straight into stable, but it was not stable and not ready to be pushed into stable. In fact, I didn't even add 2.0.1 into portage when it came out because of some serious memory issues which I don't believe are fully fixed in 2.0.2 yet. I readded the 1.7.6 ebuild to portage as the stable option for sparc and x86 to address the 1.5.x issue. Additionally, I am forcing -j1 on make because of the compilation memory overhead. I did not on my u10 with 512M and 1G swap, and in all honesty if someone doesn't have >512M of physical memory, they're probably not going to be using pixie. As for policy this, policy that... 2.0.2 should NOT have been pushed straight into stable (I don't think I need to find some policy URL for you on that one), so my actions were a response to correct that error in a timely fashion. 2.x is not stable. 1.7.6 is stable. Therefore if a user has 2.0.2 and needs a stable pixie, then they needed to downgrade to get it. And yes, I apologize for stabilizing 1.7.6 on x86 without being a member of the x86 herd, but as I mentioned above I saw that as the best option to maintain QA in the tree (didn't want there to be no stable x86 package, and didn't want an unstable package to be stable)... plus I use pixie on x86 and have tested 1.7.6 to be quite stable. Now, regarding the memory consumption during compilation, src/ri/execute.cpp has not changed significantly between 1.7.6 and 2.0.2, so can you please verify your memory usage during compilation of 2.0.2-r1?
eradicator - 1.7.6 compile consumes *any and all* available memory + swap and kills the box and all kittens around. Get yourself an *x86* box and go try it, the compile makes it completely unusable and crashes on OOM every time you try... About comparable w/ kmail and USE=kdeenablefinal. And yeah, 2.0.2 compiles just fine here, so it's really ironic when you are talking about memory issues w/ 2.0.2. Summary: 1.7.6 is unusable trash on x86, drop the stable keyword there and let people who actually *use* the arch stabilize something that compiles and works for them instead of reverting the keywords over and over again. Stabilizing version that cannot be compiled is plain useless.
Jakub, the memory issues in 2.0.2 I speak of are with the application itself, not consumption during compilation. Additionally, there is no significant difference in that file between 1.7.6 and 2.0.2 that would explain this memory consumption in 1.7.6 and not in 2.0.2. I do have an x86 chroot on my amd64 box which is what I use for pixie and what I tested it on and have been using it with for the past month. Re "over and over again"... wtf do you mean by that? I keyworded ONE thing (after testing it for a month) in response to someone pushing a package directly into stable before it was ready to be stable. Please stop trying to create drama. I didn't start this mess; I'm just trying to get it solved. So if x86 doesn't want 1.7.6 to be stable, then feel free do either: 1) resurrect a previous version and stabilize that (oh no... more downgrades) 2) have no package stable and all in ~arch (yet another policy violation at this point) and wait for me to finish testing 2.0.2 and talk with Okan to see if he addressed all the issues I found in 2.0.1
(In reply to comment #16) > Yes, the bug was with 1.6. I added 1.7.6 a month ago (into ~arch). It was not > pushed straight into stable. Check the ChangeLog if you don't believe me. I read the ChangeLog like that. As I only see "version bump" and then "restored 1.7.6 as stable option", which was not that clear to me. Anyway, this is not important as we have to talk how to fix the issue for x86. > Then a few days ago, someone other than me added 2.0.2 and requested it be > added straight into stable, but it was not stable and not ready to be pushed > into stable. I think this was a misunderstanding. It was armin76, who might have thought pixie is unmaintained (which it seemed to be) and tried to resolve an issue. He also is member of x86 team and pushed it to stable as 2.0.2 was the only version at least building on our arch. > I readded the 1.7.6 ebuild to portage as the stable option for sparc and x86 to > address the 1.5.x issue. Additionally, I am forcing -j1 on make because of the > compilation memory overhead. I did not on my u10 with 512M and 1G swap, and in > all honesty if someone doesn't have >512M of physical memory, they're probably > not going to be using pixie. I have 1GB of memory and 512MB of swap which were filled completely! So tell me what I do wrong. > As for policy this, policy that... 2.0.2 should NOT have been pushed straight > into stable (I don't think I need to find some policy URL for you on that one), Right. In normal cases. But if the previous stable is not building at all, it is a habit among arch teams to stable directly or prematurely. > so my actions were a response to correct that error in a timely fashion. 2.x > is not stable. 1.7.6 is stable. Therefore if a user has 2.0.2 and needs a > stable pixie, then they needed to downgrade to get it. And yes, I apologize > for stabilizing 1.7.6 on x86 without being a member of the x86 herd, but as I > mentioned above I saw that as the best option to maintain QA in the tree > (didn't want there to be no stable x86 package, and didn't want an unstable > package to be stable)... plus I use pixie on x86 and have tested 1.7.6 to be > quite stable. Then I would like to know which configuration on x86 does not lead to a out-of-bounds memory usage. > Now, regarding the memory consumption during compilation, src/ri/execute.cpp > has not changed significantly between 1.7.6 and 2.0.2, so can you please verify > your memory usage during compilation of 2.0.2-r1? It had no problems...otherwise I wouldn't have stabled it. My question/proposal: How severe are those memory issues in 2.0.2? Could it be a trade-off in having a version that at least emerges but works not perfectly? If yes, we will stable 2.0.2, if you say no, we leave it as is and wait for a newer version, which can go stable prematurely then. Portage 2.1.2.2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r5 i686) ================================================================= System uname: 2.6.19-gentoo-r5 i686 AMD Athlon(tm) XP 2500+ Gentoo Base System release 1.12.9 Timestamp of tree: Fri, 16 Mar 2007 06:20:01 +0000 dev-java/java-config: 1.3.7, 2.0.31 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /opt/openjms/config /usr/NX/etc /usr/NX/home /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/spool/PBS /var/vpopmail/domains /var/vpopmail/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/php/apache1-php4/ext-active/ /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php4/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php4/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php4/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo/" LANG="de_DE@euro" LC_ALL="de_DE.utf8" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.informatik.rwth-aachen.de/gentoo-portage" USE="3dnow 3dnowext X Xaw3d a52 alsa apache artworkextra asf audiofile bash-completion beagle berkdb bidi bitmap-fonts bootsplash branding bzip2 cairo cdda cddb cdparanoia cdr cli cracklib crypt css cups curl custom-cflags dbus dga directfb divx4linux dts dvd dvdr dvdread dvi eds emacs emboss encode esd evo exif expat fam fat fbcon ffmpeg firefox fortran ftp gb gcj gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml hal iconv icq idn imagemagick imap isdnlog java javamail javascript jikes jpeg jpeg2k kde ldap leim libg++ mad maildir matroska mbox mhash midi mikmod mime mmx mmxext mng mono mp3 mpeg mpeg2 mule mysql nautilus ncurses nforce2 nls nocardbus nptl nptlonly nsplugin nvidia objc ogg opengl pam pcre pdf perl plotutils pmu png ppds pppd preview-latex print python qt3 qt4 quicktime readline reflection reiserfs samba sdk session slang spell spl sse ssl svg svga t1lib tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts unicode usb vcd videos vorbis win32codecs wmf wxwindows x86 xine xml xorg xosd xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 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 mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="radeon vesa fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #19) > > Right. In normal cases. But if the previous stable is not building at all, > it is a habit among arch teams to stable directly or prematurely. This was a misunderstanding on my end. I was under the impression that 1.5.x was having issues and 1.7.6 was fine (as it was building fine for me in my x86 chroot on my amd64 box). > Then I would like to know which configuration on x86 does not lead to a > out-of-bounds memory usage. My emerge --info's are at the bottom for my x86 chroot and my sparc box. I'm using gcc-3.4 which might mean this is showing a regression in gcc-4. I'll install gcc-4.1.2 in that chroot and try using that to compile pixie-1.7.6 > It had no problems...otherwise I wouldn't have stabled it. > > My question/proposal: How severe are those memory issues in 2.0.2? Could it be > a trade-off in having a version that at least emerges but works not perfectly? > If yes, we will stable 2.0.2, if you say no, we leave it as is and wait for a > newer version, which can go stable prematurely then. There are some issues with memory leaks related to ray casting shaders in 2.0.1. I'm not sure if that has been fixed in 2.0.2 as I haven't tested it yet. I didn't realize Okan pushed out 2.0.2 until I noticed it in portage. --- Portage 2.1.2.2 (default-linux/x86/2006.0, gcc-3.4.6/hardenednopie, glibc-2.4-r2, 2.6.20-gentoo-r2 i686) ================================================================= System uname: 2.6.20-gentoo-r2 i686 AMD Athlon(tm) 64 Processor 2800+ Gentoo Base System version 1.12.0_pre19 Timestamp of tree: Thu, 15 Mar 2007 08:50:01 +0000 app-admin/eselect-compiler: 2.0.0_rc1-r4 dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r2, 2.17 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/eselect/compiler /etc/gconf /etc/terminfo" CXXFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" DISTDIR="/var/tmp/gentoo/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" PKGDIR="/var/tmp/gentoo/packages-amd64" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp/g32" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/var/tmp/gentoo/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apache2 apm arts berkdb bitmap-fonts cli cracklib crypt cups dri eds emboss encode esd foomaticdb fortran gcj gdbm gif glibc-omitfp gnome gpm gstreamer gtk gtk2 iconv imlib ipv6 isdnlog jpeg kde libg++ libwww mad midi mikmod motif mp3 mpeg multislot ncurses nls nptl nptlonly objc objc++ ogg opengl oss pam pcre perl png pppd python qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts userlocales vorbis x86 xml xorg xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 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 mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark ati chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mga neomagic nsc nv rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
and the sparc box (sorry for 2x comments, but it wouldn't fit in just one) Portage 2.1.2.2 (default-linux/sparc/sparc64/2006.0, gcc-3.4.6/vanilla, glibc-2.3.6-r5, 2.6.20-gentoo-r2 sparc64) ================================================================= System uname: 2.6.20-gentoo-r2 sparc64 sun4u Gentoo Base System release 1.12.9 Timestamp of tree: Thu, 15 Mar 2007 08:50:01 +0000 app-admin/eselect-compiler: 2.0.0_rc2-r1 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.15.92.0.2-r10, 2.16-r1, 2.16.1-r2, 2.17 sys-devel/gcc-config: 2.0.0_rc1 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.20-r1 ACCEPT_KEYWORDS="sparc ~sparc" AUTOCLEAN="yes" CBUILD="sparc-unknown-linux-gnu" CFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe" CHOST="sparc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe" DISTDIR="/var/tmp/distfiles" FEATURES="autoconfig confcache distlocks metadata-transfer sandbox sfperms strict userpriv" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/var/tmp/packages-sparc" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://cloud/gentoo-portage" USE="X Xaw3d a52 aac accessibility acl aim alsa ao apache apache2 asterisk audiofile bash-completion berkdb bidi bitmap-fonts bonobo browserplugin bzip2 c++ cap caps cddb cdparanoia chroot clamav cli cracklib crypt cups curl cvsgraph dbus dmx dnd dri dts dv dvd dvdread edl eds encode enscript erandom esd evo expat ext-png ext-zlib extlib f77 fam fame fastcgi fat fbcon fbdev ffmpeg fftw firefox flac flash fltk fluidsynth font-server foreign-package fortran freetype fullrpc gcl gdbm gif gimpprint glade glgd glut gnome gnomedb gnutls gpm gtk gtk2 gtkhtml hal iconv idea idn imagemagick imap imlib imlib2 innodb ipv6 isdnlog jabber jack javascript jbig jdepend jikes joystick jpeg jpeg2k junit justify ladcca lcms ldap leim libg libg++ libgda linuxthreads-tls live logitech-mouse lzo mad maildir makecheck midi mmap mng motif moznocompose moznoirc mozsvg mp3 mpeg mpeg2 mplayer msn mule multislot music mysql mythtv ncurses net network nls nptl nptlonly oav objc odbc offensive ogg oldworld openal opengl operanom2 oscar oss pam parse-clocks pcre perl png portaudio ppds pppd prelude propolice pthreads python qhull qt3 rdesktop readline reflection rpc rtc samba sasl sdl serial session silc slp sndfile socks5 sox sparc speex spell spl sqlite ssl tcltk tcpd tga theora tiff timidity transcode truetype truetype-fonts type1 type1-fonts unicode usb userlocales videos vim-with-x virus-scan vorbis wxwindows xaa xchattext xemacs xine xml xml2 xorg xosd xprint xv xvid yahoo zlib" ALSA_CARDS="sun-cs4231,ens1371" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="ati sunffb mga fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
> My question/proposal: How severe are those memory issues in 2.0.2? Could it be > a trade-off in having a version that at least emerges but works not perfectly? > If yes, we will stable 2.0.2, if you say no, we leave it as is and wait for a > newer version, which can go stable prematurely then. Whoops... I didn't actually finish addressing this (too late at night for me ... heh). If it is the case that something in the newer toolchain is borking on the older version of pixie, and it works on 2.0.2 (I really don't see why 1.7.6 would not compile on that file and 2.0.2 would, but I can't argue if that is really happening), then I agree that having 2.0.2 would be the lesser of two evils. That being said, I just tried compiling pixie 1.7.6 on my sparc64/2007.0 chroot which uses gcc4.1.2, and it was consuming memory up the wazoo, so it looks like it is not specific to x86 but is a regression somewhere between gcc3.4.6 and gcc4.1.2
Ok, so I remove ppc as they have no current stable. Which leaves sparc and x86 with pixie 1.7 in stable and gcc 4.1. To sum it up, please stabilise pixie 2.0.2-r1, x86 already done now. eradicator, you can come to request stabilisation prematurely when a newer pixie version comes out with the memory bugs fixed. Bye.
2.0.2-r1 is stable on sparc with a note in the changelog explaining the issue. I'm going to investigate the gcc issue a bit further to see if I can come up with a simplified test case for the problem.
