[gentoo-user] equery, make.conf USE flag mismatch on amd64

[gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

Hello All,

I have the following USE in my make.conf (on an athlon64 machine)
USE="3dnow xorg a52 alsa acpi arts avi berkdb cdr crypt cups dvdr dvd
encode foomaticdb ffmpeg flac gdbm gif gpm gtk gtk2 hal imlib jpeg kde
gnome libg++ libwww lm_sensors mad mikmod mmx motif mpeg mysql ncurses
nls oggvorbis opengl pam pam_console pdflib png python qt quicktime
readline sdl slang spell sse ssl svga tcpd tiff truetype usb X xml2
xmms xv zlib f77 v4l win32codecs"


And when i do: equery uses xawtv i get the following:
[ Searching for packages matching xawtv... ]
[ Colour Code : set unset ]
[ Legend        : Left column  (U) - USE flags from make.conf         
           ]
[                  : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for media-tv/xawtv-3.95-r1 ]
 U I
 + + X         : Adds support for X11
 + + aalib     : Adds support for media-libs/aalib (ASCII-Graphics Library)
 + + alsa      : Adds support for media-libs/alsa-lib (Advanced Linux
Sound Architecture)
 + + dv        : Enables support for a codec used by many camcorders
 + + lirc      : Adds support for lirc (Linux's Infra-Red Remote Control)
 - - mmx       : Adds support for optimizations for Pentium MMX and
Athlon class processors
 + + motif     : Adds motif support (x11-libs/openmotif x11-libs/lesstif)
 + + nls       : Adds Native Language Support (using gettext - GNU
locale utilities)
 + + opengl    : Adds support for OpenGL (3D graphics)
 + + quicktime : Adds support for OpenQuickTime
 + + xext      : Enable use of XFree extentions (DGA,VidMode,DPMS)
 + + xv        : Adds in optional support for the Xvideo extension (an
X API for video playback)
 + + zvbi      : Enable VBI Decoding Library for Zapping


Please note that "mmx" seems to be missing in both columns. despite
that its there in my USE in make.conf

When i do: emerge --pretend --newuse xawtv

It basically reports that nothing need to be done


Is this a bug in equery or is it that i can't set mmx on an Athlon64 ?

I'm using:
Portage version 2.0.54
Gentoolkit version 0.2.1


Thanks

Kumar

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Jeremy Olexa]

>Please note that "mmx" seems to be missing in both columns. despite
>that its there in my USE in make.conf
>  
>
`cat /proc/cpuinfo |grep flags` to see what flags your cpu uses. Perhaps 
your cpu doesn't handle mmx?

Sorry, I don't have expierence with your cpu.

-Jeremy
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Patrick B�rjesson]

[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]

On 2006-03-08 00:20, Kumar Golap uttered these thoughts:
> I have the following USE in my make.conf (on an athlon64 machine)
> USE="3dnow xorg a52 alsa acpi arts avi berkdb cdr crypt cups dvdr dvd
> encode foomaticdb ffmpeg flac gdbm gif gpm gtk gtk2 hal imlib jpeg kde
> gnome libg++ libwww lm_sensors mad mikmod mmx motif mpeg mysql ncurses
> nls oggvorbis opengl pam pam_console pdflib png python qt quicktime
> readline sdl slang spell sse ssl svga tcpd tiff truetype usb X xml2
> xmms xv zlib f77 v4l win32codecs"
> 
> 
> And when i do: equery uses xawtv i get the following:
> [ Searching for packages matching xawtv... ]
> [ Colour Code : set unset ]
> [ Legend        : Left column  (U) - USE flags from make.conf         
>            ]
> [                  : Right column (I) - USE flags packages was installed with ]
> [ Found these USE variables for media-tv/xawtv-3.95-r1 ]
[snip]
>  - - mmx       : Adds support for optimizations for Pentium MMX and
> Athlon class processors
[snip]

> Please note that "mmx" seems to be missing in both columns. despite
> that its there in my USE in make.conf
> 
> When i do: emerge --pretend --newuse xawtv
> 
> It basically reports that nothing need to be done

Try a
$ emerge -vp xawtv
and see if the mmx useflag is set in that output... If not, then do a 
$ emerge --info
and see if the useflag output from that command includes mmx. If not,
you've probably got a typo of some sort in your make.conf since the mmx
useflag is not profile-masked on the amd64 (use.mask under your
/etc/make.profile symlink). 

> Is this a bug in equery or is it that i can't set mmx on an Athlon64 ?

Might be, but probably not ;)


Regards,
Patrick B�rjesson

-- 
/  ()  The ASCII Ribbon Campaign - against HTML Email
\  /\   and proprietary formats.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

Hi again...

The athlon 64 does have mmx as flags ...so that's not an issue

when i do emerge -pv ...it does seem that iits not using mmx

And i have an interesting problem when i do : emerge --info

I get this in my USE flags

USE="amd64 X a52 aalib acpi alsa arts audiofile avi berkdb
bitmap-fonts bzip2 cdr crypt cups curl directfb dri dvd dvdr eds
emboss encode esd exif expat f77 fam ffmpeg flac foomaticdb fortran gd
gdbm gif glut gnome gpm gstreamer gtk gtk2 hal idn imagemagick imlib
ipv6 java jpeg kde lcms libcaca libg++ libwww lirc lm_sensors lzw
lzw-tiff mad mikmod mng motif mozilla mp3 mpeg mysql ncurses nls nptl
ogg oggvorbis openal opengl pam pam_console pcre pdflib perl png
python qt quicktime readline recode scanner sdl slang speex spell
sqlite ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts
udev usb userlocales v4l vorbis xine xml2 xmms xorg xpm xv zlib
userland_GNU kernel_linux elibc_glibc"

which is a different version from what i have in the actual make.conf

 So i wonder if this is cached somewhere and emerge is not reading my
new version of /etc/make.conf
So from where is it generating that USE flags or have i corrupted my
portage tree by any chance ?




regards

Kumar

On 3/8/06, Patrick B�rjesson <psycho@rift.ath.cx> wrote:
> On 2006-03-08 00:20, Kumar Golap uttered these thoughts:
> > I have the following USE in my make.conf (on an athlon64 machine)
> > USE="3dnow xorg a52 alsa acpi arts avi berkdb cdr crypt cups dvdr dvd
> > encode foomaticdb ffmpeg flac gdbm gif gpm gtk gtk2 hal imlib jpeg kde
> > gnome libg++ libwww lm_sensors mad mikmod mmx motif mpeg mysql ncurses
> > nls oggvorbis opengl pam pam_console pdflib png python qt quicktime
> > readline sdl slang spell sse ssl svga tcpd tiff truetype usb X xml2
> > xmms xv zlib f77 v4l win32codecs"
> >
> >
> > And when i do: equery uses xawtv i get the following:
> > [ Searching for packages matching xawtv... ]
> > [ Colour Code : set unset ]
> > [ Legend        : Left column  (U) - USE flags from make.conf
> >            ]
> > [                  : Right column (I) - USE flags packages was installed with ]
> > [ Found these USE variables for media-tv/xawtv-3.95-r1 ]
> [snip]
> >  - - mmx       : Adds support for optimizations for Pentium MMX and
> > Athlon class processors
> [snip]
>
> > Please note that "mmx" seems to be missing in both columns. despite
> > that its there in my USE in make.conf
> >
> > When i do: emerge --pretend --newuse xawtv
> >
> > It basically reports that nothing need to be done
>
> Try a
> $ emerge -vp xawtv
> and see if the mmx useflag is set in that output... If not, then do a
> $ emerge --info
> and see if the useflag output from that command includes mmx. If not,
> you've probably got a typo of some sort in your make.conf since the mmx
> useflag is not profile-masked on the amd64 (use.mask under your
> /etc/make.profile symlink).
>
> > Is this a bug in equery or is it that i can't set mmx on an Athlon64 ?
>
> Might be, but probably not ;)
>
>
> Regards,
> Patrick B�rjesson
>
> --
> /  ()  The ASCII Ribbon Campaign - against HTML Email
> \  /\   and proprietary formats.
>
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

In fact if i remove the  USE line from the make.conf file ...and i do
emerge --info ...it is showing USE flags that i have no clue from
where its coming. I guess that that is what is overiding my changes in
USE i.e  its been ignoring the fact that wanted   mmx and 3dnow etc to
be used.


In case that can give you a clue below is the whole
emerge --info even after i commented out my USE line in make.conf

Thanks a lot for all the help...

Kumar




 # emerge --info
Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.4, glibc-2.3.5-r2,
2.6.15-gentoo-r5 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
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-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-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/lib64/mozilla/defaults/pref /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/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ "
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aalib acpi alsa arts audiofile avi berkdb
bitmap-fonts bzip2 cdr crypt cups curl directfb dri dvd dvdr eds
emboss encode esd exif expat f77 fam ffmpeg flac foomaticdb fortran gd
gdbm gif glut gnome gpm gstreamer gtk gtk2 hal idn imagemagick imlib
ipv6 java jpeg kde lcms libcaca libg++ libwww lirc lm_sensors lzw
lzw-tiff mad mikmod mng motif mozilla mp3 mpeg mysql ncurses nls nptl
ogg oggvorbis openal opengl pam pam_console pcre pdflib perl png
python qt quicktime readline recode scanner sdl slang speex spell
sqlite ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts
udev usb userlocales v4l vorbis xine xml2 xmms xorg xpm xv zlib
userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Martins Steinbergs]

On Wednesday 08 March 2006 18:33, Kumar Golap wrote:
> In fact if i remove the  USE line from the make.conf file ...and i do
> emerge --info ...it is showing USE flags that i have no clue from
> where its coming. I guess that that is what is overiding my changes in
> USE i.e  its been ignoring the fact that wanted   mmx and 3dnow etc to
> be used.
>
>
> In case that can give you a clue below is the whole
> emerge --info even after i commented out my USE line in make.conf
>
> Thanks a lot for all the help...
>
> Kumar
>
>

I would advise to read "6. Installing the Gentoo Base System --> Configuring 
the USE variable"

amd64 version:
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6#doc_chap2


martins
-- 
Linux 2.6.15-gentoo-r7 AMD Athlon(tm) 64 Processor 3200+
 19:14:26 up 45 min,  5 users,  load average: 1.40, 1.44, 1.23
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

Thanks now I understand the default USE flags I see, I think. And
apologies for not searching the manual first.

But I still do not understand  why flags like mmx (or 3dnow) flags
that i put in the /etc/make.conf file is not getting picked up.

Am i right in my understanding that emerge --info reports the "sum" of
all the USE flags from all the make.defaults and /etc/make.conf ? so
it should show mmx when i put it there.

regards

Kumar


On 3/8/06, Martins Steinbergs <mar@ml.lv> wrote:
> On Wednesday 08 March 2006 18:33, Kumar Golap wrote:
> > In fact if i remove the  USE line from the make.conf file ...and i do
> > emerge --info ...it is showing USE flags that i have no clue from
> > where its coming. I guess that that is what is overiding my changes in
> > USE i.e  its been ignoring the fact that wanted   mmx and 3dnow etc to
> > be used.
> >
> >
> > In case that can give you a clue below is the whole
> > emerge --info even after i commented out my USE line in make.conf
> >
> > Thanks a lot for all the help...
> >
> > Kumar
> >
> >
>
> I would advise to read "6. Installing the Gentoo Base System --> Configuring
> the USE variable"
>
> amd64 version:
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6#doc_chap2
>
>
> martins
> --
> Linux 2.6.15-gentoo-r7 AMD Athlon(tm) 64 Processor 3200+
>  19:14:26 up 45 min,  5 users,  load average: 1.40, 1.44, 1.23
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Paul Varner]

On Wed, 2006-03-08 at 11:16 -0700, Kumar Golap wrote:
> Thanks now I understand the default USE flags I see, I think. And
> apologies for not searching the manual first.
> 
> But I still do not understand  why flags like mmx (or 3dnow) flags
> that i put in the /etc/make.conf file is not getting picked up.
> 
> Am i right in my understanding that emerge --info reports the "sum" of
> all the USE flags from all the make.defaults and /etc/make.conf ? so
> it should show mmx when i put it there.

The flags are probably masked by your profile. What does 'emerge
--pretend --verbose xawtv' show?

Regards,
Paul
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Holly Bostick]

Kumar Golap schreef:
> Thanks now I understand the default USE flags I see, I think. And 
> apologies for not searching the manual first.
> 
> But I still do not understand  why flags like mmx (or 3dnow) flags 
> that i put in the /etc/make.conf file is not getting picked up.
> 
> Am i right in my understanding that emerge --info reports the "sum" 
> of all the USE flags from all the make.defaults and /etc/make.conf ? 
> so it should show mmx when i put it there.
> 

Yes, it should... unless your USE= line got wrapped somehow (since a
previous poster has said that the flag is not masked for your $ARCH).

Now, this is going to sound weird, but it's happened to me on more than
one occasion.

I would suggest opening the file (/etc/make.conf), as root, with nano,
and going to the end of the first displayed line of the USE= variable,
and if there is not an "$" under your cursor (to indicate a non-wrapped
line that is too long to be displayed, which would be what we want, but
not what I expect :-) ), but rather empty space, hit the "Delete" key
(to delete the soft return that shouldn't be there, but is).

If this then brings the next section of the USE flags up and smashes
them against the last displayed flag on the line you're on, then that
was your problem... line wrapping. Hit the space bar to separate the
last entry of the first "line" and the first entry of the second "line,
then rinse and repeat until all the flags are on one line, then Ctrl+O
to save. Don't hit any other keys, just save, and then Ctrl-X to get out.

Then run emerge --info again and see if things have improved.

Not sure why sometimes lines get wrapped when they shouldn't be, but it
does happen (even in nano, where it shouldn't, and certainly in GUI
editors, if you set it that way without thinking), and it can have
unexpected consequences (like this).

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Abhay Kedia]

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

On Thursday 09 March 2006 00:04, Holly Bostick wrote:
>
> Not sure why sometimes lines get wrapped when they shouldn't be, but it
> does happen (even in nano, where it shouldn't, and certainly in GUI
> editors, if you set it that way without thinking), and it can have
> unexpected consequences (like this).
>
cos it is default behavior of nano? you can override it by issuing "-w" option 
to nano. i always run nano with -w.

-- 
Regards,
Abhay

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Martins Steinbergs]

On Wednesday 08 March 2006 20:16, Kumar Golap wrote:
> Thanks now I understand the default USE flags I see, I think. And
> apologies for not searching the manual first.
>
> But I still do not understand  why flags like mmx (or 3dnow) flags
> that i put in the /etc/make.conf file is not getting picked up.
>
> Am i right in my understanding that emerge --info reports the "sum" of
> all the USE flags from all the make.defaults and /etc/make.conf ? so
> it should show mmx when i put it there.
>
> regards
>
> Kumar

partial answer is in file /usr/portage/profiles/default-linux/use.mask

but still dont have a clue why these flags doesnt show 'emerge --info' if they 
are in /etc/make.conf

martins
-- 
Linux 2.6.15-gentoo-r7 AMD Athlon(tm) 64 Processor 3200+
 21:22:34 up  2:53,  5 users,  load average: 1.12, 1.15, 1.10
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

Thanks all for your help...and I know why now mmx flag was getting
masked. Its in the use.mask as suggested by Martins.

Attached is the use.mask file i have ...that file gets
updated/overwritten every time i do a "emerge --sync",  right ? For
some reason all the flags under x86/amd are uncommented... when i
comment them out then emerge --info shows me mmx etc...

For now i can live with commenting them out. But I did not realize i
had to do that...i never had to do this before on other machines (not
amd64 though...x86 and ppc64).

regards

Kumar

[-- Attachment #2: use.mask --]
[-- Type: application/octet-stream, Size: 778 bytes --]

# Copyright 2004 Gentoo Foundation.
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/use.mask,v 1.18 2006/03/03 01:46:36 lu_zero Exp $

# This file masks out USE flags that are simply NOT allowed in the default
# profile for any architecture.  This works, for example, if a non-default
# profile (such as the selinux profiles) have a USE flag associated with
# them.

uclibc

# USE flags only valid on Mac OS X
aqua
coreaudio

# amd64 only:
emul-linux-x86

# sparc only:
ultra1

# x86 only
win32codecs
kqemu

# x86/amd64 only:
mmx
mmx2
sse
sse2
3dnow
3dnowext

# ppc only:
altivec
ppcsha1
pbbuttonsd

# mips only:
n32
n64

# Only used by mips and old amd64 profiles
multilib

# ppc and x86/amd64
x264

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Boyd Stephen Smith Jr.]

On Wednesday 08 March 2006 21:20, "Kumar Golap" <tizan.moris@gmail.com> 
wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on 
amd64':
> Thanks all for your help...and I know why now mmx flag was getting
> masked. Its in the use.mask as suggested by Martins.
>
> Attached is the use.mask file i have ...that file gets
> updated/overwritten every time i do a "emerge --sync",  right ?

Yep.

> For now i can live with commenting them out. But I did not realize i
> had to do that...i never had to do this before on other machines (not
> amd64 though...x86 and ppc64).

You don't.  In the general case, you can add the flags you want unmasked 
to /etc/portage/profile/use.mask like so:
-win32codecs

In this /specific/ case, you don't have to because the ebuilds and gcc know 
that x86_64 CHOST means that mmx etc. ARE supported and they will 
hard-enable them (you may not turn them off).

Normally, you won't want to mask or unmask USE flags yourself.  They are 
turned on or off by the developers because they are either redundant or 
broken.

I don't know why I didn't jump in the conversation earlier; I guess I hoped 
someone here could read 'man portage'.  There's full documentation for 
use.mask and over-riding your profile in there.

*grumble grumble*

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

Apologies for not having done my research properly....




> In this /specific/ case, you don't have to because the ebuilds and gcc know
> that x86_64 CHOST means that mmx etc. ARE supported and they will
> hard-enable them (you may not turn them off).
>

Do you mean that, say, xawtv would have been built with mmx for an
amd64 arch...despite that "equery uses" say its not ? Because that
what confused me....

Thanks

Kumar

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Ryan Tandy]

Kumar Golap wrote:
> Apologies for not having done my research properly....
>
>
>
>
>   
>> In this /specific/ case, you don't have to because the ebuilds and gcc know
>> that x86_64 CHOST means that mmx etc. ARE supported and they will
>> hard-enable them (you may not turn them off).
>>
>>     
>
> Do you mean that, say, xawtv would have been built with mmx for an
> amd64 arch...despite that "equery uses" say its not ? Because that
> what confused me....
>
> Thanks
>
> Kumar
>
>   
There's a difference.  Due to your CHOST, the compiler knows what 
optimizations are supported by your CPU and will automatically generate 
code that makes the best possible use of them.  On the other hand, the 
"mmx" USE flag's most likely effect is to activate portions of the 
program's code that explicitly invoke MMX CPU instructions - for 
example, through assembly inlining.  I don't know much about 64-bit 
systems, so I'd recommend leaving "mmx" masked as per your profile, or 
perhaps unmasking it just to test one or two packages for stability, and 
then unmasking permanently if you have no problems.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Boyd Stephen Smith Jr.]

On Wednesday 08 March 2006 21:49, "Kumar Golap" <tizan.moris@gmail.com> 
wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on 
amd64':
> Apologies for not having done my research properly....

No problem, it happens.  Truth be told it's probably more of a problem with 
people being unable to /find/ the manual than being unwilling to /read/ 
it.

Besides, the age-old man command, and it's younger upstart info, are 
quickly being deprecated in favor of simply pointing someone to a web 
page.  I find this unfortunate, at best.

BTW, if you don't like consoles or fixed-width fonts make you itch, you can 
always use a man:/ or info:/ URL in konqueror.  (Not sure what the 
Gnome/FB/BB/OB/ION/WMII/RP/other people use...)

> > In this /specific/ case, you don't have to because the ebuilds and gcc
> > know that x86_64 CHOST means that mmx etc. ARE supported and they will
> > hard-enable them (you may not turn them off).
>
> Do you mean that, say, xawtv would have been built with mmx for an
> amd64 arch...despite that "equery uses" say its not ? Because that
> what confused me....

Yes.  It will.  The ebuild controls which arguments are passed to 
configure/make so it can decide on the combination of you USE flags and 
profile.  I'm not sure if it is portage magic (the portage 'use' command 
available in ebuilds doing some check on CHOST) or just ebuild maintainers 
explicitly checking for an x86_64 CHOST, but you will get mmx/sse 
optimizations without any special USE flags.

You probably /should/ set your -march flag (or at least -mcpu) in CFLAGS, 
so that gcc will optimize to your particular processor, including extended 
instruction sets.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[wieseltux23]

[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]

www.wolfspakt.de/spiel.php?id=7358

On Wed, 8 Mar 2006 22:24:25 -0600
"Boyd Stephen Smith Jr." <bss03@volumehost.net> wrote:

> On Wednesday 08 March 2006 21:49, "Kumar Golap" <tizan.moris@gmail.com> 
> wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on 
> amd64':
> > Apologies for not having done my research properly....
> 
> No problem, it happens.  Truth be told it's probably more of a problem with 
> people being unable to /find/ the manual than being unwilling to /read/ 
> it.
> 
> Besides, the age-old man command, and it's younger upstart info, are 
> quickly being deprecated in favor of simply pointing someone to a web 
> page.  I find this unfortunate, at best.
> 
> BTW, if you don't like consoles or fixed-width fonts make you itch, you can 
> always use a man:/ or info:/ URL in konqueror.  (Not sure what the 
> Gnome/FB/BB/OB/ION/WMII/RP/other people use...)
> 
> > > In this /specific/ case, you don't have to because the ebuilds and gcc
> > > know that x86_64 CHOST means that mmx etc. ARE supported and they will
> > > hard-enable them (you may not turn them off).
> >
> > Do you mean that, say, xawtv would have been built with mmx for an
> > amd64 arch...despite that "equery uses" say its not ? Because that
> > what confused me....
> 
> Yes.  It will.  The ebuild controls which arguments are passed to 
> configure/make so it can decide on the combination of you USE flags and 
> profile.  I'm not sure if it is portage magic (the portage 'use' command 
> available in ebuilds doing some check on CHOST) or just ebuild maintainers 
> explicitly checking for an x86_64 CHOST, but you will get mmx/sse 
> optimizations without any special USE flags.
> 
> You probably /should/ set your -march flag (or at least -mcpu) in CFLAGS, 
> so that gcc will optimize to your particular processor, including extended 
> instruction sets.
> 
> -- 
> "If there's one thing we've established over the years,
> it's that the vast majority of our users don't have the slightest
> clue what's best for them in terms of package stability."
> -- Gentoo Developer Ciaran McCreesh
> -- 
> gentoo-user@gentoo.org mailing list
> 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Richard Fish]

On 3/8/06, Kumar Golap <tizan.moris@gmail.com> wrote:
> Thanks all for your help...and I know why now mmx flag was getting
> masked. Its in the use.mask as suggested by Martins.

The mmx USE flag is not supported on the amd64 profile.  The processor
does support mmx instructions, but (I think) only when operating in
32-bit mode.  So it probably doesn't make sense to have an amd64
profile with the mmx/sse/3dnow use flags.  Presumably there are better
processor instructions for a true 64-bit multi-media application to
use...

If you really want to applications to use mmx/sse/3dnow for some
reason, you will need to remain in 32-bit mode with the x86 profile. 
Or I suppose you could use some kind of chroot/cross-compilation
environment...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Kumar Golap]

> The mmx USE flag is not supported on the amd64 profile.  The processor
> does support mmx instructions, but (I think) only when operating in
> 32-bit mode.  So it probably doesn't make sense to have an amd64
> profile with the mmx/sse/3dnow use flags.  Presumably there are better
> processor instructions for a true 64-bit multi-media application to
> use...
>

Ah alright thanks ...i did not know  that mmx 3dnow flags /
instruction set was for the 32 bit operation only


Sorry again if i've wasted you guys time ...but i learned a few things today.

regards

Kumar

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Richard Fish]

On 3/8/06, Kumar Golap <tizan.moris@gmail.com> wrote:
> > The mmx USE flag is not supported on the amd64 profile.  The processor
> > does support mmx instructions, but (I think) only when operating in
> > 32-bit mode.  So it probably doesn't make sense to have an amd64
> > profile with the mmx/sse/3dnow use flags.  Presumably there are better
> > processor instructions for a true 64-bit multi-media application to
> > use...
> >
>
> Ah alright thanks ...i did not know  that mmx 3dnow flags /
> instruction set was for the 32 bit operation only

Don't thank me.  I was wrong.

As an example, take a look at the following from the mplayer ebuild:

       # mplayer now contains SIMD assembler code for amd64
        # AMD64 Team decided to hardenable SIMD assembler for all users
        # Danny van Dyk <kugelfang@gentoo.org> 2005/01/11
        if use amd64; then
                myconf="${myconf} --enable-3dnow --enable-3dnowex
--enable-sse --enable-sse2 --enable-mmx --enable-mmx2"
        fi

In this case, since mplayer knows how to use both 64-bit and mmx/sse
instructions simultaneously, the ebuild adds all of this stuff for
amd64 users.  No use flags required.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64

[Boyd Stephen Smith Jr.]

On Wednesday 08 March 2006 21:45, "Richard Fish" <bigfish@asmallpond.org> 
wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on 
amd64':
> On 3/8/06, Kumar Golap <tizan.moris@gmail.com> wrote:
> > Thanks all for your help...and I know why now mmx flag was getting
> > masked. Its in the use.mask as suggested by Martins.
>
> The mmx USE flag is not supported on the amd64 profile.  The processor
> does support mmx instructions, but (I think) only when operating in
> 32-bit mode. 

I know it supports them, and I'm fairly sure the work in 64-bit mode.

> So it probably doesn't make sense to have an amd64 
> profile with the mmx/sse/3dnow use flags.  Presumably there are better
> processor instructions for a true 64-bit multi-media application to
> use...

Actually, since ALL x86_64 processors support these instructions, it's 
kinda silly to compile without using these instruction sets.  There are 
few, if any, extended instruction sets for x86_64, AFAIK, so mmx3/sse2 is 
probably the fastest code path for multimedia operations.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-user@gentoo.org mailing list