public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de> To: aj@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: web/7603: Incorrect flag specified in page Date: Thu, 15 Aug 2002 11:56:00 -0000 [thread overview] Message-ID: <20020815173604.2670.qmail@sources.redhat.com> (raw) The following reply was made to PR web/7603; it has been noted by GNATS. From: Andreas Jaeger <aj@suse.de> To: rchiang@nvidia.com Cc: gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: web/7603: Incorrect flag specified in page Date: Thu, 15 Aug 2002 19:27:44 +0200 rchiang@nvidia.com writes: >>Number: 7603 >>Category: web >>Synopsis: Incorrect flag specified in page >>Confidential: no >>Severity: serious >>Priority: medium >>Responsible: gerald >>State: open >>Class: doc-bug >>Submitter-Id: net >>Arrival-Date: Thu Aug 15 09:36:00 PDT 2002 >>Closed-Date: >>Last-Modified: >>Originator: rchiang@nvidia.com >>Release: GCC 3.2 >>Organization: >>Environment: > >>Description: > The web page at > > http://gcc.gnu.org/gcc-3.2/c++-abi.html > > Specifies that "-enable-shared" should be set. The correct flag should be "--enable-shared". fixed with the appended patch which I committed as obvious. thanks, Andreas Index: htdocs/gcc-3.2/c++-abi.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/c++-abi.html,v retrieving revision 1.2 diff -u -p -r1.2 c++-abi.html --- htdocs/gcc-3.2/c++-abi.html 9 Aug 2002 13:41:17 -0000 1.2 +++ htdocs/gcc-3.2/c++-abi.html 15 Aug 2002 17:27:31 -0000 @@ -22,16 +22,16 @@ the guidelines given here for GNU/Linux systems.</p> <h2>Configuring GCC</h2> - + <p>Configure GCC with this options:</p> <pre> --enable-__cxa_atexit </pre> - + <p>GCC is configured by default on GNU/Linux systems also with these two flags, do not change them to any other value:</p> <pre> - --enable-threads=posix -enable-shared + --enable-threads=posix --enable-shared </pre> <p>If you do not use these options, your files generated by GCC will not be fully ABI compatible.</p> @@ -55,14 +55,14 @@ this order:</p> <ol> <li>New binutils version</li> - <li>New glibc version</li> + <li>New glibc version (on GNU/Linux systems only)</li> <li>GCC 3.2</li> </ol> <p>Especially, if you update binutils, you should rebuild glibc so that glibc can take advantage of some new options of binutils.</p> <h2>Caveat</h2> - + <p>Since GCC now implements a written ABI that is also implemented by other compiler vendors, it might be that we encounter different interpretations of the ABI by the vendors, bugs in the ABI or bugs -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2002-08-15 17:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-15 11:56 Andreas Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-15 10:36 aj 2002-08-15 10:29 rchiang
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=20020815173604.2670.qmail@sources.redhat.com \ --to=aj@suse.de \ --cc=aj@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).