Hi , Thanks for the suggestions. In the proccess of trying to understand my possible mistake I'm wondering , which stage3 file should I use ? the i686 or the i486 ?
I'm trying to install it on an Asus EEEPC 1005ha netbook which stage should I use ? ( and I suppose i'll have to use the same with the CFLAGS .. ? ) Thanks, Benny On Tue, Nov 9, 2010 at 4:11 PM, Bill Longman <bill.long...@gmail.com> wrote: > On 11/09/2010 06:04 AM, Benyamin Dvoskin wrote: > > Hi Everyone , > > I am actually quite new to Gentoo , so give me a break if my question is > > a newbie one. > > anyway , while installing Gentoo , I got to the point where I want to > > compile the kernel , and for that I've done the following : > > > > emerge --sync > > > > it did the sync , but stated at the end that I must upgrade portage > > using "emerge portage" > > > > so I tried that , and it doesn't seem to work , but giving out the > > following output : > > / > > " > > --- Invalid atom in /etc/portage/package.keywords: > > dev-perl/Locale-gettext-1.05-r1 > > Calculating dependencies / > > !!! All ebuilds that could satisfy "dev-perl/Locale-gettext" have been > > masked. > > !!! One of the following masked packages is required to complete your > > request: > > - dev-perl/Locale-gettext-1.05-r1 (masked by: EAPI 2) > > > > The current version of portage supports EAPI '1'. You must upgrade to a > > newer version of portage before EAPI masked packages can be installed. > > > > For more information, see MASKED PACKAGES section in the emerge man page > or > > refer to the Gentoo Handbook. > > (dependency required by "sys-apps/help2man-1.37.1" [ebuild]) > > " > > > > /What should I do to solve this ? > > I've googled it , yet haven't found a solution ... ( found some stuff > > about it , but couldn't make it work ) > > please help ... > > Benny, welcome to the club. > > Try "env-update" then source /etc/profile. > > The env-update command straightens out all the /etc/env.d directories > for the new software that you installed. > > You're at the hard part, here, so keep going. > > After that, just post for us the output from "emerge --info" and a > little basic info about the machine you're running. > > >
