Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What does anyone else think (you can always reinstall if you absolutely need to).
I clearly stated that setarch should be removed. It really isn't an option, it must be done. So let me repeat myself:
Quote:
Originally Posted by Shingoshi
Ok. The solution was found. setarch in now included in util-linux, and can be safely removed to continue with "emerge -e system", which is running now. 98 packages have to be emerged.
Are you referring to the old setup which I have since dropped into a basket.
Quote:
Originally Posted by Electro
I suggest using the following command as root.
revdep-rebuild --ignore --pretend
This will hopefully fix your setup.
The original setup which I was trying to fix, has been dropped into a folder named ".old" in my root directory. I have since abandoned that old root entirely, and started over with a new stage3. The stage3 I used before was for the hardened-multilib. That was a nightmare. So I decided to start over from scratch, rather than beating my head against the wall. Maybe, just maybe, I'll go back and try to repair that old root later. But right now, I am committed to building the new root from a new (generic) stage3 (I made a mistake here and wrote stage2).
For the purposes that I'm engaging in, I haven't even chosen a different profile, other than what is specified by the default installation of stage3. My present thinking is this. I will use this new root as my build engine. I will use it to construct a stage4 installation. That tarball will then be copied to my functional system, and will then be used for daily operations. But the present build I'm engaged in now, will remain in pristine condition. Meaning I will make no changes (ie. customizations) in it except to add all of the packages I want to use in my working system. I will let conf-update handle all of the changes in /etc. Beyond that, I won't do anything else to it.
I am also thinking that I should start this as a new thread, explaining how to complete this process in detail for new users like myself.
Presently, I'm in the final stages (95 of 98 @ glibc-2.6.1) of running "emerge -e system". When this is done, I will then install the following:
lzma-utils (For my man pages)
cppunit (I will doing a lot of compilations)
distcc
doxygen
ccache
sandbox (This is what started the whole mess in the first place!)
mc (I never work without this.)
gentoolkit-dev (For all the extra functions I will need in the future.)
ufed (Because I really like seeing what I'm doing in a gui.)
conf-update (Same here as above.)
revdeps-rebuild (Required by rebuilding glibc.)
autounmask (Now on to the fun stuff.)
boost (Because most of what I'll be doing in the future, requires this.)
I will be adding more to this as I go along. This probably really ought to be a new thread.
This concerns emerge apparently stating it will remove binutils and groff. That doesn't seem right, and I think it only want to rebuild them for the new use flags I've set.
If you have working sandbox you can skip the build in emerge -e system/world process, use emerge --skipfirst, you can even come back after emerge -e is finished and try again, it may build then.
You can also live without sandbox, to turn it off permanently add FEATURES="-sandbox" to your make.conf.
@billymayday
Setting FEATURES in make.conf has same effect as setting it from command line. Actually command line overrides everything else. -oneshot option does not change anything in build process, the only difference it makes is package is not stored in world file.
If you have working sandbox you can skip the build in emerge -e system/world process, use emerge --skipfirst, you can even come back after emerge -e is finished and try again, it may build then.
You can also live without sandbox, to turn it off permanently add FEATURES="-sandbox" to your make.conf.
@billymayday
Setting FEATURES in make.conf has same effect as setting it from command line. Actually command line overrides everything else. -oneshot option does not change anything in build process, the only difference it makes is package is not stored in world file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.