Emacs seems to have a sand box error well compilling that stops it coold and leaves sandbox running so i have to relog in Reproducible: Always Steps to Reproduce: 1.'emerge emacs --ask' (NOTE: I tried setting pakage.use in several ways including default and -*) Actual Results: It seemed to compile till it hit the part in the first screen shot. Atempting the comand without reloging in will make get the results in the second screen shot. https://i.imgur.com/xGDTqlh.png (NOTE: The ^X as a misteke that has no effect and the ^C was so you could see what it dose when I try to make it stop.) https://i.imgur.com/Y9FOAHr.png Expected Results: Emacs should emerge normally.
1) Please attach the entire build log to this bug report. 2) Please post your `emerge --info' output in a comment.
(In reply to Jeroen Roovers from comment #1) > 1) Please attach the entire build log to this bug report. > 2) Please post your `emerge --info' output in a comment. Oh yes, how silly of me. http://bpaste.net/show/407787/ And thank you for getting back to me so quickally.
(In reply to Jeroen Roovers from comment #1) > 1) Please attach the entire build log to this bug report. > 2) Please post your `emerge --info' output in a comment. Don't use external sources, please. Attach means make an attachment to this bug report under "Attachments". Posting information means pasting it in a comment.
Created attachment 379688 [details] emerge --info
(In reply to Jeroen Roovers from comment #3) > (In reply to Jeroen Roovers from comment #1) > > 1) Please attach the entire build log to this bug report. > > 2) Please post your `emerge --info' output in a comment. > > Don't use external sources, please. Attach means make an attachment to this > bug report under "Attachments". Posting information means pasting it in a > comment. Oh yes, how silly of me. Anyway i posted it like you asked. Thanks.
Build log?
Created attachment 379694 [details] Build log
(In reply to Jeroen Roovers from comment #6) > Build log? Added.
I cannot reproduce the problem. What version of setfattr is installed on your system? ("/bin/setfattr --version" to find out.) What happens if you call setfattr manually, like this: $ touch /var/tmp/conftest.tmp $ /bin/setfattr -n user.pax.flags /var/tmp/conftest.tmp
(In reply to Ulrich Müller from comment #9) > I cannot reproduce the problem. > > What version of setfattr is installed on your system? ("/bin/setfattr > --version" to find out.) > > What happens if you call setfattr manually, like this: > $ touch /var/tmp/conftest.tmp > $ /bin/setfattr -n user.pax.flags /var/tmp/conftest.tmp "setfattr 2.4.47" setfattr seems to lock up in the same way as Emacs.
(In reply to silverwerwolf13 from comment #10) > setfattr seems to lock up in the same way as Emacs. What type of filesystem is /var/tmp/ on?
(In reply to Ulrich Müller from comment #11) > (In reply to silverwerwolf13 from comment #10) > > setfattr seems to lock up in the same way as Emacs. > > What type of filesystem is /var/tmp/ on? ext3
This doesn't look like a problem in Emacs, therefore reassigning to base-system.
please go into your /var/tmp/portage/ dir and run the same command: touch foo setfattr -n user.pax.flags foo if that hangs, then run it through strace: strace -f -o log -s 4096 -v setfattr -n user.pax.flags foo and then attach that log file here
