j-g-

If you don't want to be building 32bit binaries for every library you should have taken the route of package.use, but this sort of stuff can be deal with later, when it's bugging you, and you have read a bit more about portage, the key for making portage more friendly to use, is to know about it's concepts, package atoms, package.use, package.mask, etc, take your time to understand these stuff.

No make.conf changes, I explained to you about this message from portage in your previous topic, also check that suggested manpage. get used to that kind of output, if you read it carefully as recommended, you'll find the instructions there. Also this is important as you are building a desktop: http://www.funtoo.org/News:ABI_X86_64_and_32(This type of info, used to be in news that came with the portage tree, but in funtoo, IMO, the bad decision of removing these from the tree, and put them in the webpage was made. in gentoo emerge notifies you there are important news to know about, like this one)

Most surely, try commenting/remmoving that line from that file.

Didn't the error message told you about a larger log file? like /var/log/Xorg.$DISPLAY.log, there's not really much info in the error you posted. seems like the driver wasn't handled properly because of the screen line, but not much info anyway.

Did you check the required modules are being added to the initramfs ? you do have the modules but you need them before mounting /. you can also try making your own kernel build with the modules built-in. I do not use genkernel so I cant help you on fixing your initramfs, but the documentation should be enough, I guess.

I would think is correct, if you check the list a lot of stuff will be virtuals, and packages that use scripting languages(python,perl,ruby, etc... no compiling), and as compiling your packages from sources requires build-time and run-time dependencies, you'll have to install more packages compared to a binary distro.

+1 Especially when portage has stuff to do brute force, like emerge --empty-tree. the concepts of @world and @system, are one of the things that make portage such a powerful package manager in my opinion. OP: This is just a guess but, until you add some fans to your hardware, you could try running with MAEKOPTS=-j2 or 3 as max, but as I said this is just a guess not really based on technical knowledge about microprocessors temperature. Also you should check the manpage portage(5) about configurations in /etc/portage, I think a good start might be package.use package.mask and package.accept_keywords .

Change your VIDEO_CARDS for: VIEO_CARDS="vga noveau" The thing is when you try to emerge the drivers for your video card, you are installing a binary package with 32bit binaries, so you need the libraries on which this depends, but as most things in Funtoo you have to compile the 32 bit libraries required, in order to use the drivers, so as suggested above get working the noveau drivers and then deal with the nvidia proprietary if you want. About the shutdown, you aren't being specific, It was a proper shut down or more like a power outage, kernel panic? There's no reason why compiling would shutdown your pc, exept heat, compiling is intense, so make sure your pc is at a proper temperature.

If you are going to use BTRFS don't use LVM, what is the point?, why add so much overhead to your file system?

Some of these questions should have been answered by the installation process(ego? epro? the boot configuration?), in gentoo's terms is ~arch with a different profile system, some overlays merged with the portage tree, also OpenRC is not the same as gentoo, the git sync system was another difference but gentoo has now sync of the portage tree via git also, and it seems the full move to git(from cvs) will happen next month. Check the wiki there's a list of the forked packages from gentoo, if you want to get the details check the funtoo-overlay and the script used to merge the gentoo tree and the overlays.

Did you re-run the ebuild command 2 times from inside /var/tmp/portage/... the directories created get remove everytime you try to do a new build either using emerge or ebuild ... clean, I have had similar errors when I forgot to cd out of the autogenerated directories. Now that you have identified that the failure is in speex, report a bug so the dependecy get's added to the ebuild so this error doesn't happen to other people. Since you emerged it with one-shot you shouldn't have any problems once it gets fixed. you can try from your home dir, to check the errors are because of what I tell you before. $ sudo emerge --oneshot pulseaudio

The build failed at configure phase would there be any more logs? OP: You can try to manually check if the configure phase is completing, and if not get the important log with this: (try to run the build up to the configure phase using the portage user) # sudo -u portage ebuild $(equery w pulseaudio) clean configure if that fails with a similar error as the first you posted go into the build dir, I recommend as the portage user. $ sudo -u portage bash $ cd /var/tmp/portage/media-sound/pulseaudio/work/pulseaudio-${the version you are installing}/ and run : $ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --with-database=gdbm --enable-bluez5 --disable-bluez4 --disable-bluez5-native-headset --disable-bluez5-ofono-headset --localstatedir=/var --with-udev-rules-dir=//lib/udev/rules.d --disable-coreaudio-output --disable-esound --disable-solaris --disable-waveout --enable-largefile --enable-x11 --disable-adrian-aec --enable-asyncns --enable-glib2 --disable-oss-output --disable-oss-wrapper --enable-alsa --enable-dbus --disable-gcov --enable-gconf --enable-gtk3 --disable-jack --enable-ipv6 --disable-samplerate --disable-lirc --disable-neon-opt --enable-orc --enable-openssl --disable-systemd-daemon --disable-systemd-journal --disable-systemd-login --enable-tcpwrap --disable-default-build-tests --enable-udev --enable-hal-compat --enable-webrtc-aec --disable-xen --disable-avahi --with-caps --without-fftw --with-speex (This is the line portage ran for you before) The fail log of this should be what contains the info that matters if configure is what is failing.

Sure is doable and is really easy, as installing any other kernel sources, just try putting the ebuild in your local overlay. or adding the funtoo overlay with a lower priority than ::gentoo on repos.conf, and emerging the sources, is not like a kernel has any runtime dependencies right? it is the runtime dependency to start a user space. I have never used debian-sources but I looked at the ebuild and I saw nothing there that could make it not work on gentoo, but I don't feel like trying I don't like debian-sources.

If you plan to start fiddling with a custom kernel I recomend you a conscious read of the help of the Makefiles of the kernel $ cd /usr/src/linux $ make help I'm not trying to say you can't read helps, but the kernel help is a fairly large one, and one should take some time to read all those options. On the topic of getting the driver, you should know what filesystem you will use and enable those, but a way that can get you on a .config that doesn't need you to go disabling and enabling every single thing, would be: boot with the standard kernel # make defconfig or olddefconfig using /proc/config.gz (You read about thouse) then # make localmodconfig -- to disable the modules not loaded this may disable some that also might be needed or have changed name in newer versions # make menuconfig -- to select filesystem, security, cpu and further fine-tuning. ( Using '/' is a quick way to navigate trough the kernel you can put kernel module names or CONFIG names, and '?' will give plenty of info) If you want to reuse your newly custom config for specific hardware and quickly try it on a new version One way of doing it is to make a backup of the .config everytime you upgrade or modify your kernel, and then place it in a kernel source dir to upgrade it to the newer version using make olddefconfig make && make install ... Another good practice is to start building as user your kernel, and only installing it as root.

I give you unity is the worst thing has ever happened to a desktop, I haven't tried the other ubuntu flavors recently but I'd say Xubuntu is still a nice not-so-bloated noob-friendly distro, I should have added the 'X' , thou my personal recomendation for noobs has been Linux Mint, as I say "Ubuntu without the crap" I have had good experiences recommending it to very non-technical people and now they do their own installs and have learned to upgrade their system, and aren't constantly asking for my help, in fact almost never, The good thing about Mint is It comes with the right tools for the everyday pc user, a web browser(firefox), libreoffice for documents, and a media player(the always good vlc), and Cinnamon is very pleasing to the eye, so most people just install it and don't need to search anymore for software (e.g. Don't go to suspicious guides telling them to add unoffical packages and install .debs by hand, that will break their upgrades later). Debian via debootstrap and Arch are for when you have covered the basics of course!

So you are running in a chroot, I have never tried to start X as root in a chroot, I didn't know you could get to display something my guess is /dev/ is not being handled properly by the chroot , stop that, boot your real installation and stop using startx as root, or get a display manager you would be better using one of those. Install a bootlader if you haven't already, and boot the real thing, theres a kernel already installed at this point I'm not sure if your 4.0.5 kernel is built or you have only installed the sources. and don't try building a personalized kernel until you know all the drivers and cpu options required for your computer, take your time(not ours) to figure out those things. Also are you sure you want twm? Again read the documentation you are not following a proper installation procedure, and no one wants to post a personalized version of what's in the wiki. See above this person is trying to start X in a chroot, ignoring documentation and advice. OP deleted their replies but this one was quoted in one of mine's. Why are you deleting everything you posted? makig this topic further obscure and really pushing away anyone that still might want to help you. Follow instructions properly and DO NOT install a graphical system until you have booted your new installation!!! If you can't get what this means you still have lots to learn about basics. +1 for this, but Fedora has times when more than noob-level knowledge is required, I would recomend First Ubuntu or Mint, to learn the basics of shell and package management Install Debian using debootstrap or Arch, that should give you knowledge about putting together parts from a base system to a server or desktop. Then come again to Funtoo or Gentoo, and you can tune your system as you want and your imagination is the limit(And maybe package.mask some times )

I'm glad to read that, with few hours of sleep I was able to put this together, and it seems to work:https://github.com/j-g-/funtoo-systemd.git Test was -> unpack funtoo's stage3 # cd ${FUNTOO_CONTAINER_DIR} && systemd-nspawn -> add overlay according to instructions on github -> sync main tree and overlay # eselect profile set-flavor <a systemd flavor> # emerge -avuDN @world # ^D (logout) # systemd-nspwan -b -> Systemd Funtoo Container Working! Here's a paste of the outuput of the container If time and laziness don't get me tonight, I might look into modifying ego to read overlay profiles not just the ones from the main tree. Feedback is appreciated! BTW, I have included my ebuild of cockpit[1] in the systemd-server flavor, inspired by Fedora Server. What do you think about creating a google group "Systemd Funtooers" or something like that and continue the dicussion there? [1] http://cockpit-project.org/

For the ones interested in running systemd on Funtoo, I had a working configuration with systemd and was in the process of creating profile stuff for it, but the maintaince burden would take too much time I don't have, but I might try again when I have more time, or if there's more people that want to run systemd on top of what funtoo provides and are willing to contribute fixing stuff we could put something together and use github or gitlab as a meeting point for discussion. I wouldn't try to make it official, neither discuss development or fixes in any funtoo channel, just a overlay that makes easy to install and provides profiles for systemd in the funtoo style, that way unnecessary flames are avoided.

So you are running in a chroot, I have never tried to start X as root in a chroot, I didn't know you could get to display something my guess is /dev/ is not being handled properly by the chroot , stop that, boot your real installation and stop using startx as root, or get a display manager you would be better using one of those. Install a bootlader if you haven't already, and boot the real thing, theres a kernel already installed at this point I'm not sure if your 4.0.5 kernel is built or you have only installed the sources. and don't try building a personalized kernel until you know all the drivers and cpu options required for your computer, take your time(not ours) to figure out those things. Also are you sure you want twm? Again read the documentation you are not following a proper installation procedure, and no one wants to post a personalized version of what's in the wiki.

Your problem is you don't want to read documentation, you just want the 'magic commands' given to you, some in this thread have tried to help you, but you either ignore or don't give the information requested appropriately, You make it possible by not reading documentation, and clearly having little idea of what you are doing. This kind of un-polite request won't get you any much help. Not following advice and the issuing random commands as root wont get you anywere, there's no point in executing synclient if you are not inside an X session, you haven't even posted your .xinitrc or what desktop enviroment or window manager you are trying to start, and you seem to be doing everything as root, why are you installing X if you haven't even created a user, if you follow the install guide you should have your own user before even be thinking of a graphical environment. Also that uname and the snippet of kernel configuration you posted makes me think you might be running this from a chroot, are you? Read the documentation before asking, and make good questions, not just ' under startx, after a new install ', without giving information about your system and logs, 'under startx' doesn't even makes sense. If you want help one shouldn't be doing heuristics to figure out what's really happening on your system. The amount of threads asking for help you have posted to this forum just for getting your first install done, tells you don't have the knowledge of a linux system, required to maintain a source based distro, you should try learn first using a vm or spare hardware(for a source based distro at least have 2 cores and 2GB of ram with swap), take your time to learn about the linux base system, and then you can run funtoo or gentoo as a server or workstation, if you don't have the experience to quickly trouble-shoot simple problems like the ones you have posted any source-based distro will just be maintainace pain for you, the packages in gentoo and funtoo are very vanilla, and many packages require configuration to work properly after install( that's not saying they won't work). I've read in this forums funtoo can be a distro for noobs, but I strongly disagree, just learning basic shell, file system concepts and hierarchy might take a day for some people, and that desn't cover 'basic unix', so if you are a noob unless you have a week and lot's of time to read, you wont be able to make a proper installation of gentoo or funtoo, you might get something working by just coping commands from the install guide but that will soon become a nightmare to maintain.

Last time I tried I had to use my own overlay to get some of the packages from the gentoo tree, and some unmasking as you said, It can be done is not that complicated, but definitely requieres you to be familiar with portage before being able to do it.

try "emerge chromium" or libreoffice that will give you an idea about how much ram/cpu you might need just for compilation. You are already having trouble with this, and don't seem to get it, make the connection between your previous topic and this one. I bet anyone with some months using gentoo/funtoo knew RAM was the issue when one webkit was in the topic.

I'm guessing you have MAKEOPTS="-j9" also, I'd say your ram is being the bottleneck, does it fail with an out of memory message? , these packages take a lot of ram when compiling, and that many jobs wouldn't fit in your ram, I even log out of gnome when upgrading webkit, and I only run with -j4, I also have 4GB RAM. You might want to get more RAM, or you could make those packages run with less jobs at the cost of more compile time, using package.env you would need to do something like: # echo MAKEOPTS="-j3" > /etc/portage/env/limitjobs # echo net-libs/webkit-gtk limitjobs >> /etc/portage/package.env XFS is mature in the kernel, but does it fit what you need? , I'm running with BTRFS right now and it has handled well a few unexpected power downs, but I'm prepared to have trouble with it, are you prepared to deal with unexpected FS issues? if not, go with the already very much tested ext4. About what kernel, if vanilla, debian or gentoo-ources(which is mainly some configuration patches) have what you need use one of those, or even better have two of them around, In case you have problems with newer ones, you can go back to a previous version, and even another patch-set, nothing stops you from having many kernels compiled, you just have to choose one as default.

That stopped being a Funtoo only feature some months ago. https://github.com/gentoo/gentoo-portage-rsync-mirror Now It's optional This isn't actually a feature, because Gentoo still uses Openrc as default init system, Funtoo just has it masked(You can't install it easily ), and doesn't have official profiles for it. It can actually be unmasked and installed, I did it. That said, the feature I most like that is exclusive to Funtoo are the profile mixins.

Since you say you are new to portage, I will warn you. You might be creating a recipe for upgrade problems, if you just simply 'emerge cat/pkg' the dependencies missing, whenever you encounter this problem again and want to install missing dependencies for a package, use: # emerge --oneshot 'cat/pkg' The short why, is you don't want dependencies of packages in your @world, you want the dependecies resolved by portage, more info `man 1 emerge`. Also you should have opened a report on this on the bugtracker, so the missing dependency gets added to the ebuild. . So before you get into strange problems with portage do: emerge --deselect $DEPENDECIES_YOU_INSTALLED this wont uninstall them just take them out of your /var/lib/portage/world file.