public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66765] gfortran passing fortran-specific options to ld and collect2
Date: Sun, 30 Aug 2015 14:40:00 -0000	[thread overview]
Message-ID: <bug-66765-4-qJS4LcsTM7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66765-4@http.gcc.gnu.org/bugzilla/>

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

David Edelsohn <dje at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #2 from David Edelsohn <dje at gcc dot gnu.org> ---
This has nothing to do with dejagnu.  On AIX, collect2 re-invokes the compiler
and collect2 uses the compiler command-line arguments.  With or without
dejagnu, the command is invoking a fortran-specific option *and* invoking the
linker wrapped with collect2 to generate an executable.


  parent reply	other threads:[~2015-08-30 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04 16:30 [Bug fortran/66765] New: gfortran invoking cc1 on AIX dje at gcc dot gnu.org
2015-08-30 14:29 ` [Bug fortran/66765] gfortran passing fortran-specific options to ld and collect2 dominiq at lps dot ens.fr
2015-08-30 14:40 ` dje at gcc dot gnu.org [this message]
2015-08-30 15:23 ` dominiq at lps dot ens.fr
2015-08-30 17:29 ` dje at gcc dot gnu.org
2015-08-30 18:10 ` dominiq at lps dot ens.fr
2015-08-30 18:12 ` dominiq at lps dot ens.fr
2015-08-30 19:58 ` dje at gcc dot gnu.org
2015-08-30 21:25 ` dominiq at lps dot ens.fr
2015-08-31  0:05 ` dje at gcc dot gnu.org
2021-12-18  2:49 ` [Bug driver/66765] " pinskia 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-66765-4-qJS4LcsTM7@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).