From: jwd@graphics.cornell.edu (James W. Durkin)
To: help-gcc@gnu.org
Subject: Building GCC/libraries to support "guiding declarations"
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <ren1rdmaxz.fsf@eyrie.graphics.cornell.edu> (raw)
Message-ID: <19991231222400.t-4EkM5VxLZgB1ZSjnjkhpnZqEUlXL0M_DJox7pYzPA@z> (raw)
Although this is a rather specific question, I guess it generalizes to
"How do you build new versions of the GCC libraries after successfully
building and installing the compiler, WITHOUT doing yet another `make
bootstrap'?"
According to the INFO pages documenting GCC's C++ compiler options, in
order to properly support the -fguiding-decls compiler flag, I need to
take into account the following:
"Like all options that change the ABI, all C++ code, *including
libgcc.a* must be built with the same setting of this option."
I guess this implies that I need to build new versions of the GCC
libraries that include any C++ code. Certainly libstdc++. And (I
guess) libgcc too. Now what's the best way to accomplish this?
Using GCC 2.95.2 and doing the configure/build in a directory outside
the source tree (as suggested by the latest installation
instructions), it would seems that overriding the compiler flags
(e.g., LIBCXXFLAGS) on the make invocation would do the trick. That
doesn't seem to work though -- the flags aren't propagated down into
the compilation of the library code (using GNU make 3.78.1).
Modifying the top-level makefile that is created by "configure" to set
these flags seems to fair better, but I'm not convinced that all the
necessary flags are getting set and passed down into the bowels of the
GCC build.
Does anyone have a suggestion/solution on how to build new versions of
these libraries with appropriate control of the compiler flags used on
the library's source code?
--
James Durkin
jwd@graphics.cornell.edu
next reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 14:17 James W. Durkin [this message]
1999-12-31 22:24 ` James W. Durkin
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=ren1rdmaxz.fsf@eyrie.graphics.cornell.edu \
--to=jwd@graphics.cornell.edu \
--cc=help-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).