From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Problems building www-client/uzbl-9999
Date: Wed, 25 Sep 2013 03:33:07 -0400 [thread overview]
Message-ID: <20130925073307.GA25548@waltdnes.org> (raw)
Since this is a 9999 ebuild, I'm not filing a bugzilla bug. Note that
www-client/uxbl-2012.05.14 built OK. Apparently, the latest git sources
have some features I really want, that are not in any of the other
ebuilds. So I'm trying to build it. The 9999 build first pulled down
and installed git, so that it could then pull the latest uzbl source.
The compile seems to have gone OK, but the final install process ran
into permission problems creating a directory. Here's the part with the
error...
> running build_scripts
> running install_lib
> creating /usr/lib64/python3.2/site-packages/uzbl
> * ACCESS DENIED: mkdir: /usr/lib64/python3.2/site-packages/uzbl
> error: could not create '/usr/lib64/python3.2/site-packages/uzbl': Permission denied
> make: *** [install-event-manager] Error 1
> * ERROR: www-client/uzbl-9999 failed (install phase):
> * emake failed
I'm attaching the full log. The system is a Dell Intel i5, with
pure 64-bit mode (no multilib), and the basic workstation profile, cut
down even more by starting USE with "-*" and adding the flags I need for
a "custom profile".
This is the first time I've tried a "9999" ebuild, so I may be missing
something obvious. /usr/lib64/python3.2/site-packages/ is user:group
root:root
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next reply other threads:[~2013-09-25 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 7:33 Walter Dnes [this message]
2013-09-25 8:32 ` [gentoo-user] Problems building www-client/uzbl-9999 Walter Dnes
2013-09-25 8:33 ` Alan McKinnon
2013-09-25 23:01 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130925073307.GA25548@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox