public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "coyote at coyotegulch dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/18013] make install failure: cannot touch `testsuite_wchar_t': Permission denied
Date: Fri, 15 Oct 2004 16:03:00 -0000 [thread overview]
Message-ID: <20041015160259.5067.qmail@sourceware.org> (raw)
In-Reply-To: <20041015152859.18013.coyote@coyotegulch.com>
------- Additional Comments From coyote at coyotegulch dot com 2004-10-15 16:02 -------
I can manually touch the file. The directory appears writable, and I have 40GB
of free space.
scott@Tycho ~/gnu/gcc-3.4/build-p4 $ ls
/home/scott/gnu/gcc-3.4/build-p4/i686-pc-linux-gnu/libstdc++-v3 -l
drwxr-xr-x 3 scott users 4096 Oct 15 10:55 testsuite
scott@Tycho ~/gnu/gcc-3.4/build-p4 $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda3 76312224 32244088 40191652 45% /
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18013
next prev parent reply other threads:[~2004-10-15 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 15:29 [Bug bootstrap/18013] New: " coyote at coyotegulch dot com
2004-10-15 15:49 ` [Bug bootstrap/18013] " pinskia at gcc dot gnu dot org
2004-10-15 16:03 ` coyote at coyotegulch dot com [this message]
2004-10-15 17:10 ` [Bug libstdc++/18013] " pinskia at gcc dot gnu dot org
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=20041015160259.5067.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).