Hi,
I have a gentoo system that I've installed (stage 2) a few months
ago with the default options, no optimisations. After some research I
decided to add some optimisations in the CFLAGS and USE variables on the
make.conf. I'll take my chances with the following configuration in CFLAGS:
-march=athlon-xp -O3 -fomit-frame-pointer -pipe -m3dnow -mmmx -msse
-mfpmath=sse
-fforce-addr -ftracer -fmove-all-movables -fprefetch-loop-arrays
-maccumulate-outgoing-args
-ffast-math
I'm aware that it is risky to include options like -ffast-math and
-mfpmath=sse, but I reckon that if it passes the TEST fase while merging
it should work fine, and there are people out there that used all these
flags on gentoo stating that their systems seem to be stable and working
fine (and faster), so I'll give it a go.
But enough of preliminaries, let's go to the questions:
* My system is a bit outdated, so if I emerge --update and emerge
--emptytree (in whichever order) I'll spend many unnecessary hours
compiling many packages all over again (mostly all the kde 3.4.1).
Question: Is there a way to do a mix of both?
* I actually started with emerge --emptytree world, and failed twice
(I have maketest in FEATURES ): gettext failed while asking for missing
libraries (lib<IdontRecall>{x,y,z}.so), so I disabled the maketest, then
emerged with --resume, aborted after gettext was installed, enabled
maketest again and finally continued emerging with --resume. Question:
is there a way to enable/disable the maketest for a single package while
emerging many? Note: I believe the gettext TEST phase failing is
unrelated to my choice of compiler options, it seems to be buggy
* I decided to emerge -f -e world on one session (to speed things
up), and after a few packages were downloaded start emerge -e world in
another. Question: Is it any dangerous to run more than one emerge
simultaneously? Wouldn't it be a good idea to have emerge download all
the required packages in the background while compiling?
* emerge failed while testing the glibc (due to the noatime setting
in /, which seems to be a bug in the testing script). By this time the
emerge -f -e world had finished downloading all the packages. I
remounted the partitions with atime and diratime and attempted to
--resume, but it would not resume it. Question: did it fail because the
other emerge had finished? How/where does portage store the details of
the current emerge to allow resuming? Is there a way to resume starting
at a particular point?
* I saved the output of emerge -e world --pretend to a file, removed
the brackets and their contents and prefixed each package with an =
(equal sign), deleting all the 65 packages that I had previously emerged
successfully. Then attempted to emerge ` cat packages.txt ` and to my
surprise the list included the required updates, so I wen't for it.
Question: is it expected to have some packages upgraded when the
packages emerged were specified as =package-x.y?
* I tried " emerge `qpkg -I -nc |grep -oe '^[^ ]*' ` --pretend " and
it seems to do the job, but it looks like there are more packages there
than in the list of " emerge --emptytree world --pretend ", some
violating dependencies, others blocking while requirying the ~x86 flag.
Question: Are absolutely all the packages recompiled with emerge
--emptytree world?
I'm sorry to be such a pain in the arse, you must be exhausted if
you reached this line! Anyway, thanks in advance for your support.
Ezequiel Tolnay
BTW, the glibc package failed again, this time while testing
tst-cancel17 ... :-(
--
gentoo-user@gentoo.org mailing list
