Re: [gentoo-amd64] 2005.0 and multilib
Hi,
Pascal BERTIN wrote:
> grep multi /usr/portage/media-video/nvidia-glx/nvidia-glx-1.0.6629-r1.ebuild
> IUSE="multilib"
> PDEPEND="amd64? ( multilib? (
>
>>=app-emulation/emul-linux-x86-nvidia-${PV} ) )"
This is bug #87587 [1], feel free to CC yourself. a quick workaround
would be to stick =media-video/nvidia-glx-1.0.6629-r5 ~amd64 into
/etc/portage/package.keywords
Greetings,
blubb
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
Octavio Ruiz (Ta^3) wrote: > David Klaftenegger, who happens to be smarter than you, thinks: Thanks for the compliment >>Pascal BERTIN wrote: >> >>>Hi all, >>> >>>I upgraded from 2004.3 to 2005.0 using the Makefile method, >>>everything went OK, >>> >>>but after all this, an emerge --newuse -puDv world >>>wants to remerge gcc with following USE flag : (-multilib)* >>> >>>so, as 2005.0 is said to have multilib enabled by default, why would >>>portage re-merge gcc without multilib ? >> >>That is a (quite common) misunderstanding: You just can't DISABLE it >>anymore, > > > Well, you can always use the default-linux/amd64/2005.0/no-multilib profile > :-D > > >>the USE-flag is no longer optional, and therefore written in >>brackets. > > > Should this be inside the Gentoo/AMD64 Technotes? > Probably it would help against all that uncertainty that obviously is caused by a behavior that emerge shows here. Just a small remark, that multilib USE flag isn't used on amd64. It is not even a bug, it's just a flaw in design that a USE-flag, that is not available on this arch is always disabled. In our amd64 case this means multilib-USE-flag is disabled because the multilib support is not optional. (Of course unless you use the 2005.0/no-multilib profile as correctly mentioned above) Greetings, David -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
Well, it could well be a 'harmless' bug of misrepresentation of USE flags by emerge (say multilib is defined so deep inside the profile, that higher level tools don't see it, whatever this idea means). But the suggestion to irreversibly recompile gcc seemingly disabling multilib is certainly scaring :) > Hmmm, my profile says (-multilib) too, yet I am dead certain that the 32bit libs were compiled and placed in the right folders. > > On Fri, 01 Apr 2005 12:27:11 +0200 > Pascal BERTIN <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > I upgraded from 2004.3 to 2005.0 using the Makefile method, > > everything went OK, > > > > but after all this, an emerge --newuse -puDv world > > wants to remerge gcc with following USE flag : (-multilib)* > > > > so, as 2005.0 is said to have multilib enabled by default, why would > > portage re-merge gcc without multilib ? > > > > > > > > > > > > -- > > gentoo-amd64@gentoo.org mailing list > > -- Dmitri PogosyanDepartment of Physics Associate ProfessorUniversity of Alberta tel 1-780-492-2150 412 Avadh Bhatia Physics Labs fax 1-780-492-0714 Edmonton, AB, T6G 2J1, CANADA -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
Yes Dmitri,
You understood exactly my point,
from man emerge :
[...]
A USE flag in pparenthesis, like (-selinux), is always disabled and
shows that the flag is not available for the current system profile.
[...]
also, I have nvidia-glx which was merged without profile change without
multilib and is not proposed for an update. (emerge --newuse -pv
nvidia-glx returns also (-multilib) with no star)
also, consider the following two commands :
emerge --newuse -peDtv nvidia-glx |grep emul
(empty result implying that nvidia-glx does not depend of anything with
emul in its name on my system)
grep multi /usr/portage/media-video/nvidia-glx/nvidia-glx-1.0.6629-r1.ebuild
IUSE="multilib"
PDEPEND="amd64? ( multilib? (
>=app-emulation/emul-linux-x86-nvidia-${PV} ) )"
(in case you ask 1.0.6629-r1 is the one that the emerge command would re
merge)
so it looks that on my system, multilib is not set
(also, emerge --info |grep multilib => nothing)
Pascal
Dmitri Pogosyan wrote:
>David, still unclear.
>
>We have
>
>(-multilib)*
>
>Yes, brackets mean that the parameter can be changed. However,
>a) Inside the bracket is the default (unchangable value). Seeing there
> -multilib means for me that default is multilib disabled.
>b) Star (*) means that the parameter is changed relative to the value gcc
> was compiled with before. For me and the author of question, before
> gcc was compiled with multilib enabled. Thus star indicates that
> the new compilation will change that.
>
>Having alredy installed multilib gcc,
>I would expect to see (multilib) among USE flags, not (-multilib)*
>
>
>
>
>
>>Pascal BERTIN wrote:
>>
>>
>>>Hi all,
>>>
>>>I upgraded from 2004.3 to 2005.0 using the Makefile method,
>>>everything went OK,
>>>
>>>but after all this, an emerge --newuse -puDv world
>>>wants to remerge gcc with following USE flag : (-multilib)*
>>>
>>>so, as 2005.0 is said to have multilib enabled by default, why would
>>>portage re-merge gcc without multilib ?
>>>
>>>
>>That is a (quite common) misunderstanding: You just can't DISABLE it
>>anymore, the USE-flag is no longer optional, and therefore written in
>>brackets.
>>
>>Greetings,
>>David
>>
>>--
>>gentoo-amd64@gentoo.org mailing list
>>
>>
>
>
>
>--
>Dmitri PogosyanDepartment of Physics
>Associate ProfessorUniversity of Alberta
>tel 1-780-492-2150 412 Avadh Bhatia Physics Labs
>fax 1-780-492-0714 Edmonton, AB, T6G 2J1, CANADA
>
>
>
>--
>gentoo-amd64@gentoo.org mailing list
>
>
>
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
Hmmm, my profile says (-multilib) too, yet I am dead certain that the 32bit libs were compiled and placed in the right folders. On Fri, 01 Apr 2005 12:27:11 +0200 Pascal BERTIN <[EMAIL PROTECTED]> wrote: > Hi all, > > I upgraded from 2004.3 to 2005.0 using the Makefile method, > everything went OK, > > but after all this, an emerge --newuse -puDv world > wants to remerge gcc with following USE flag : (-multilib)* > > so, as 2005.0 is said to have multilib enabled by default, why would > portage re-merge gcc without multilib ? > > > > > > -- > gentoo-amd64@gentoo.org mailing list > pgpaAvNss9JHX.pgp Description: PGP signature
Re: [gentoo-amd64] 2005.0 and multilib
David, still unclear. We have (-multilib)* Yes, brackets mean that the parameter can be changed. However, a) Inside the bracket is the default (unchangable value). Seeing there -multilib means for me that default is multilib disabled. b) Star (*) means that the parameter is changed relative to the value gcc was compiled with before. For me and the author of question, before gcc was compiled with multilib enabled. Thus star indicates that the new compilation will change that. Having alredy installed multilib gcc, I would expect to see (multilib) among USE flags, not (-multilib)* > Pascal BERTIN wrote: > > Hi all, > > > > I upgraded from 2004.3 to 2005.0 using the Makefile method, > > everything went OK, > > > > but after all this, an emerge --newuse -puDv world > > wants to remerge gcc with following USE flag : (-multilib)* > > > > so, as 2005.0 is said to have multilib enabled by default, why would > > portage re-merge gcc without multilib ? > > That is a (quite common) misunderstanding: You just can't DISABLE it > anymore, the USE-flag is no longer optional, and therefore written in > brackets. > > Greetings, > David > > -- > gentoo-amd64@gentoo.org mailing list -- Dmitri PogosyanDepartment of Physics Associate ProfessorUniversity of Alberta tel 1-780-492-2150 412 Avadh Bhatia Physics Labs fax 1-780-492-0714 Edmonton, AB, T6G 2J1, CANADA -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
David Klaftenegger, who happens to be smarter than you, thinks: > Pascal BERTIN wrote: > > Hi all, > > > > I upgraded from 2004.3 to 2005.0 using the Makefile method, > > everything went OK, > > > > but after all this, an emerge --newuse -puDv world > > wants to remerge gcc with following USE flag : (-multilib)* > > > > so, as 2005.0 is said to have multilib enabled by default, why would > > portage re-merge gcc without multilib ? > > That is a (quite common) misunderstanding: You just can't DISABLE it > anymore, Well, you can always use the default-linux/amd64/2005.0/no-multilib profile :-D > the USE-flag is no longer optional, and therefore written in > brackets. Should this be inside the Gentoo/AMD64 Technotes? -- micro: Thinker toys. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] 2005.0 and multilib
Pascal BERTIN wrote: > Hi all, > > I upgraded from 2004.3 to 2005.0 using the Makefile method, > everything went OK, > > but after all this, an emerge --newuse -puDv world > wants to remerge gcc with following USE flag : (-multilib)* > > so, as 2005.0 is said to have multilib enabled by default, why would > portage re-merge gcc without multilib ? That is a (quite common) misunderstanding: You just can't DISABLE it anymore, the USE-flag is no longer optional, and therefore written in brackets. Greetings, David -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] 2005.0 and multilib
Hi all, I upgraded from 2004.3 to 2005.0 using the Makefile method, everything went OK, but after all this, an emerge --newuse -puDv world wants to remerge gcc with following USE flag : (-multilib)* so, as 2005.0 is said to have multilib enabled by default, why would portage re-merge gcc without multilib ? -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] 2005.0 and multilib
Hi all, I upgraded from 2004.3 to 2005.0 using the Makefile method, everything went OK, but after all this, an emerge --newuse -puDv world wants to remerge gcc with following USE flag : (-multilib)* so, as 2005.0 is said to have multilib enabled by default, why would portage re-merge gcc without multilib ? -- gentoo-amd64@gentoo.org mailing list
