From: Reuben Thomas <rrt@sc3d.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile <bug-guile@gnu.org>
Subject: Re: Building GUILE from git
Date: Tue, 6 Apr 2010 00:05:16 +0100 [thread overview]
Message-ID: <o2tf92540e31004051605h47eabcdft67c06f75253f01c9@mail.gmail.com> (raw)
In-Reply-To: <87k4sllddn.fsf@gnu.org>
Thanks, it's the usual automake permissions problem, i.e. that because
my user's umask is 0027, directories made during "sudo make install"
are made with the same permission, although files are installed
correctly. I had manually corrected the permissions on the other
directories in /usr/local/share and /usr/local/include, but I hadn't
spotted /usr/local/lib. Fixing the permissions there makes it work
perfectly; thanks!
--
http://rrt.sc3d.org
prev parent reply other threads:[~2010-04-05 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f92540e31003240335r6e285db9jdbc936e51de7646a@mail.gmail.com>
[not found] ` <m3eiiu7yac.fsf@pobox.com>
2010-04-05 18:57 ` Building GUILE from git Reuben Thomas
2010-04-05 22:53 ` Ludovic Courtès
2010-04-05 23:05 ` Reuben Thomas [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=o2tf92540e31004051605h47eabcdft67c06f75253f01c9@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).