public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/64094] "No such file or directory" -> "No such file"
Date: Mon, 08 Dec 2014 12:48:00 -0000	[thread overview]
Message-ID: <bug-64094-4-OryUdjBXKV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64094-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64094

--- Comment #5 from Jon Grant <jg at jguk dot org> ---
Hi Manu

I like your open_strerror() propopsal. Is this how Bintuils has done it?


Note: I realise this problem stems from ENOENT being used by both opendir() and
open(). I think you only need to provide two wrappers to handle these cases

Note: %m is not ideal in my view as it is a C Library extension that I believe
is not widely supported. could it be replaced with %s?
http://www.gnu.org/software/libc/manual/html_node/Other-Output-Conversions.html


Alternatively, could have a check where files are stat() before they are
opened, and then report the error then. Likewise for directories.


  parent reply	other threads:[~2014-12-08 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 11:18 [Bug pending/64094] New: " jg at jguk dot org
2014-11-27 12:16 ` [Bug driver/64094] " manu at gcc dot gnu.org
2014-11-27 13:40 ` harald at gigawatt dot nl
2014-11-27 14:10 ` schwab@linux-m68k.org
2014-12-08 12:48 ` jg at jguk dot org [this message]
2014-12-08 12:52 ` jg at jguk dot org
2014-12-08 13:01 ` schwab@linux-m68k.org
2014-12-09  9:41 ` jg at jguk 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=bug-64094-4-OryUdjBXKV@http.gcc.gnu.org/bugzilla/ \
    --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).