From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12105 invoked by alias); 9 Oct 2008 19:28:08 -0000 Received: (qmail 11866 invoked by uid 48); 9 Oct 2008 19:26:48 -0000 Date: Thu, 09 Oct 2008 19:28:00 -0000 Message-ID: <20081009192648.11865.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug driver/37786] Documentation for `-symbolic' needs fixing In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "martinrb at google dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-10/txt/msg00650.txt.bz2 ------- 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