Robert Schweikert wrote:
I am trying to update my gentoo distribution that I am running on my laptop. When emerge is running the build for X.org gcc blows up with an internal compiler error. I am assuming at this point that there is a memory issue, i.e. not enough horsepower on the laptop. However, when I change to the working directory and then run make and make install everything works just fine, i.e. the compiler only blows up when run from emerge.

I'd say that's it's either a CFLAGS or memory issue, in which case with the memory one, I'd guess that portage just takes a little bit of extra memory that makes it too much. Increasing the swap size would help if it's a memory issue.
My question is now, how do I tell portage that the package in question is already installed and to move on to the next package to be upgraded?

look at "man emerge":
       --inject (-i)
              Injecting  a  package  inserts a 'stub' for that package so that
              Portage thinks that it is installed.  It is handy if  you  need,
              say,  a  binary version of XFree86 for esoteric hardware, or you
              just like to roll your own packages.  You must specify  a  cate-
              gory  and  particular  version  of a package for injecting.  For
              example, emerge --inject sys-kernel/gentoo-sources-2.4.19.
So you would run "emerge --inject x11-base/xorg-x11" except when I try a --pretend of that it says:
*** --inject has been deprecated.
*** If you manage a piece of software yourself, add it's name and
*** version (eg foo/bar-1.0) to /etc/portage/profile/package.provided.
*** If you want to prevent portage from upgrading a package, add it to
*** /etc/portage/package.mask prepending it with '>' (eg >foo/bar-1.0)
*** For more information on fine-grained portage control, please see
*** the portage man page.
So you would add the line "/x11-base/xorg-x11" (except with the version number as well) to the file "/etc/portage/profile/package.provided" (create it if it does'nt already exist)

    Alex Schultz

Reply via email to