Segmental fault when emerging ruby-1.8.2-r2, which is marked as stable in x86. Reproducible: Always Steps to Reproduce: 1. emerge =dev-lang/ruby-1.8.2-r2 2. 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) dev-lang/ruby-1.8.2-r2 to / >>> md5 files ;-) ruby-1.8.3_pre1.ebuild >>> md5 files ;-) ruby-1.6.8-r12.ebuild [snip lengthy output] i686-pc-linux-gnu-gcc -O3 -march=pentium-m -mtune=pentium-m -fforce-addr -momit-leaf-frame-pointer -ftracer -pipe -fPIC -Wl,-O1 -rdynamic -Wl,-export-dynamic main.o dmyext.o libruby18-static.a -lpthread -ldl -lcrypt -lm -o miniruby i686-pc-linux-gnu-gcc -shared -Wl,-soname,libruby18.so.1.8 array.o bignum.o class.o compar.o dir.o dln.o enum.o error.o eval.o file.o gc.o hash.o inits.o io.o marshal.o math.o numeric.o object.o pack.o parse.o process.o prec.o random.o range.o re.o regex.o ruby.o signal.o sprintf.o st.o string.o struct.o time.o util.o variable.o version.o dmyext.o -lpthread -ldl -lcrypt -lm -o libruby18.so.1.8.2 ./mkconfig.rb:37: [BUG] Segmentation fault ruby 1.8.2 (2004-12-25) [i686-linux] make: *** [rbconfig.rb] Aborted make: *** Waiting for unfinished jobs.... make: *** Waiting for unfinished jobs.... !!! ERROR: dev-lang/ruby-1.8.2-r2 failed. !!! Function src_compile, Line 88, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. Expected Results: It should be emerged smoothly. USE flags for ruby-1.8.2-r2: +cjk -doc -socks5 +tcltk +threads Output of `emerge info' followed: Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.13-suspend2-r2 i686) ================================================================= System uname: 2.6.13-suspend2-r2 i686 Intel(R) Pentium(R) M processor 1.73GHz Gentoo Base System version 1.6.13 ccache version 2.3 [enabled] dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium-m -mtune=pentium-m -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium-m -mtune=pentium-m -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://ftp.gentoo.or.kr/ http://gentoo.mirrors.tds.net/gentoo http://gentoo.llarian.net/" LDFLAGS="-Wl,-O1" LINGUAS="zh_CN" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac acpi alsa apache2 audiofile authdaemond avi bash-completion berkdb bitmap-fonts bzip2 cjk crypt cups curl directfb divx4linux emboss encode fam fbcon foomaticdb gif gpm gstreamer gtk gtk2 i8x0 imagemagick imlib immqt-bc irda jikes jpeg libg++ libwww logrotate mad matroska mmx mmx2 mmxext mozsvg mp3 mpeg ncurses nls nptl ntl offensive ogg oggvorbis opengl pam pdflib png quicktime readline real sdl sms spell sse sse2 ssl subversion svg tcpd tetex threads truetype truetype-fonts type1-fonts unicode vorbis win32codecs wxwindows xosd xv xvid xvmc zlib linguas_zh_CN userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL
does it fail in the same place every time you try to emerge?
(In reply to comment #1) > does it fail in the same place every time you try to emerge? Yes, it does, the same place every time.
Just to make sure, can you try to compile ruby with 'vanilla' CFLAGS like e.g. march=XXX -02 -pipe? Thanks!
CFLAGS="-march=pentium-m -O2 -pipe" emerge ruby it emerged smoothly.
Some packages just don't like overoptimized CFLAGS, so I'll mark this bug as INVALID. You're of course free to use whichever CFLAGS you like, you just have to live with the occasional breakage. :)
