>>> emerge (6 of 11) dev-perl/XML-XQL-0.67-r1 to / --- No package manifest found: /usr/portage/dev-perl/XML-XQL/Manifest >>> md5 src_uri ;-) XML-XQL-0.67.tar.gz >>> Unpacking source... >>> Unpacking XML-XQL-0.67.tar.gz to /var/tmp/portage/XML-XQL-0.67-r1/work >>> Source unpacked. Checking if your kit is complete... Looks good ACCESS DENIED unlink: /usr/bin/perl1053012714 Warning: prerequisite XML::DOM 1.29 not found. Warning: prerequisite XML::Parser 2.30 not found. Writing Makefile for XML::XQL::Parser Writing Makefile for XML::XQL cp lib/XML/XQL/DOM.pm blib/lib/XML/XQL/DOM.pm cp lib/XML/XQL/Strict.pm blib/lib/XML/XQL/Strict.pm cp lib/XML/XQL/Date.pm blib/lib/XML/XQL/Date.pm cp lib/XML/XQL/Debug.pm blib/lib/XML/XQL/Debug.pm cp lib/XML/XQL/Query.pod blib/lib/XML/XQL/Query.pod cp lib/XML/XQL/Tutorial.pod blib/lib/XML/XQL/Tutorial.pod cp lib/XML/XQL/DirXQL.pm blib/lib/XML/XQL/DirXQL.pm cp lib/XML/XQL/Plus.pm blib/lib/XML/XQL/Plus.pm cp lib/XML/XQL.pm blib/lib/XML/XQL.pm make[1]: Entering directory `/var/tmp/portage/XML-XQL-0.67-r1/work/XML-XQL- 0.67/XQLParser' cp Parser.pm ../blib/lib/XML/XQL/Parser.pm make[1]: Leaving directory `/var/tmp/portage/XML-XQL-0.67-r1/work/XML-XQL- 0.67/XQLParser' cp bin/xql.pl blib/script/xql.pl /usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/xql.pl Manifying blib/man3/XML::XQL::DOM.3pm Manifying blib/man3/XML::XQL::Query.3pm Manifying blib/man3/XML::XQL::Tutorial.3pm Manifying blib/man3/XML::XQL::Date.3pm Manifying blib/man3/XML::XQL.3pm --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-XML-XQL-0.67-r1-15149.log" unlink: /usr/bin/perl1053012714 --------------------------------------------------------------------------------
Are you rebuilding this box? Or have you re-installed perl at any point, including an upgrade from perl 5.6.1 to perl 5.8.0? I ask because among other things (just tested again, it installs fine over here with sandbox enabled on an x86) I noticed that perl Makefile.PL failed to locate XML::DOM - which means that either your portage isn't honoring depends (unlikely), or that portage believes that the depends are met, but perl itself can't see the installed module. This doesn't directly relate to the sandbox errors you are receiving, but it may be related.
yes I wanted to install a perl photoalbum script bins. This has updated my perl to 5.8.0-r9 Quite possible that it was 5.6.1 before. Any idea what I can do?
You will need to re-emerge your installed perl modules. There is a script in <PORTAGE-DIR>/dev-lang/perl/files called libperl_rebuilder that should take care of most of that. This script is an attempt to rebuild anything compiled against your old version of perl, as well as rebuilding any modules that you had installed. It isn't without flaws, but is the best stab we have right now.
I don't think this sandbox error is depend related. I say that because I get the same error as OP about the sandbox violation and I have: dev-perl/XML-Parser-2.31-r1 dev-perl/XML-DOM-1.42 installed. Moreoever, I ran the libperl_rebuilder script and it bombed on the XML-XQL ebuild during pass 1, 2 &3 (but kept going after failing on that particular ebuild). IMO, in this case, it's 2 hours of wasted compilation time (on a P4 1.8GHz). If I didn't have ccache it would have take a little longer. Here's my emerge info: Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-ck6 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/portage.local" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts tetex bonobo svga tcltk java guile mysql postgres X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla cdr apache2 gtk2 jikes junit mbox" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math" CXXFLAGS="-march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="ccache sandbox userpriv usersandbox" Let's get to the real problem here. If I uncomment my FEATURES line in /etc/make.conf and issue emerge --oneshot XML-XQL I get a proper installation. Isn't that what we should be focusing on instead of looking at the dependencies? Regards,
Let's clarify this a little, first. I asked if you had rebuilt your box because before you even get to the sandbox errors, you have "Warning: prerequisite XXXXXX not found." The rebuilder script attempts to rebuild anything compiled against libperl.so, as well as modules that were previously installed under 5.6.1 and therefore no longer available in your @INC. Your sandbox problem is a different issue, but until I was certain you were working with a clean install I wanted to tackle this one step at a time.
2 things: 1. I am not the OP 2. I am working with a clean install.
Gadfly, Good point =:) (though my general rant about the rebuilder still stands, insofar as why it rebuilds your modules). Have you tried the .68 ebuild? Not that it differs in any way from the -r1 that is giving you trouble. Believe it or not, a related question, but can you confirm for me that version of ExtUtils::MakeMaker that you are using? Is it the default that came with your perl install or the ebuild inc portage? And which version-release of perl are you working with? A clean install can still be a 1.0, 1.2, or 1.4 profile is why I ask (the perl version varies for each one).
Hi Michael, Sorry about not mentioning earlier that my problems were indeed with the 0.68 ebuild. So, many things to tell... so little words to tell them in... Here's some answers to your questions: dev-lang/perl-5.8.0-r10 dev-perl/ExtUtils-MakeMaker-6.05-r5 The sandbox ACCESS DENIED violation are kind of strange because they seem to be wanting to unlink /usr/bin/perl### where ### seems to be epoch seconds. Odd! Here's some sample values in order: /usr/bin/perl1056144838 /usr/bin/perl1056144889 /usr/bin/perl1056144953 Furthermore, they only occur if userpriv and usersandbox are BOTH present in FEATURES in /etc/make.conf Sorry, if I'm not being very helpful here. The machine itself used to be a gentoo 1.2 which was updated to 1.4 long, long time ago. So, I'm not sure if I know what "clean" is?
In comment 4, I earlier said: > If I uncomment my FEATURES line in /etc/make.conf and > issue emerge --oneshot XML-XQL I get a proper installation. That should have been instead: If I comment my FEATURES line.
Hi, to give you a feedback as original reporter: The libperl_rebuilder script has solved the problem for me. XML-XQL was compiling without any errors Thx,
Gadfly - this still an issue? OP has it marked as working now.
Yes, it is still an issue for me. Not to be redundant, but to be clear, "the sandbox violations only occur if userpriv and usersandbox are BOTH present in FEATURES in /etc/make.conf" Thanks,
Carpaski, Adding you to this bug as a cc. User is having problems compiling a module when usersandbox and userpriv are in their FEATURES - sandbox violations. Any thoughts?
Gadfly, Yours is a problem that is solved in the next release of portage and is not a perl related problem. If you continue to experience problems after the next portage upgrade, please submit a bug to the portage team. Thanks, Michael
