public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martinrb at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/37786] Documentation for `-symbolic' needs fixing
Date: Thu, 09 Oct 2008 19:28:00 -0000	[thread overview]
Message-ID: <20081009192648.11865.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37786-16725@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from martinrb at google dot com  2008-10-09 19:26 -------
(In reply to comment #2)
> "Only a few      systems support this option."
> 
> x86-linux-gnu is one of those targets that don't support this option :).
> 
> There is no changes needed here for the documentation as far as I can tell so
> closing as invalid.

Dear bugmeister,

At the very least the documentation could be made less confusing.
The documentation for GNU ld gives:

`-Bsymbolic'
     When creating a shared library, bind references to global symbols
     to the definition within the shared library, if any.  Normally, it
     is possible for a program linked against a shared library to
     override the definition within the shared library.  This option is
     only meaningful on ELF platforms which support shared libraries.

The wording is sufficiently similar that one might think
`-symbolic' and `-Bsymbolic' have the same meaning.
Yet on x86-linux-gnu, the first fails, while the second appears to succeed.

$ gcc -symbolic main.c; echo --; gcc -Bsymbolic main.c
gcc: unrecognized option '-symbolic'
--

Also, gcc has a documented `-B' flag with a completely different meaning.

All in all, I think there is at least scope for improved clarity
in the documentation.  I've used gcc for decades, but am still confused.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37786


  parent reply	other threads:[~2008-10-09 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:54 [Bug driver/37786] New: " martinrb at google dot com
2008-10-09 18:58 ` [Bug driver/37786] " pinskia at gcc dot gnu dot org
2008-10-09 19:02 ` pinskia at gcc dot gnu dot org
2008-10-09 19:28 ` martinrb at google dot com [this message]
2008-10-09 20:36 ` pinskia at gcc dot gnu dot org
2008-10-09 23:11 ` martinrb at google dot com
2008-10-09 23:17 ` pinskia at gcc dot gnu dot org
2008-10-09 23:18 ` martinrb at google dot com

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=20081009192648.11865.qmail@sourceware.org \
    --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).