Posted 30 January 2015 - 02:42 PM
Posted 30 January 2015 - 03:14 PM
IMHO it would be wise to use portage's news feature for something like this. I just happened to come here and find it, but it would have been useful to see a new news item was available after syncing and then view it with `eselect news read`.
Or has the news feature been deprecated?
- spectromas likes this
Posted 23 February 2015 - 04:00 PM
New user and poster here,
This is a good feature, thank you for the script it worked well.
However I have an observation about the documentation, in the op post and the wiki there is reference to adding the flags as such
users will be required to update their make.conf (and package.use) file
there is an example for the /etc/portage/make.conf but not /etc/portage/package.use.
In my case I added the recommended lines to both files.
This ends up creating a cryptic error message when you try to emerge something, the error below.
Invalid atom in /etc/portage/package.use: CPU_FLAGS_X86="avx
So I comment out the line added to the package.use and all is well.
The line added to both files from the script was the line below ( created from memory, funtoo is compiling away at the moment so not accessible)
CPU_FLAGS_X86="avx other ones here mmx mmxext sse sse2 sse3"
Should the docs exclude the info to add this line to package.use or give an example of use maybe?
Posted 26 February 2015 - 12:46 AM
I find this interesting, while I do not understand it yet.
What is the reason for the change, what happened ... what changed to require this.
I do not doubt funtoo's great wisdom, just trying to understand why, so can help explain the change to others.
I run the cpuinfo2cpuflags-x86 and get
CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3"
CFLAGS="-mtune=generic -O2 -pipe"
CXXFLAGS="-mtune=generic -O2 -pipe"
While this is what I have currently in make.conf .... the new flags seems like I would need to rebuild my whole system.
I just want to ask why the changes, and what benefits it has?
What if I simply sit back and do nothing?
Not angry, just uninformed and curious about this change.
Posted 26 February 2015 - 04:31 PM
AFAIK, the CPU_FLAGS_X86 variable is for ebuilds that contain the option for those flags whereas the CHOST, CFLAGS and CXXFLAGS are for EVERY ebuild.
If you want to see what would be recompiled, add the result that you posted in your make.conf file, and run a --pretend emerge:
`emerge world -uDNpv --with-bdeps=y`
IIRC, it was only about 22 packages on my setup.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users