Bug 11320

Summary:	xmms-infinity 0.2 fails to build
Product:	Gentoo Linux	Reporter:	Andy Romeril <aromeril>
Component:	New packages	Assignee:	Nick Hadaway <grandmasterlinux>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	High
Version:	1.4_rc1
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Build log for 'xmms-infinity' Output of 'emerge info'

Description Andy Romeril 2002-11-27 18:59:59 UTC

Using Gentoo 1.4rc-1
Pentium 4 - 1.8Ghz

CFLAGS="-march=pentium4 -O3 -pipe"

USE="-3dnow mmx sse sse2 apm pcmcia pnp trusted pda gphoto2 cdr dvd cups
 x opengl -dga xv fbcon directfb -kde -qt -qtmt -arts gnome tcltk imlib
 ncurses readline sdl gif jpeg png tiff avi mpeg quicktime alsa ggi xmms
 oggvorbis pam ssl crypt tcpd mozilla mozaccess-builtin mozctl mozirc
 truetype tetex java perl python samba -nls gpm zlib"

MAKEOPTS="-j2"

FEATURES="sandbox ccache buildpkg"

Comment 1 Andy Romeril 2002-11-27 19:00:52 UTC

Created attachment 6004 [details]
Build log for 'xmms-infinity'

Comment 2 Nick Hadaway 2002-11-29 07:42:50 UTC

hrm... i have just emerged xmms-infinity without a problem...  then again I have
a very up to date system.  gcc-3.2.1 and glibc-2.3.1 

Do you keep your system up to date regularily?  There have been many changes in
the 1.4 profile... Can you put in here the complete output of "emerge info" ?

Comment 3 Andy Romeril 2002-11-29 12:24:49 UTC

Created attachment 6043 [details]
Output of 'emerge info'

I run 'emerge rsync' almost daily, followed by an 'emerge -b -u world'. Output
from 'emerge info' is attached.  As you can see, I am somewhat behind you, but
that may be due to your use of the ACCEPT_KEYWORDS="~x86" setting...

On the latter, I was left with the impression that this was only for those
wishing to be on the complete bleeding edge.  I am misconstruing the warnings
that came with this flag?

Comment 4 Nick Hadaway 2002-11-30 18:00:02 UTC

the ~ is for "unstable" ebuilds but generally the quality is fairly high.  I
have had very little problems when running the unstable packages.

I have seen problems with gcc-2 and gcc-3 with the -march=pentium4 flag ... but
more things are fixed withing gcc-3.2.1 which is currently marked unstable.  It
will be marked stable soon but if you are willing to live on the edge a little
bit i'd encourage you to try the unstable profile.

Based on the log you provided I don't see anything else that immediately sticks
out as a problem.