public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/4025: Bootstrap fails to create jv-convert (undefined refs)
Date: Wed, 15 Aug 2001 03:46:00 -0000 [thread overview]
Message-ID: <20010815104605.19504.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR bootstrap/4025; it has been noted by GNATS.
From: Gabriel Dos Reis <gdr@codesourcery.com>
To: Gordon Sadler <gbsadler1@lcisp.com>
Cc: nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/4025: Bootstrap fails to create jv-convert (undefined refs)
Date: 15 Aug 2001 12:44:22 +0200
Gordon Sadler <gbsadler1@lcisp.com> writes:
| > > export CXXFLAGS='-Os -march=i686 -fno-implicit-templates'
| > > export OPTIMIZE_CXXFLAGS='-g -Os -march=athlon -fno-implicit-templates'
| >
| > It is not safe to use -fno-implicit-templates in CXXFLAGS. Would you
| > try again without those flags, please?
| >
| That does indeed correct the problem. Strange, it was/is still working
| on mainline and worked until Friday on the branch.
|
| Perhaps there should be a configure test to detect/warn about the use of
| the switch? At the least on the libstdc++/documentation/configopts
| website?
We went though this sometime ago -- -fno-implicit-templates should not
be used unless there is very specific reasons to do so; but then you
have a global idea of what is going on.
Yes, it is probably a good idea to add some text to that effect on our
documentation.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com
next reply other threads:[~2001-08-15 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 3:46 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 21:26 Gordon Sadler
2001-08-14 17:36 gbsadler1
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=20010815104605.19504.qmail@sourceware.cygnus.com \
--to=gdr@codesourcery.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).