public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/63881] New: [5 Regression] patch to error out when input file is the same as output file causes glibc's config to fail Date: Sat, 15 Nov 2014 04:46:00 -0000 [thread overview] Message-ID: <bug-63881-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63881 Bug ID: 63881 Summary: [5 Regression] patch to error out when input file is the same as output file causes glibc's config to fail Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org glibc's log has this: configure:95: checking for SSE4 support configure:101: /data1/src/gcc-cavium/toolchain-thunder/scripts/../minimal-i686-montavista-linux-gnu/bin/i686-montavista-linux-gnu-gcc -m32 -O2 -msse4 -xc /dev/null -S -o /dev/null i686-montavista-linux-gnu-gcc: fatal error: input file '/dev/null' is the same as output file Which is incorrect as /dev/null is a special file and should be handled differently.
next reply other threads:[~2014-11-15 4:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-15 4:46 pinskia at gcc dot gnu.org [this message] 2014-11-15 4:46 ` [Bug driver/63881] " pinskia at gcc dot gnu.org 2014-11-16 22:03 ` trippels at gcc dot gnu.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-63881-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).