Find the answer to your Linux question:
Results 1 to 3 of 3
Hello, Fellow LinuxForum-goers. As a first note, i only have 4-5 hours to fix this. Then am to be going to have to wait for a long time (say, two ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined! DingoBoy's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Installation Emerge Problem - Every single packadge masked


    Hello, Fellow LinuxForum-goers.
    As a first note, i only have 4-5 hours to fix this. Then am to be going to have to wait for a long time (say, two weeks) to try again. Just saying.

    I just installed Gentoo, x86 (using the standart i686).
    I followed the install instructions (this being my very first gentoo Installation).
    However, now that i got to having to install my kernel (emerge gentoo-sources) it claims that the packadge is masked (with masked by: missing keyword).
    The only other emerge actions have been, emerge --rsync (I know it's bad Chi, but i did this both when sceduled, and after first getting the masked message, to ensure i got it right), and emerge --oneshot portage (getting the newest portage according to the instructions.
    This is the output of my /etc/make.conf
    Code:
     
    # I Didn't mess around with this
    CFLAGS="-02 -march=i686 -pipe"
    # Or this
    CXXFLAGS="-02 -march=i686 -pipe"
    # Nor this
    CHOST="i686-pc-linux-gnu"
    # I manualle put this in
    MAKEOPTS="-j2"
    # And this
    USE="-kde gnome alsa"

    I used the desktop profile originally, but changed to default trying to fix this myself.

    Code:
    emerge --update world
    Say nothing is outdated

    Also, when i
    Code:
    emerge -s kernel
    , every single packadge is marked as masked. This confirms to me it is a global problem. (global as in my entire system - Do you say that in English?)




    Comradly, DingoBoy.

  2. #2
    Linux Enthusiast gruven's Avatar
    Join Date
    Dec 2004
    Location
    Arkansas
    Posts
    541
    It sounds like it is definitely a profile problem, since you said you changed it.

    I would go over that section of the handbook again and make sure you are using the correct profile.

    Post the output of:
    Code:
    ls -FGg /etc/make.profile
    and if it isn't what you want, then you want to do this:
    Code:
    ln -snf /usr/portage/profiles/default/linux/x86/2008.0 /etc/make.profile
    That will get you back to the default profile, and everything should be better.

    Linux User #376741
    Code is Poetry

  3. #3
    Just Joined! DingoBoy's Avatar
    Join Date
    Sep 2008
    Posts
    30
    Quote Originally Posted by gruven View Post
    It sounds like it is definitely a profile problem, since you said you changed it.

    I would go over that section of the handbook again and make sure you are using the correct profile.

    Post the output of:
    Code:
    ls -FGg /etc/make.profile
    and if it isn't what you want, then you want to do this:
    Code:
    ln -snf /usr/portage/profiles/default/linux/x86/2008.0 /etc/make.profile
    That will get you back to the default profile, and everything should be better.
    That did it! I choose /usr/portage/profiles/default instead of the full path. Must have misread that section.
    Thanks for the helping, much appritiated.

    Comradly, DingoBoy.

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •