Bug 104899 – bash built with CFLAGS causes emerge script to fail

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Ryan Winter 2005-09-05 07:41:35 UTC]

I have built bash with the following CFLAGS:

CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -ftracer
-fno-crossjumping -mfpmath=sse -maccumulate-outgoing-args -fmove-all-movables
-freduce-all-givs"

and now all ebuild.sh fails with:

/usr/lib/portage/bin/ebuild.sh: line 1443: : No such file or directory

One of the compile flags above is causing this problem, I just havent tracked
down which one yet.

Reproducible: Always
Steps to Reproduce:
1. Compile bash 3.0 with the above CFLAGS
2. Try to emerge a package
3. Watch the errors fly!




Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.12-gentoo-r9 i686)
=================================================================
System uname: 2.6.12-gentoo-r9 i686 AMD Athlon(tm) Proswssor
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5
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="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -ftracer
-fno-crossjumping -mfpmath=sse -maccumulate-outgoing-args -fmove-all-movables
-freduce-all-givs"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -ftracer
-fno-crossjumping -mfpmath=sse -maccumulate-outgoing-args -fmove-all-movables
-freduce-all-givs"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks prelink sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.aarnet.edu.au/pub/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="x86 3dnow X aac alsa apache2 apm arts avi berkdb bitmap-fonts cdparanoia
cdr crypt cups curl divx4linux dvd dvdr eds emboss encode fam ffmpeg flac
foomaticdb fortran gd gdbm gif gpm gstreamer gtk2 hal imagemagick imap imlib
ipv6 java jpeg kde kdeenablefinal ldap libg++ libwww mad maildir mikmod mmx mng
mp3 mpeg mysql ncurses nls nptl ogg oggvorbis opengl pam pdflib perl png python
qt quicktime readline ruby samba sdl snmp spell sse ssl svga tcltk tcpd tetex
theora tiff truetype truetype-fonts type1-fonts usb vorbis xine xml xml2 xmms xv
xvid zeroconf zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 SpanKY 2005-09-05 14:29:39 UTC]

try it with less agressive CFLAGS

[Comment 2 Ryan Winter 2005-09-06 06:54:34 UTC]

I assume this is another way of saying report it to bash directly :D  

[Comment 3 SpanKY 2005-09-06 08:09:03 UTC]

not at all, upstream maintainers dont want to hear about random users and how
their excessive optimizations broke their package

why dont you do what i asked you to in the first place

[Comment 4 Ryan Winter 2005-09-06 08:35:10 UTC]

> not at all, upstream maintainers dont want to hear about random users and how  
> their excessive optimizations broke their package  
  
Gee you certainly know how to encourage feedback from users. Can you point me  
to the gcc bug reports showing the *excessive* optimisations I have used as 
broken?  
  
> why dont you do what i asked you to in the first place  
  
There is no need, you have already marked the bug as resolved so everything  
must be fine.  

[Comment 5 SpanKY 2005-09-06 10:43:58 UTC]

you dont understand the point of NEEDINFO

it means 'provide more information and re-open'

we have many reports where users file a bug but never get back to us so NEEDINFO
lets us track issues where there isnt enough info to figure out the issue