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 pending/64094] New: "No such file or directory" -> "No such file" Date: Thu, 27 Nov 2014 11:18:00 -0000 [thread overview] Message-ID: <bug-64094-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64094 Bug ID: 64094 Summary: "No such file or directory" -> "No such file" Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: pending Assignee: unassigned at gcc dot gnu.org Reporter: jg at jguk dot org Hello I saw when "main.cpp" is not accessible, the standard ENOENT message "No such file or directory" is used. However, this is not really accurate, as it was open() that was used to open a file. A file was expected, therefore if GCC could output "No such file" the message would be clearer. I objdump has this behaviour already: $ objdump -a main2.exe objdump: 'main2.exe': No such file $ gcc --version gcc (GCC) 4.8.3 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ gcc -o main main.cpp gcc: error: main.cpp: No such file or directory gcc: fatal error: no input files compilation terminated.
next reply other threads:[~2014-11-27 11:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-27 11:18 jg at jguk dot org [this message] 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 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@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: linkBe 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).