public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/99896] g++ drops -lc
Date: Sun, 04 Apr 2021 02:02:52 +0000 [thread overview]
Message-ID: <bug-99896-4-A7y5iO1kpB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99896-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99896
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matz at suse dot de
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Tom de Vries from comment #2)
> > I don't understand. AFAICT, it's dropped. It's not moved to the end,
> > because -lc is already at the end without specifying -lc.
>
> OK, it's dropped because it's always present at the end.
>
> This is similar to adding -I/usr/include which gets ignored, because it's
> already going to be searched anyway as a system header directory. Quoting
> the manual:
>
> "If a standard system include directory, or a directory specified with
> -isystem, is also specified with -I, the -I option is ignored."
>
>
> > Um, for my understanding, does that mean you agree this is a bug in g++?
>
> No.
>
OK, so here ( https://gcc.gnu.org/onlinedocs/gcc/Invoking-GCC.html#Invoking-GCC
) I read:
...
Also, the placement of the -l option is significant.
...
So, if the documentation of gcc says that placement of the -l option is
significant, then why does g++ decide to mess with that? ISTM g++ violates
documented behaviour.
next prev parent reply other threads:[~2021-04-04 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 13:04 [Bug driver/99896] New: " vries at gcc dot gnu.org
2021-04-03 14:32 ` [Bug driver/99896] " redi at gcc dot gnu.org
2021-04-03 16:57 ` vries at gcc dot gnu.org
2021-04-03 18:01 ` schwab@linux-m68k.org
2021-04-03 20:30 ` redi at gcc dot gnu.org
2021-04-03 22:45 ` schwab@linux-m68k.org
2021-04-04 2:02 ` vries at gcc dot gnu.org [this message]
2021-04-06 14:16 ` matz 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-99896-4-A7y5iO1kpB@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).