Bugzilla Bug 77972

bootstraping during installation from  stage1-x86-2004.3 cannot be completed
because texinfo-4.8 fails. I am accepting "~x86" keyword.

Reproducible: Always
Steps to Reproduce:
1.cd /usr/portage
2.scripts/bootstrap.sh
3.

Actual Results:  
  if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
done; \
if ..//makeinfo/makeinfo   -I . \
 -o info-stnd.info `test -f 'info-stnd.texi' || echo './'`info-stnd.texi; \
then \
  rc=0; \
else \
  rc=$?; \
  $restore $backupdir/* `echo "./info-stnd.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
restore=: && backupdir=".am$$" && \
rm -rf $backupdir && mkdir $backupdir && \
for f in info.info info.info-[0-9] info.info-[0-9][0-9] info.i[0-9]
info.i[0-9][0-9]; do \
  if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
done; \
if ..//makeinfo/makeinfo   -I . \
 -o info.info `test -f 'info.texi' || echo './'`info.texi; \
then \
  rc=0; \
else \
  rc=$?; \
  $restore $backupdir/* `echo "./info.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
make[2]: *** [texinfo.info] Error 132
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/texinfo-4.8/work/texinfo-4.8/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/texinfo-4.8/work/texinfo-4.8'
make: *** [all] Error 2


Expected Results:  
processing of bootstraping should be completed

Portage 2.0.51-r12 (default-linux/x86/2004.3, gcc-3.3.4,
glibc-2.3.4.20041102-r0, 2.6.9-1-k7 i686)
=================================================================
System uname: 2.6.9-1-k7 i686 AMD Athlon(tm) processor
Gentoo Base System version 1.4.16
Python:               [2.3.4 (#1, Oct 24 2004, 00:50:52)]
dev-lang/python:     [Not Present]
sys-devel/autoconf:  [Not Present]
sys-devel/automake:  [Not Present]
sys-devel/binutils:  2.14.90.0.8-r1
sys-devel/libtool:   [Not Present]
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -ftracer
-fprefetch-loop-arrays -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/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -ftracer
-fprefetch-loop-arrays -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/
ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow 3dnowex X alsa apm ati audiofile avi berkdb bitmap-fonts blas
cdparanoia cdr crypt cups dvd dvdr encode f77 fftw flac font-server foomaticdb
fortran freetype gd gdbm gif gimpprint glx gnuplot gphoto2 gpm gtk2 icq imlib
jabber jpeg jpeg2k kde ldap libg++ libwww lzw-tiff mad maildir mikmod mmx mmx2
motif mozilla mpeg ncurses network nls nptl objc oggvorbis ooo-kde opengl oss
pam pdflib perl plotutils png python qt quicktime readline samba scanner sdl
speex spell sse ssl svg svga tcltk tcpd theora threads tiff truetype
truetype-fonts trutype type1-fonts videos wmf x86 xine xinerama xml2 xmms xv
xvid zlib linguas_pl"
Unset:  LDFLAGS, PORTDIR_OVERLAY

Had the exact same problem the other day.
Turns out my machine was an athlon-tbird, not an athlon-xp (which I had in /etc/make.conf).
This resulted in illegal instructions (SIGILL) being sent to some apps.
This in turn results in the Error 132 you see there.
Other apps (like nano) may also exit with SIGILL, and the system is generally hosed after this.
Check with /proc/cpuinfo to see if your CPU is really an athlon-xp.
If it is, try turning down the optimizations to just '-march=athlon-xp -O2 -pipe', and see what happens.

Same issue today bootstrappin' my laptop.  Had -march=pentium4m which I had
seen somewhere without doing any real research and decided to try it.  Changed
back to -march=pentium4 no problems.

I'm not low down and dirty enough to decipher exactly what's happening here,
but perhaps this is the first package that uses the -march= for compiling? 
That would indicate this isn't a bug as much as a typical point for user error
to show up!

I've the same problem with the below make.conf
Any idea?

Problem go away when -msse2 os being removed...


Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 i686)
=================================================================
System uname: 2.6.9-gentoo-r1 i686 Intel(R) Pentium(R) III CPU family      1266MHz
Gentoo Base System version 1.4.16
Python:               [2.3.4 (#1, Oct 24 2004, 00:50:52)]
dev-lang/python:     [Not Present]
sys-devel/autoconf:  [Not Present]
sys-devel/automake:  [Not Present]
sys-devel/binutils:  2.14.90.0.8-r1
sys-devel/libtool:   [Not Present]
virtual/os-headers:  2.4.22-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=pentium3 -fomit-frame-pointer -pipe -mmmx -msse -msse2"
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/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=pentium3 -fomit-frame-pointer -pipe -mmmx -msse -msse2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig buildpkg candy ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://mymirror.asiaosc.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.asia.gentoo.org/gentoo-portage"
USE="x86 acl apache2 apm arts avi bash-completion berkdb bitmap-fonts bzlib cjk crypt cups emboss encode ethereal f77 font-server foomaticdb fortran gdbm gif gpm gtk2 imap imlib ipv6 jpeg ldap libg++ libwww mad mhash mikmod mime motif mp3 mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png posix postgres python qt quicktime readline samba sasl sdl slp spell sse ssl svga tcpd truetype truetype-fonts type1-fonts unicode usb xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

looks like every combination here is just using wrong CFLAGS for their host cpu

On a Gentoo 2005.0 bootstrap I was doing, I had to remove this line from my
make.conf before texinfo would build:

LDFLAGS="-Wl,-O1" 

I found this in the comments thread in bug 65002 "LDFLAGS in Gentoo":
"before we hop into this we need to straighten out LDFLAGS

LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common"
these, for example, are not linker flags per-say ... those are really gcc flags
which pass on to ld

'proper' LDFLAGS in this case would be:
LDFLAGS="-O1 --enable-new-dtags --sort-common"

the issue is that a lot of packages dont do LDFLAGS right ... they often times
group CFLAGS and LDFLAGS together

that means the current/safest way to get these into portage is to add them onto
CFLAGS via the -Wl, pass-through mech

i'd suggest we put off LDFLAGS for now until we can get some mad QA on our
packages and have people do reasearch into how to properly get LDFLAGS into
most packages out there"

Ok, I just tried to compile with MAKEOPTS="j2". Did not work for textinfo-4.8.
With MAKEOPTS="-j2" it worked. Can I continue to do my bootstrap or will my
whole system now be screwed for the future if I change back the "-j2" option to
"j2".

Thanks
Zeno

'j2' is a completely invalid value for MAKEOPTS (just about everything *should*
fail), '-j2' is correct syntax.
Apart from the package affected, I don't see how this relates in any other way
to this bug, though.