public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aneejit1 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/14121] make writes .mo files in po directory
Date: Sun, 29 Dec 2013 16:20:00 -0000	[thread overview]
Message-ID: <bug-14121-131-ItX6qe6Qd2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14121-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14121

--- Comment #4 from aneejit1 at gmail dot com ---
My setup is as follow:

1. The source is on user "source".  Its home directory is on NFS and mounted
read-only as /home/source with the glibc source in g/glibc/glibc-2.18.
2. Group/other do not have write permissions for the source files.
3. The user is "build" which has its home directory on NFS mounted read only as
/home/build.  The object directory is
projects/g/glibc/glibc-2.18/x86_64-unknown-linux-gnu.
4. The configure command is "configure --prefix=/usr --libdir=/usr/lib64
--localstatedir=/var --sysconfdir=/etc --enable-add-ons=nptl".
5. No special "make" options are being used.

The build fails on "permission denied" in the "po" subdirectory as it is
attempting to write the ".mo" files to the source directory which it cannot do
as not only are the file/directory permissions are against it (the group/other
settings are read-only) but the source directory is on read-only NFS.  At this
moment in time, I do not think it is the NFS part which is an issue, it is the
read-only source directory which appears to highlight the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-12-29 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 18:41 [Bug build/14121] New: " aj at suse dot de
2013-12-08 17:18 ` [Bug build/14121] " aneejit1 at gmail dot com
2013-12-08 17:19 ` aneejit1 at gmail dot com
2013-12-27 21:45 ` carlos at redhat dot com
2013-12-29 16:20 ` aneejit1 at gmail dot com [this message]
2014-06-25 10:57 ` fweimer at redhat dot com

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=bug-14121-131-ItX6qe6Qd2@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).