On Thu, 21 Aug 2003 09:41:29 -0500 Shawn <[EMAIL PROTECTED]> wrote: > Look, you DON'T want to play with NPTL if you are still struggling to > meet dependencies. > > The ebuild gave you enough info for you to go off on your own and > satisfy what it was asking for by manually unmasking some stuff, > slotting it appropriately if it isn't already, etc etc etc. > > To play with glibc, you MUST be proficient in all-of-the-above, > including portage, compilers, the kernel, patching (you must patch > your 2.6 kernel), etc etc. You've demonstrated that you are not. > > Start smaller. > > On Thu, 2003-08-21 at 03:39, Loic Domaigne wrote:
> > > > I tried this yesterday already. I get the following error message: > > > > | !!! all ebuilds that could satisfy ">=sys-devel/gcc-3.3-r1" > > | have been masked > > | > > | !!! (dependency required by "sys-libs/glibc-2.3.2-r3" [ebuild]) > > > > If I understood correctly, I need to install gcc-3.3-r1 first? > > (this is indeed required by nptl v0.55). Is it correct? > > > > My understanding was that emerge would take care about > > all dependencies, download eventually the new version required and > > compile it... But, it seems that I'm wrong... > > Quick answer. If you emerge <generic-package-name>, portage finds the appropriate version and all dependancies. If you emerge <specific- package-name>, you are responsible for finding any dependancies that can't be met automatically and resolving them yourself. If looks like the package you are trying to emerge has a dependancy that is still masked, so you need to unmask and emerge that dependancy first. As the other poster said, do you really want to do this? You are getting into an area of experimentation where even some experts may not choose to tread. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
