From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27953 invoked by alias); 29 Dec 2013 16:20:36 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 27907 invoked by uid 48); 29 Dec 2013 16:20:29 -0000 From: "aneejit1 at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: build X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: aneejit1 at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg00216.txt.bz2 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.