Funtoo Linux BDFL drobbins Posted March 29, 2015 Funtoo Linux BDFL Report Share Posted March 29, 2015 Hi All, If you have installed a new Funtoo Linux system in the last week, you may have noticed something interesting -- /etc/make.conf is EMPTY and eselect profile show shows something new -- a subarch profile: test / # eselect profile show Currently set profiles: arch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit build: gentoo:funtoo/1.0/linux-gnu/build/current flavor: gentoo:funtoo/1.0/linux-gnu/flavor/core subarch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 What's going on? This is part, or maybe culmination of an ongoing effort to simplify /etc/make.conf. While it is still possible to set CFLAGS in /etc/make.conf, by default, these settings are now defined in a subarch profile. By default, new stage3's will have a subarch profile set, but existing Funtoo systems don't need to have one set. If you'd like to set a subarch profile, you can do so by ensuring you have the latest eselect installed and using the "eselect profile set-subarch" command. What are the benefits of subarch profiles? Of course, the first big benefit is to keep /etc/make.conf clean. Subarch profiles, along with flavors and mix-ins, are designed to help keep /etc/make.conf tidy and only contain the tweaks you personally need for your system. It also assists with Metro, our stage building tool. Metro no longer has to store all the CFLAGS settings for each subarch -- these are now integrated into the Portage tree, in one place. And also, this allows us to fix and improve subarches over time, and you automatically benefit from any improvements with an emerge --sync. Hope you enjoy the new system, Daniel swamprabbit, fabiobeneditto, spectromas and 1 other 4 Link to comment Share on other sites More sharing options...
jorgicio Posted March 30, 2015 Report Share Posted March 30, 2015 That's pretty good, but... how about the subarchs with AVX, AVX2, etc. ? (SandyBridge) My CFLAGS is "-march=corei7-avx -O2 -pipe" Link to comment Share on other sites More sharing options...
overkill Posted March 30, 2015 Report Share Posted March 30, 2015 So, if I want to replace CFLAGS="-march=native -O2 -pipe" in make.conf, would that be subarch 16? ... [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 ... Link to comment Share on other sites More sharing options...
Funtoo Linux BDFL drobbins Posted March 31, 2015 Author Funtoo Linux BDFL Report Share Posted March 31, 2015 Yes. Link to comment Share on other sites More sharing options...
Funtoo Linux BDFL drobbins Posted March 31, 2015 Author Funtoo Linux BDFL Report Share Posted March 31, 2015 Also, per request, I just added a subarch for intel64-sandybridge. Link to comment Share on other sites More sharing options...
jlee Posted March 31, 2015 Report Share Posted March 31, 2015 This is a cool feature. 'avx2' needs to be added to intel64-haswell CPU_FLAGS_X86. http://en.wikipedia.org/wiki/Haswell_%28microarchitecture%29 And I see that with your last update, the core-avx-i and intel64-ivybridge profiles are now the same--as they should be--but it may be a point of confusion. Indeed, it took some scrutiny for me to figure out which of the two to use. Link to comment Share on other sites More sharing options...
Funtoo Linux BDFL drobbins Posted April 4, 2015 Author Funtoo Linux BDFL Report Share Posted April 4, 2015 Yes. there were a number of subarches moved over that don't use the official "intel64-" naming scheme. You should use the "intel64-" ones if possible. Link to comment Share on other sites More sharing options...
moonfrog Posted April 5, 2015 Report Share Posted April 5, 2015 I just put a "stage3-athlon-xp-funtoo-current" on an AMD64I didn't see a "native_32" subarch profile so I set none.I noticed that make.conf was empty and filled it in. CFLAGS="-march=native -O2 -pipe" CXXFLAGS="${CFLAGS}" ACCEPT_KEYWORDS="~x86" MAKEOPTS="-j5" VIDEO_CARDS="radeon" INPUT_DEVICES="synaptics evdev" ACCEPT_LICENSE="*" USE="X gtk -ipv6 -gnome -kde -qt -qt3 -qt3support -qt4 -qt5 -systemd" PORTDIR="/usr/portage" DISTDIR="${PORTDIR}/distfiles" PKGDIR="${PORTDIR}/packages" But it should be more liks this..or even less? CFLAGS="-march=native -O2 -pipe" MAKEOPTS="-j5" VIDEO_CARDS="radeon" INPUT_DEVICES="synaptics evdev" ACCEPT_LICENSE="*" USE="X gtk -ipv6 -gnome -kde -qt -qt3 -qt3support -qt4 -qt5 -systemd" btw My first post here I want to say hey to allI moved over here ~ a year ago when I figured out it was drobbin's projectIt's a great OS and I thank the people that help build it. Link to comment Share on other sites More sharing options...
Chris Kurlinski Posted April 5, 2015 Report Share Posted April 5, 2015 I like the new profile setup. Rebuilding my system on another drive right now in a chroot. Greatly simplified the use flag mess I had going, between package.use and make.conf. Needed some basic changes in /etc/portage/package.accept_keywords for zfs kernel builtins and zfs package, but that's it. Plus portage seems way more responsive, way faster. Good job everyone, keep up the good work. BTW, I love the no-systemd mix-in ....... Link to comment Share on other sites More sharing options...
moonfrog Posted April 5, 2015 Report Share Posted April 5, 2015 I didn't see a "native_32" subarch profile so I set none. Found and set. Probably overlooked it but maybe it's new. Link to comment Share on other sites More sharing options...
ainsley31415926 Posted April 9, 2015 Report Share Posted April 9, 2015 Looks good. But for Intel cpu's I only see [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 Is [12] the same as 'native'? What would I set for E3-1271 v3 ? Link to comment Share on other sites More sharing options...
overkill Posted April 10, 2015 Report Share Posted April 10, 2015 No. 12 is march=generic. If you want native, choose native-64. If you are really curious, you can view the settings of each subarch by reading the file contents for a particular subarch. They reside in /usr/portage/profile/funtoo/1.0/linux-gnu/arch/<preferred arch>/subarch/<preferred subarch>/make.defaults Link to comment Share on other sites More sharing options...
ainsley31415926 Posted April 10, 2015 Report Share Posted April 10, 2015 Thats my point, I cant choose native-64, I ONLY see [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64If I look in/usr/portage/profile/funtoo/1.0/linux-gnu/arch/<preferred arch>/subarch/There are a whole bunch of subarch's that I dont see when I doeselect profile listAm I missing something? Link to comment Share on other sites More sharing options...
overkill Posted April 10, 2015 Report Share Posted April 10, 2015 Have you updated your system lately? I show 20 subarchs: Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-bulldozer [4] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-jaguar [5] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k10 [6] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8 [7] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8+sse3 [8] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver [9] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-steamroller [10] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/atom_64 [11] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/btver1_64 [12] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core2_64 [13] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core-avx-i [14] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 [15] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64 [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell [17] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-ivybridge [18] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-sandybridge [19] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 [20] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/nocona [21] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/opteron_64 [22] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/xen-pentium4+sse3_64 So, 19 is the one I would choose on my system. Link to comment Share on other sites More sharing options...
ainsley31415926 Posted April 10, 2015 Report Share Posted April 10, 2015 I have 10 servers all completely up to date, most installed in the last few days. They are slightly different from each other in their configuration and booting. They are all up to date, and they all give: Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit [2] funtoo/1.0/linux-gnu/arch/pure64 *Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-bulldozer-pure64 [4] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-jaguar-pure64 [5] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k10-pure64 [6] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k8-pure64 [7] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-piledriver-pure64 [8] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-steamroller-pure64 [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64Currently available build profiles: [13] funtoo/1.0/linux-gnu/build/stable [14] funtoo/1.0/linux-gnu/build/current * [15] funtoo/1.0/linux-gnu/build/experimentalCurrently available flavor profiles: [16] funtoo/1.0/linux-gnu/flavor/minimal [17] funtoo/1.0/linux-gnu/flavor/core * [18] funtoo/1.0/linux-gnu/flavor/desktop [19] funtoo/1.0/linux-gnu/flavor/workstation [20] funtoo/1.0/linux-gnu/flavor/hardenedCurrently available mix-ins profiles: [21] funtoo/1.0/linux-gnu/mix-ins/audio [22] funtoo/1.0/linux-gnu/mix-ins/cinnamon [23] funtoo/1.0/linux-gnu/mix-ins/console-extras [24] funtoo/1.0/linux-gnu/mix-ins/dvd [25] funtoo/1.0/linux-gnu/mix-ins/gnome [26] funtoo/1.0/linux-gnu/mix-ins/kde [27] funtoo/1.0/linux-gnu/mix-ins/mate [28] funtoo/1.0/linux-gnu/mix-ins/media (auto) [29] funtoo/1.0/linux-gnu/mix-ins/media-pro * [30] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer (auto) [31] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro * (auto) [32] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base (auto) [33] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer (auto) [34] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro * (auto) [35] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common (auto) [36] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [37] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common (auto) [38] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [39] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common (auto) [40] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [41] funtoo/1.0/linux-gnu/mix-ins/lxde [42] funtoo/1.0/linux-gnu/mix-ins/lxqt [43] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [44] funtoo/1.0/linux-gnu/mix-ins/no-systemd * [45] funtoo/1.0/linux-gnu/mix-ins/print [46] funtoo/1.0/linux-gnu/mix-ins/python3-only [47] funtoo/1.0/linux-gnu/mix-ins/X [48] funtoo/1.0/linux-gnu/mix-ins/xfce [49] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [50] funtoo/1.0/linux-gnu/mix-ins/hardened yet ls -la /usr/portage/profiles/funtoo/1.0/linux-gnu/arch/pure64/subarch/ gives total 92drwxr-xr-x 22 root root 4096 Apr 6 22:00 .drwxr-xr-x 6 root root 4096 Apr 6 22:00 ..-rw-r--r-- 1 root root 121 Apr 6 22:00 README.txtdrwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-bulldozer-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-jaguar-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k10-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k8+sse3-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-k8-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-piledriver-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 amd64-steamroller-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 atom_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 btver1_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 core-avx-i-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 core2_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 corei7-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 generic_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-haswell-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-ivybridge-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 intel64-sandybridge-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 native_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 nocona-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 opteron_64-pure64drwxr-xr-x 2 root root 4096 Apr 6 22:00 xen-pentium4+sse3_64-pure64 What am I doing wrong? Link to comment Share on other sites More sharing options...
ainsley31415926 Posted April 10, 2015 Report Share Posted April 10, 2015 I see the missing subarch profiles in /usr/portage/profiles/profiles.eselect.desc Link to comment Share on other sites More sharing options...
overkill Posted April 10, 2015 Report Share Posted April 10, 2015 I think you found a bug. If I change my arch from x64_86 to pure64, then I only show 10 subarchs available, just like you noted. # eselect profile replace 1 2 # eselect profile list Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit [2] funtoo/1.0/linux-gnu/arch/pure64 * Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-bulldozer-pure64 [4] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-jaguar-pure64 [5] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k10-pure64 [6] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k8-pure64 [7] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-piledriver-pure64 [8] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-steamroller-pure64 [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 Currently available build profiles: [13] funtoo/1.0/linux-gnu/build/stable [14] funtoo/1.0/linux-gnu/build/current * [15] funtoo/1.0/linux-gnu/build/experimental Currently available flavor profiles: [16] funtoo/1.0/linux-gnu/flavor/minimal [17] funtoo/1.0/linux-gnu/flavor/core [18] funtoo/1.0/linux-gnu/flavor/desktop * [19] funtoo/1.0/linux-gnu/flavor/workstation [20] funtoo/1.0/linux-gnu/flavor/hardened Currently available mix-ins profiles: [21] funtoo/1.0/linux-gnu/mix-ins/audio [22] funtoo/1.0/linux-gnu/mix-ins/cinnamon [23] funtoo/1.0/linux-gnu/mix-ins/console-extras [24] funtoo/1.0/linux-gnu/mix-ins/dvd [25] funtoo/1.0/linux-gnu/mix-ins/gnome * [26] funtoo/1.0/linux-gnu/mix-ins/kde [27] funtoo/1.0/linux-gnu/mix-ins/mate [28] funtoo/1.0/linux-gnu/mix-ins/media [29] funtoo/1.0/linux-gnu/mix-ins/media-pro [30] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer [31] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro [32] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base [33] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer [34] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro [35] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common [36] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [37] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common [38] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [39] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common [40] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [41] funtoo/1.0/linux-gnu/mix-ins/lxde [42] funtoo/1.0/linux-gnu/mix-ins/lxqt [43] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [44] funtoo/1.0/linux-gnu/mix-ins/no-systemd [45] funtoo/1.0/linux-gnu/mix-ins/print (auto) [46] funtoo/1.0/linux-gnu/mix-ins/python3-only [47] funtoo/1.0/linux-gnu/mix-ins/X [48] funtoo/1.0/linux-gnu/mix-ins/xfce [49] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [50] funtoo/1.0/linux-gnu/mix-ins/hardened If I change it back, then all the subarchs reappear: # eselect profile replace 2 1 # eselect profile list Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit * [2] funtoo/1.0/linux-gnu/arch/pure64 Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-bulldozer [4] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-jaguar [5] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k10 [6] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8 [7] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8+sse3 [8] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver [9] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-steamroller [10] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/atom_64 [11] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/btver1_64 [12] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core2_64 [13] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core-avx-i [14] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 [15] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64 [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell [17] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-ivybridge [18] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-sandybridge [19] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 [20] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/nocona [21] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/opteron_64 [22] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/xen-pentium4+sse3_64 Currently available build profiles: [23] funtoo/1.0/linux-gnu/build/stable [24] funtoo/1.0/linux-gnu/build/current * [25] funtoo/1.0/linux-gnu/build/experimental Currently available flavor profiles: [26] funtoo/1.0/linux-gnu/flavor/minimal [27] funtoo/1.0/linux-gnu/flavor/core [28] funtoo/1.0/linux-gnu/flavor/desktop * [29] funtoo/1.0/linux-gnu/flavor/workstation [30] funtoo/1.0/linux-gnu/flavor/hardened Currently available mix-ins profiles: [31] funtoo/1.0/linux-gnu/mix-ins/audio [32] funtoo/1.0/linux-gnu/mix-ins/cinnamon [33] funtoo/1.0/linux-gnu/mix-ins/console-extras [34] funtoo/1.0/linux-gnu/mix-ins/dvd [35] funtoo/1.0/linux-gnu/mix-ins/gnome * [36] funtoo/1.0/linux-gnu/mix-ins/kde [37] funtoo/1.0/linux-gnu/mix-ins/mate [38] funtoo/1.0/linux-gnu/mix-ins/media [39] funtoo/1.0/linux-gnu/mix-ins/media-pro [40] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer [41] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro [42] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base [43] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer [44] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro [45] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common [46] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [47] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common [48] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [49] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common [50] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [51] funtoo/1.0/linux-gnu/mix-ins/lxde [52] funtoo/1.0/linux-gnu/mix-ins/lxqt [53] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [54] funtoo/1.0/linux-gnu/mix-ins/no-systemd [55] funtoo/1.0/linux-gnu/mix-ins/print (auto) [56] funtoo/1.0/linux-gnu/mix-ins/python3-only [57] funtoo/1.0/linux-gnu/mix-ins/X [58] funtoo/1.0/linux-gnu/mix-ins/xfce [59] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [60] funtoo/1.0/linux-gnu/mix-ins/hardened Link to comment Share on other sites More sharing options...
overkill Posted April 10, 2015 Report Share Posted April 10, 2015 I believe Daniel is still perfecting the eselect profile feature. Link to comment Share on other sites More sharing options...
Funtoo Linux BDFL drobbins Posted April 11, 2015 Author Funtoo Linux BDFL Report Share Posted April 11, 2015 The profiles themselves are working well, although eselect profile does have some bugs. I'm in the process of rewriting eselect profile to replace it with a new tool. Beta should be available within a week. More info near the bottom of the latest news item: http://www.funtoo.org/News:How_We%27re_Keeping_You_At_the_Center_of_the_Funtoo_Universe Link to comment Share on other sites More sharing options...
ainsley31415926 Posted April 11, 2015 Report Share Posted April 11, 2015 I am not sure if this really worked or is even wise, but I did it anyhow. I changed to the x86-64bit arch Then added subarch intel64-haswell Then changed back to the pure64 arch Now eselect profile showlooks like this: arch: gentoo:funtoo/1.0/linux-gnu/arch/pure64 build: gentoo:funtoo/1.0/linux-gnu/build/current flavor: gentoo:funtoo/1.0/linux-gnu/flavor/core subarch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/no-systemd But of course intel64-haswell does not show under eselect profile list Link to comment Share on other sites More sharing options...
Funtoo Linux BDFL drobbins Posted April 11, 2015 Author Funtoo Linux BDFL Report Share Posted April 11, 2015 Guys, you are not really supposed to change the arch. That is set when the stage3 is built. Quit doing that, and eselect may work fine for you :) 666threesixes666 1 Link to comment Share on other sites More sharing options...
Recommended Posts