LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Distributions (https://www.linuxquestions.org/questions/linux-distributions-5/)
-   -   GENTOO : emerge PORTAGE Failed due to sandbox (https://www.linuxquestions.org/questions/linux-distributions-5/gentoo-emerge-portage-failed-due-to-sandbox-613899/)

billymayday 02-16-2008 12:32 AM

Having looked at both of these, util-linux looks like something you need and setarch doesn't (http://linuxcommand.org/man_pages/setarch8.html).

I'd try removing setarch and see how it goes.

What does anyone else think (you can always reinstall if you absolutely need to).

Shingoshi 02-16-2008 01:57 AM

You didn't read the last paragraph of my last post...
 
Quote:

Originally Posted by billymayday (Post 3058911)
Having looked at both of these, util-linux looks like something you need and setarch doesn't (http://linuxcommand.org/man_pages/setarch8.html).

I'd try removing setarch and see how it goes.

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.

Shingoshi

billymayday 02-16-2008 02:57 AM

Looks to me like you edited while I was responding since your last edit was one minute prior to my post - and it took more than that for me to reply

Edit

regarding following post - no offense taken. Rgds

Shingoshi 02-16-2008 03:28 AM

Sorry about that.
 
Quote:

Originally Posted by billymayday (Post 3059008)
Looks to me like you edited while I was responding since your last edit was one minute prior to my post - and it took more than that for me to reply

I accused you of not paying attention. Sorry. I could have looked myself to verify the time that you posted that. Again, I'm sorry.

Shingoshi

Electro 02-16-2008 03:36 AM

I suggest using the following command as root.

revdep-rebuild --ignore --pretend

This will hopefully fix your setup.

Shingoshi 02-16-2008 04:42 AM

Are you referring to the old setup which I have since dropped into a basket.
 
Quote:

Originally Posted by Electro (Post 3059019)
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.

Shingoshi

Shingoshi 02-16-2008 11:45 AM

You will find the continuation of this off topic thread in this new location.
 
If any of you are interested in continuing this topic, you will now find it here in this new thread:

http://www.linuxquestions.org/questi...85#post3059085

I wish to thank all of you for your participation and contributions.

Shingoshi

Shingoshi 02-16-2008 06:53 PM

Here's a link to a question I felt better asked in a new thread.
 
http://www.linuxquestions.org/questi...45#post3059745

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.

============================================
starbase64 / # emerge lm_sensors --pretend

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-devel/binutils-2.18-r1 USE="multislot*"
[ebuild R ] sys-apps/groff-1.19.2-r1 USE="X*"
[ebuild N ] sys-apps/lm_sensors-2.10.4 USE="-sensord"
============================================

Please use the above link, and answer this question there and not here.

Shingoshi

NEVERMIND: My assumption was correct that they were only meant to be rebuilt.

JackTrust 03-04-2008 12:20 AM

Quote:

Originally Posted by Emerson (Post 3050179)
Use eselect profile list to see common profiles. Profiles are stored in /usr/portage/profiles/, to use them symlink desired one to /etc/make profile.

/etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2007.0

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.



I attempted to do this by typing;

/etc/make.profile -> ../usr/portage/profiles/default-linux/amd64/2007.0

at the prompt and it comes back with "There is no such file or directory"

I also tryed without the two dots (..) in front of /usr/portage/profiles/default-linux/amd64/2007

and it says it's a directory.

I have confirmed and verified that both directories exist.

What am I doing wrong here?

Thanks

JackTrust 03-04-2008 12:41 AM

***Accidental repost. Same as above.***

Quote:

Originally Posted by Emerson (Post 3050179)
Use eselect profile list to see common profiles. Profiles are stored in /usr/portage/profiles/, to use them symlink desired one to /etc/make profile.

/etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2007.0

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.



I attempted to do this by typing;

/etc/make.profile -> ../usr/portage/profiles/default-linux/amd64/2007.0

at the prompt and it comes back with "There is no such file or directory"

I also tryed without the two dots (..) in front of /usr/portage/profiles/default-linux/amd64/2007

and it says it's a directory.

I have confirmed and verified that both directories exist.

What am I doing wrong here?

Thanks

gaug 04-26-2008 05:23 PM

I had the same probleme to compile on ABIS=amd64 sandbox and sandbox want to compile on ABIS=x86. I find this solution

Code:

#MULTILIB_ABIS="amd64" emerge --oneshot sandbox
And all compile just fine.

casidiablo 09-07-2009 02:14 AM

Quote:

Originally Posted by gaug (Post 3133959)
I had the same probleme to compile on ABIS=amd64 sandbox and sandbox want to compile on ABIS=x86. I find this solution

Code:

#MULTILIB_ABIS="amd64" emerge --oneshot sandbox
And all compile just fine.

I singed up in linuxquestions just to say: THANKS. I've been finding the solution for this issue for hours, and your response solved my problem.

Thank you so much!


All times are GMT -5. The time now is 06:20 PM.