Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Unable to compile xf86-video-virtualbox-4.3.24 or -4.3.26
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 482
Location: "Hemp"shire, UK

PostPosted: Thu Mar 19, 2015 9:15 pm    Post subject: Unable to compile xf86-video-virtualbox-4.3.24 or -4.3.26 Reply with quote

Does anyone knows why I'm getting this compile error with xf86-video-virtualbox 4.3.24 and 4.3.26? This error is the same for both! Running kernel 3.19.0 here.

Code:

  CXX RuntimeGuestR0 - common/checksum/alt-md5.cpp
g++ -c -O2 -nostdinc -iwithprefix include -include /lib/modules/3.19.0-gentoo/build/include/linux/kconfig.h -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wno-sign-compare -fdiagnostics-show-option -fno-stack-protector -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fno-common -include /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/VBox/VBoxGuestMangling.h -m64 -mno-red-zone -mcmodel=kernel -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-reorder-blocks -fno-asynchronous-unwind-tables -funit-at-a-time -Wno-sign-compare -fno-exceptions -fno-rtti -include /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/VBox/VBoxGuestMangling.h -Ir0drv/linux -I/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime -Iinclude -I/lib/modules/3.19.0-gentoo/build/include -I/lib/modules/3.19.0-gentoo/build/include/asm-i386/mach-default -I/lib/modules/3.19.0-gentoo/build/include/asm-x86/mach-default -I/lib/modules/3.19.0-gentoo/build/include/drm -I/lib/modules/3.19.0-gentoo/build/arch/x86/include -I/lib/modules/3.19.0-gentoo/build/arch/x86/include/asm/mach-default -I/lib/modules/3.19.0-gentoo/build/arch/x86/include/uapi -I/lib/modules/3.19.0-gentoo/build/arch/x86/include/generated -I/lib/modules/3.19.0-gentoo/build/arch/x86/include/generated/uapi -I/lib/modules/3.19.0-gentoo/build/include/uapi -I/lib/modules/3.19.0-gentoo/build/include/generated/uapi -I/lib/modules/3.19.0-gentoo/build/include -I/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/dtrace -I/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include -I/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/opt/VirtualBox\" -DRTPATH_APP_PRIVATE_ARCH=\"/opt/VirtualBox\" -DRTPATH_SHARED_LIBS=\"/opt/VirtualBox\" -DRTPATH_APP_DOCS=\"/opt/VirtualBox\" -DIN_RING0 -DIN_RT_R0 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -D__KERNEL__ -DMODULE -DIN_GUEST -DIN_GUEST_R0 -DIN_RT_R0 -DRT_WITH_VBOX -DRT_WITHOUT_NOCRT_WRAPPERS -DRT_NO_EXPORT_SYMBOL -DRT_NO_EXPORT_SYMBOL -DMODULE -DKBUILD_MODNAME=KBUILD_STR\(vboxdrv\) -DKBUILD_BASENAME=KBUILD_STR\(vboxdrv\) -DIN_SUP_R0 -Wp,-MD,/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/checksum/alt-md5.o.dep -Wp,-MT,/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/checksum/alt-md5.o -Wp,-MP -o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/checksum/alt-md5.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime/common/checksum/alt-md5.cpp
In file included from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/types.h:116:0,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/mem.h:31,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime/common/alloc/alloc.cpp:34:
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:197:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void data_access_exceeds_word_size(void)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:201:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __read_once_size(volatile void *p, void *res, int size)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:218:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __write_once_size(volatile void *p, void *res, int size)
                             ^
In file included from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/types.h:116:0,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/heap.h:30,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime/common/alloc/heapsimple.cpp:32:
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:197:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void data_access_exceeds_word_size(void)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:201:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __read_once_size(volatile void *p, void *res, int size)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:218:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __write_once_size(volatile void *p, void *res, int size)
                             ^
kmk: *** [/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/alloc/alloc.o] Error 1
kmk: *** Waiting for unfinished jobs....
In file included from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/types.h:116:0,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/md5.h:29,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime/common/checksum/alt-md5.cpp:51:
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:197:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void data_access_exceeds_word_size(void)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:201:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __read_once_size(volatile void *p, void *res, int size)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:218:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __write_once_size(volatile void *p, void *res, int size)
                             ^
In file included from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/types.h:116:0,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/include/iprt/heap.h:30,
                 from /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/src/VBox/Runtime/common/alloc/heapoffset.cpp:32:
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:197:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void data_access_exceeds_word_size(void)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:201:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __read_once_size(volatile void *p, void *res, int size)
                             ^
/lib/modules/3.19.0-gentoo/build/include/linux/compiler.h:218:29: error: can’t set ‘no_instrument_function’ attribute after definition
 static __always_inline void __write_once_size(volatile void *p, void *res, int size)
                             ^
kmk: *** [/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/alloc/heapsimple.o] Error 1
kmk: *** [/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/checksum/alt-md5.o] Error 1
kmk: *** [/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.3.24/work/VirtualBox-4.3.24/out/linux.amd64/release/obj/RuntimeGuestR0/common/alloc/heapoffset.o] Error 1
kmk: *** Exiting with status 2
 * ERROR: x11-drivers/xf86-video-virtualbox-4.3.24::gentoo failed (compile phase):

_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
thomai
n00b
n00b


Joined: 05 Jan 2015
Posts: 10

PostPosted: Fri Mar 20, 2015 10:38 am    Post subject: Reply with quote

Same here with xf86-video-virtualbox-4.3.18 and also 4.3.24 @ kernel 3.19.2

Seems like a gcc bug?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49718
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 482
Location: "Hemp"shire, UK

PostPosted: Fri Mar 20, 2015 6:28 pm    Post subject: Reply with quote

thomai wrote:
Same here with xf86-video-virtualbox-4.3.18 and also 4.3.24 @ kernel 3.19.2

Seems like a gcc bug?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49718


OK then I'll try GCC 4.8.4 see if that solves the issue. If not, GCC 4.9.2 will be next to try.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 482
Location: "Hemp"shire, UK

PostPosted: Fri Mar 20, 2015 7:13 pm    Post subject: Reply with quote

I can confirm you need GCC 4.9.2 to compile the xf86-video-virtualbox 4.3.26 driver!! WTF?
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
thomai
n00b
n00b


Joined: 05 Jan 2015
Posts: 10

PostPosted: Tue Mar 24, 2015 9:07 am    Post subject: Reply with quote

Yes, using GCC 4.9.2 solves the issue.

I also needed to unmask xf86-video-virtualbox-4.3.26 (~amd64) since 4.3.18 won't compile due to a missing symbol (dir_mmap or something).
Back to top
View user's profile Send private message
wfdawson
n00b
n00b


Joined: 05 Aug 2010
Posts: 17

PostPosted: Mon Aug 03, 2015 11:56 am    Post subject: Reply with quote

This problem is still active. I had gcc-4.8.4 and no luck building virtualbox-guest-additions-4.3.30 until I installed gcc-4.9.3.
Back to top
View user's profile Send private message
destroyedlolo
l33t
l33t


Joined: 17 Jun 2011
Posts: 712
Location: Close to Annecy (France)

PostPosted: Fri Aug 21, 2015 9:27 am    Post subject: Reply with quote

Idem for me :cry:

Is it solved with gcc 4.8.5 ?
Because moving to Gcc 5.9 seems needing large recompilation.

Thanks

Laurent
Back to top
View user's profile Send private message
engil
Tux's lil' helper
Tux's lil' helper


Joined: 22 Nov 2005
Posts: 117
Location: France

PostPosted: Wed Aug 26, 2015 8:17 am    Post subject: Reply with quote

So,

it does work after switching to GCC 4.9, for information.

Florent
_________________
Lisa Simpson : Il doit être programmé pour éliminer la concurrence !
Bart Simpson : Comme Microsoft ?!
Lisa Simpson : Exactement !
Back to top
View user's profile Send private message
dbishop
Tux's lil' helper
Tux's lil' helper


Joined: 08 Dec 2007
Posts: 99

PostPosted: Sat Aug 29, 2015 12:31 am    Post subject: Reply with quote

Same here, gcc 4.8.4 wouldn't compile x11-drivers/xf86-video-virtualbox-4.3.28, but gcc 4.9.3 worked perfectly.
Back to top
View user's profile Send private message
Madskills
n00b
n00b


Joined: 11 Sep 2015
Posts: 3

PostPosted: Fri Sep 11, 2015 2:54 pm    Post subject: Reply with quote

Same problem.

However, I'm even more confused being a newbie to gentoo, so here's a blob of questions:
1) how do I even update to newer GCC? If I run emerge --update gcc, it just tells me "Calculating dependencies... done!" even if my version is 4.8.4.
2) how come bleeding edge gentoo uses GCC 4.8-family by default when there's 5.2 available already and how come virtual box drivers package does not explicitly require more recent compiler version to work?
3) I got this error while trying to emerge x11-base/xorg-drivers, compilation failed(same error as OP) and now if I try to emerge the same packet again with --update, it tells me there's nothing to download, but how if it failed to compile to start with?? Should I rebuild it from scratch?

I really need to get used to portage, the more documentation I read, the more questions arise.
Back to top
View user's profile Send private message
dbishop
Tux's lil' helper
Tux's lil' helper


Joined: 08 Dec 2007
Posts: 99

PostPosted: Fri Sep 11, 2015 3:29 pm    Post subject: Reply with quote

lots of variations, but here's what I would do...

1. create a text file: /etc/portage/package.keywords/gcc and then put this in it (4.9.3 is current as of this writing)

Code:
=sys-devel/gcc-4.9.3


This is an easy way to do it:

Code:
mkdir -p /etc/portage/package.keywords
echo  =sys-devel/gcc-4.9.3 > /etc/portage/package.keywords/gcc


then you should be able to (this may take a while):

Code:
emerge -uDN gcc


then double-check with:

Code:
gcc-config -l


you should get something like this:

[1] x86_64-pc-linux-gnu-4.9.3 *

If you get more than one line, just make sure that the asterisk is next to the 4.9.3 version (I have tons of packages on my systems, in various combinations, and I have not had a problem with gcc-4.9.{2,3}

Note: you should already have gcc-config, but if not, do:

Code:
emerge -uDN  gcc-config


And make sure you have eix and gentoolkit too, these are very helpful to have around, then look on the gentoo wiki to see how to use them:

Code:
emerge -uDN app-portage/eix app-portage/gentoolkit


Hope this helps...

And remember: those who do not read possess no advantage over those who cannot read. But the forum does help :D
Back to top
View user's profile Send private message
dbishop
Tux's lil' helper
Tux's lil' helper


Joined: 08 Dec 2007
Posts: 99

PostPosted: Fri Sep 11, 2015 4:14 pm    Post subject: Reply with quote

as for your other two questions:

Quote:
2) how come bleeding edge gentoo uses GCC 4.8-family by default when there's 5.2 available already and how come virtual box drivers package does not explicitly require more recent compiler version to work?


Everyone asks this at some point :) Not sure exactly, but I suspect that there may be packages that cannot compile with >gcc-4.8.4 or have not been tested. Gentoo is primarily a source-based distro so if gcc works sporadically, you have real problems. You can have multiple versions, they are managed with gcc-config and you would explicitly emerge others (i.e. create the keyword entry if necessary, don't use the -u flag, and specify the exact version you want, like this:

Code:
emerge =sys-devel/gcc-4.9.3


Quote:

3) I got this error while trying to emerge x11-base/xorg-drivers, compilation failed(same error as OP) and now if I try to emerge the same packet again with --update, it tells me there's nothing to download, but how if it failed to compile to start with?? Should I rebuild it from scratch?



First, I imagine the ebuild should specify gcc >=4.9.2 -- probably qualifies as a bug, no one is perfect I suppose.

That said, (assuming you've emerged eix) run:

Code:
eix-sync


That will update your portage tree and do some other useful things. I do this every few weeks, or whenever I add a new package, an I always do an eix-sync as a first step (but never more than once a day on the eix-sync). If you get too far behind, you will tend to give yourself extra work.

Then you can run something like this. It will tell you what needs to get updated:

Code:
emerge -uDN @world -p


The -p switch will let you see what will happen. Look through the list to make sure that you're okay with what it proposes to do, then re-run the command without the -p flag.


If you have a little time on your hands, you can do this:

Code:
emerge -e @world


This will recompile everything, and can expose subtle problems, although some question the wisdom of doing this. I do it from time to time, especially when things start getting wonky (but I run lots of machines, and on my desktops I experiment a lot so sometimes I need to do this just to get things back in some general order).

After I do an update -uDN world, I will often do a revdep-rebuild -i, followed by an emerge -cp. The last command will show you what packages your system thinks you no longer need. It is generally safe, but make sure that your read through the list. Often, my system proposes to nuke my kernel source (because a new version got installed in the world update, but I haven't gotten round to building a new kernel), and if you're just starting it, nano will get removed if you're not careful. If you see such a warning (it's pretty obvious) Just add it to your world file:

Code:
emerge -n nano


As a final suggestion, I always put this in my /etc/portage/make.conf file:

Code:
EMERGE_DEFAULT_OPTS="-v --with-bdeps=y --complete-graph=y --jobs=5 --load-average=5.0"


Try that, you may find it useful. If you don't like it, just remove it. You can man emerge to see what it will do.

Again, hope this is helpful.


Last edited by dbishop on Fri Sep 11, 2015 7:51 pm; edited 1 time in total
Back to top
View user's profile Send private message
Madskills
n00b
n00b


Joined: 11 Sep 2015
Posts: 3

PostPosted: Fri Sep 11, 2015 4:48 pm    Post subject: Reply with quote

@dbishop
Definitely thank you for the reply, however a few more questions have risen:

1) I do try to read the manuals, however gentoo is vastly different from all other distros I've tried and the documentation seems far too overwhelming to a newbie. As far as I understand, your suggestion of running
Code:

mkdir -p /etc/portage/package.keywords
echo  =sys-devel/gcc-4.9.3 > /etc/portage/package.keywords/gcc

is supposed to add an accepted keyword to =sys-devel/gcc-4.9.3, but I don't see any actual keyword. According to https://wiki.gentoo.org/wiki/ACCEPT_KEYWORDS, syntax should be something like this:
Code:

mkdir -p /etc/portage/package.keywords
echo  =sys-devel/gcc-4.9.3 ~x86 > /etc/portage/package.keywords/gcc

but I have tried it and looks like portage is capable of finding gcc-4.9.3 even when there's no keywords are even assigned to it. Where am I supposed to read it? Is accepting a keyword is the recommended way of installing updated(unstable?) version of a software?

2) I have found an old archived page: http://www.gentoo-wiki.info/HOWTO_Use_Portage_Correctly that answers most of my questions regarding newbie-confusion with portage. Why is this archived? Why the new page https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage is far inferior to the old one?

3) I still don't understand what happens when I try to emerge a package, it gives an error and then I try to update this package.

PS: -v --with-bdeps=y and --complete-graph=y seem very useful. I think it may be reasonable to add such options as a general good practice advice on the portage newbie pages.
Back to top
View user's profile Send private message
dbishop
Tux's lil' helper
Tux's lil' helper


Joined: 08 Dec 2007
Posts: 99

PostPosted: Fri Sep 11, 2015 7:10 pm    Post subject: Reply with quote

The ~x86 (or ~amd64 -- the 64bit intel/amd flag) is now optional, the wiki is probably a little behind, but you can add it, there's no downside (unless it's the wrong one :wink: )

You certainly have the correct distro, Gentoo is the best -- and I have used a lot of them. The trouble is that you won't realize how much better it is until you get past the initial learning curve. So stick with it, you won't regret it. You will know Linux in and out, and that will make you healthy, wealthy, and wise :D

Regarding emerge default options, --jobs=5 will allow parallel emerges, which is also quite useful, I'd add it if I were you, regardless. It will make things go MUCH faster (unless you like reading all gcc's spew). You can always see problems in the ebuild log output. The --load-average is good to keep your machine from getting subsumed by gcc.

gentoo-wiki is old. I don't remember the bloody history of it all, but a long time ago in a galaxy far away, the data center in which gentoo-wiki resided went bankrupt and the server and its backups were absconded. It had nothing to do with Gentoo or the maintainer, it had to do with the data center owing $ to their landlord.

Are you using x86 or amd64? Please note that amd64 is for 64bit intel as well as amd...


Last edited by dbishop on Fri Sep 11, 2015 8:05 pm; edited 1 time in total
Back to top
View user's profile Send private message
ct85711
Veteran
Veteran


Joined: 27 Sep 2005
Posts: 1726

PostPosted: Fri Sep 11, 2015 7:27 pm    Post subject: Reply with quote

One of the biggest reasons why Gentoo hasn't moved onto gcc-5, is that gcc-5+ has made some significant changes that affects the entire system. Once they figure out a clean way to transition everyone over, it may get released to the unstable branch. Then we have the part that, the devs are still testing most of the packages, to try resolving most of the significant breakages. There is some packages that is known to be broken with gcc5, the big one last I saw was wine. You are of course welcome to help test gcc-5, but expect everything to work right away.

Feel free to monitor the gcc-5 testing thread, to see how other's experience with it is doing.
https://forums.gentoo.org/viewtopic-t-1024198.html
Back to top
View user's profile Send private message
Madskills
n00b
n00b


Joined: 11 Sep 2015
Posts: 3

PostPosted: Fri Sep 11, 2015 8:55 pm    Post subject: Reply with quote

@dbishop
Regarding ~x86 indeed looks like wiki is a bit behind. again. I really think it may use some restructuring. It looks like it was a well-structured handbook quite some time ago, but later a lot of fixes and additions were added here and there resulting in overall structure being lost. I think? Funtoo wiki : http://www.funtoo.org/Install looks way more structured and less confusing, at least the installation part even if funtoo install is a little easier.

I used ubuntu for like ages. Then I accidentally moved to arch only to find it was far superior in basically every aspect of my needs and then to gentoo to find out that it definitely has potential to overcome arch(for me of course) but there's so many poorly structured things in the wiki and little broken things here and there and compilation of KDE took me 3 days straight.

The most important thing in gentoo for me is that portage supports slots. If something does not support the most recent version of a library in arch, it basically gets thrown out of the window. That's definitely an interesting approach but kinda extreme and tends to break from time to time. Portage designed to be way more stable since it supports multiple versions of the same library and that's why I'm interested in it. And being able to compile only features I need for every package looks like an interesting advantage as well.

--jobs=5 sounds awesome. Only if I had more than 1 CPU for my virtual box lol. I'm only tinkering with gentoo out of curiosity for now so it won't get more than 1 CPU from me. For now.

@ct85711
Glad to know that there's a team working on it already and they're not like "wow it's out already?" lol. That's definitely the way I imagine things go at debian at least according to their ponderous package update schedule.

I'm definitely curious though how arch being a rolling release has gcc 5.2 and wine both working.

Also upd
Switching to latest gcc did allow me to compile vbox driver.
Back to top
View user's profile Send private message
dbishop
Tux's lil' helper
Tux's lil' helper


Joined: 08 Dec 2007
Posts: 99

PostPosted: Sat Sep 12, 2015 1:13 pm    Post subject: Reply with quote

Regarding the Gentoo Handbook, here's the link to the amd64 version: https://wiki.gentoo.org/wiki/Handbook:AMD64

Since you are using VirtualBox, I do have a 'generic' vm that I can make available to you via dropbox if you'd like. The window manager is Enlightenment 18, but you can add/change as you wish. It uses OpenRC, not that pointless systemd junk. (Anyone who trusts a massive monolithic init system is foolish. Might as well run Windows.)

Funtoo looks pretty nice, I've never worked with it. But I trust anything Daniel Robbins does, he is a great writer and a great Linux guy. His ability to communicate in print is exceptional, which is why you're finding his Funtoo pages so crisp and concise. Maybe I will finally try a VM with Funtoo soon...

There is also Pentoo, which you may find interesting. It is a ready-to-rock Gentoo descendant and will install whole -- but you will miss the learning experience.

As for your VM, while emerging, up the CPU count to two, and make --jobs=2. I don't think it matters how many CPUs you have anyway. Even if you leave it at 1 CPU, it won't do anything it can't do, but it will speed things up regardless, try it.

Please also note that "Ubuntu" is an African word that means "I would rather be running Gentoo" :lol:

**Update on --jobs=5 : I changed my VirtualBox VM to 1 CPU and left --jobs=5, worked perfectly. You should try it!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum