IWBCMAN Guru
Joined: 25 Jun 2002 Posts: 474
|
Posted: Sun Aug 25, 2002 10:24 am Post subject: |
|
|
sounds like portage got b0rked....
If I were you...reformat and start again.....
or unapck the stageX tarball again ovetop of your existing install..(remeber things like your settings in fstab, rc.conf, make.conf, resolv.conf and modules.autoload)
with the exception of the installation phase I find portage to be very very stable...but during the install phase, if a package fails to install, it sometimes can leave you without a working portage system.....and finally a note to all if your are using a pentium 4 and wish to install the stageX-1.4 tarball ONLY USE "-march=i686 -O3 -pipe"....I mention this beccause only two files fail w/ more aggressive settings(-fomit-frame-pointer -malign-double -mfpmath=sse -mmmx -msse -funroll-loops-frerun-cse-after-loop) when you do an emerge system(perly/python) and when you do an emerge kde only kdebase fails......BUT don´t be decieved by successfull compilation......many,many key things will be borked if you you use aggressive settings---gnome flakes completely with such optimizations and kde crashes permanently with segfaults everywhere....gnomes scroll-keeper will not function w/ those agrresive settings meaning that nothing gets registered right as regards gnome-session.........Install everything with boring conservative simple flags, as listed above, and if everything works right afterwords selecvtively recompile key libraries with the more aggreessive settings,
I ran into problems with aggressive settings with zlib, ncompress, gzip, tar-all of which compiled, but b0rked afterwards, python, perl failed to compile at all, and neither gnome or kde were functioning after doing a stage1-x86-1.4 install with aggressive settings -I am trying to save my ass now doing an emerge -e kde gnome w/ simple settings..... |
|