public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105599] g++ by itself is not producing "fatal error: no input files" for darwin target
Date: Fri, 13 May 2022 23:03:47 +0000	[thread overview]
Message-ID: <bug-105599-4-n7Ld5httz3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105599-4@http.gcc.gnu.org/bugzilla/>

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

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-05-13
     Ever confirmed|0                           |1

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
gcc version 12.0.1 20220429 (prerelease) [gcc-12-1rc1 revision
r12-8321-g621650f64fb6] (GCC) 
gcc-12-1-darwin mini-07-cat:gcc-git-12 isandoe$
/opt/iains/x86_64-apple-darwin19/gcc-12-1rc1/bin/gcc
gcc: fatal error: no input files
compilation terminated.

$ /opt/iains/x86_64-apple-darwin19/gcc-12-1rc1/bin/g++
ld: -rpath can only be used when targeting Mac OS X 10.5 or later
collect2: error: ld returned 1 exit status

So, we have some addition to the command line from the g++ driver that is
causing this (the actual reported problem is not significant, the reason is
that the command line is not being seen as empty by the darwin driver)

  parent reply	other threads:[~2022-05-13 23:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 21:06 [Bug c++/105599] New: g++ binary: undefined symbols _main referenced from __start in crt1.0 mario_grgic at hotmail dot com
2022-05-13 22:05 ` [Bug target/105599] g++ by itself is not producing "fatal error: no input files" for darwin target pinskia at gcc dot gnu.org
2022-05-13 22:21 ` iains at gcc dot gnu.org
2022-05-13 23:03 ` iains at gcc dot gnu.org [this message]
2022-05-29 18:27 ` cvs-commit at gcc dot gnu.org
2022-06-15 19:07 ` cvs-commit at gcc dot gnu.org
2022-06-15 19:09 ` iains at gcc dot gnu.org
2023-05-16 19:01 ` cvs-commit at gcc dot gnu.org
2023-05-16 19:10 ` iains at gcc dot gnu.org
2024-04-24 18:36 ` cvs-commit 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-105599-4-n7Ld5httz3@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).