vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello All, I've reinstalled gentoo and figured out that the installation steps from stage1 changed a little bit (for example, with 2006.1 I had to recompile perl before doing bootstrap, because of some missing dependencies). Later, even reusing my old /etc/make.conf file, I've noticed that glibc wasn't using nptl and nptlonly flags... .... I didn't care too much, because needed my computer back as soon as possible, thought to set that later and recompile eventually with "emerge world -DN". By the way later I noticed that each time I start gnome-terminal or firefox, several instances of the application are fired at once, and even skype starts 5 instances of itself. Googling a little bit, it seemed to me that multithreading applications (especially the ones using some Qt libriaries, have this behaviour)... therefore I thought to say goodbye to old linuxthreads and move to NPTL which were doing greately their job previously. But! I'm still unable to figure out why flags are still not used!!! ### /etc/make.conf ### [...] USE="nptl nptlonly" [...] ### /etc/portage/packages.use ### [...] sys-libs/glibc nptl nptlonly userlocales [...] but still I have [ebuild R ] sys-libs/glibc-2.5 USE="nls -build -glibc-compat20 - glibc-omitfp -hardened (-multilib) (-nptl) (-nptlonly) -profile (- selinux)" 0 kB I tried to find documentation regarding parentheses usage in portage and emerge, but still did not find anything useful to explain such behavior. Can someone enlight me? Thanks, guys! |
| |||
| On Feb 15, 11:04 pm, "askar.bektas...@gmail.com" <askar.bektas...@gmail.com> wrote: > Hello All, > > I've reinstalled gentoo and figured out that the installation steps > from stage1 changed a little bit (for example, with 2006.1 I had to > recompile perl before doing bootstrap, because of some missing > dependencies). Later, even reusing my old /etc/make.conf file, I've > noticed that glibc wasn't using nptl and nptlonly flags... > > ... I didn't care too much, because needed my computer back as soon as > possible, thought to set that later and recompile eventually with > "emerge world -DN". > > By the way later I noticed that each time I start gnome-terminal or > firefox, several instances of the application are fired at once, and > even skype starts 5 instances of itself. Googling a little bit, it > seemed to me that multithreading applications (especially the ones > using some Qt libriaries, have this behaviour)... therefore I thought > to say goodbye to old linuxthreads and move to NPTL which were doing > greately their job previously. > > But! I'm still unable to figure out why flags are still not used!!! > > ### /etc/make.conf ### > [...] > USE="nptl nptlonly" > [...] > ### /etc/portage/packages.use ### > [...] > sys-libs/glibc nptl nptlonly userlocales > [...] > > but still I have > > [ebuild R ] sys-libs/glibc-2.5 USE="nls -build -glibc-compat20 - > glibc-omitfp -hardened (-multilib) (-nptl) (-nptlonly) -profile (- > selinux)" 0 kB > > I tried to find documentation regarding parentheses usage in portage > and emerge, but still did not find anything useful to explain such > behavior. Can someone enlight me? > > Thanks, guys! I found the issue. When untarred stage1 I didn't check where /etc/ make.profile was pointing. And indeed it was pointing towards /usr/ portage/profiles/default-linux/x86/no-nptl... Changed the link, now I'm able to fix the issue by recompiling the world with --newuse --deep. Ah I found the explanation regarding parentheses here http://gentoo-wiki.com/HOWTO_Use_Portage_Correctly Cheers |
| |||
| askar.bektassov@gmail.com wrote: > By the way later I noticed that each time I start gnome-terminal or > firefox, several instances of the application are fired at once, and > even skype starts 5 instances of itself. Googling a little bit, it > seemed to me that multithreading applications (especially the ones > using some Qt libriaries, have this behaviour)... therefore I thought > to say goodbye to old linuxthreads and move to NPTL which were doing > greately their job previously. > But! I'm still unable to figure out why flags are still not used!!! > ### /etc/make.conf ### > [...] > USE="nptl nptlonly" > [...] > ### /etc/portage/packages.use ### > [...] > sys-libs/glibc nptl nptlonly userlocales > [...] > [ebuild R ] sys-libs/glibc-2.5 USE="nls -build -glibc-compat20 - > glibc-omitfp -hardened (-multilib) (-nptl) (-nptlonly) -profile (- > selinux)" 0 kB check your /etc/make.profile symlink, so it's not pointing at .../usr/portage/profiles/default-linux/x86/no-nptl -- //Aho |