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
www.wolfspakt.de/spiel.php?id=7358
On Wed, 8 Mar 2006 22:24:25 -0600
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Wednesday 08 March 2006 21:49, Kumar Golap [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on
amd64':
Apologies for not having done
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
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
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
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
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
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
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
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
On Wednesday 08 March 2006 21:20, Kumar Golap [EMAIL PROTECTED]
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
On 3/8/06, Kumar Golap [EMAIL PROTECTED] 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
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
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
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,
On Wednesday 08 March 2006 21:45, Richard Fish [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on
amd64':
On 3/8/06, Kumar Golap [EMAIL PROTECTED] wrote:
Thanks all for your help...and I know why now mmx flag was getting
masked. Its in the use.mask
On 3/8/06, Kumar Golap [EMAIL PROTECTED] 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
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
18 matches
Mail list logo
