Dnia 2015-01-23, o godz. 17:56:49 Michael Orlitzky <m...@gentoo.org> napisał(a):
> On 01/23/2015 05:38 PM, Michał Górny wrote: > > > > 3. Put it in an ebuild, after all. This will add a lot of complexity > > but GPG comes for free, plus some people will actually test > > and stabilize it. > > > > I do. It seems like a lot of work, but we can test and quick-stable it. > Thank you. Ebuild committed. Now review the news item :P. -- Best regards, Michał Górny
Title: CPU_FLAGS_X86 introduction Author: MichaŠGórny <mgo...@gentoo.org> Content-Type: text/plain Posted: 2015-01-xx Revision: 1 News-Item-Format: 1.0 Display-If-Keyword: amd64 ~amd64 x86 ~x86 The USE flags corresponding to intruction sets and other features specific to the x86 architecture are being moved into a separate USE flag group called CPU_FLAGS_X86. In order not to lose CPU-specific optimizations, users will be required to update their make.conf (and package.use) file. For example, if the following USE flags were present: USE="mmx mmxext sse sse2 sse3" Those flags need to be copied into: CPU_FLAGS_X86="mmx mmxext sse sse2 sse3" Please note that CPU_FLAGS_X86 is used both on x86 and amd64 systems. When in doubt, please consult profiles/desc/cpu_flags_x86.desc. Most of the flag names match /proc/cpuinfo names, with the notable exception of SSE3 which is called 'pni' in /proc/cpuinfo (please also do not confuse it with distinct SSSE3). To help you enable the correct USE flags, we are providing a Python script tool generates the correct value using your /proc/cpuinfo. It can be found in app-portage/cpuinfo2cpuflags package: $ emerge -1v app-portage/cpuinfo2cpuflags $ cpuinfo2cpuflags-x86.py In order to ensure safe migration and maintain compatibility with external repositories, it is recommended to preserve the old USE settings for a period of one year or until no package of interest is still using them.
pgpWKv40QLbwE.pgp
Description: OpenPGP digital signature
