From: Jeffrey A Law <law@redhat.com>
To: "Tim Prince" <tprince@computer.org>
Cc: "Bryce McKinlay" <bryce@albatross.co.nz>, gcc@gcc.gnu.org
Subject: Re: gcc snapshots -vs- java libraries
Date: Wed, 13 Dec 2000 21:05:00 -0000 [thread overview]
Message-ID: <20994.976770462@upchuck> (raw)
In-Reply-To: <00b601c06587$ec5e7ea0$9865fea9@intel9txl52pzr>
In message < 00b601c06587$ec5e7ea0$9865fea9@intel9txl52pzr >you write:
> Is the build of libgcj intended to be mandatory regardless of whether
> java is built? Likewise, for libstdc++-v3 without c++? I'd prefer to
> be able to build languages one at a time and test just the ones which
> are building successfully.
libgcj should only be built if we are building the java compiler too.
libstdc++ should work the same way.
jeff
next prev parent reply other threads:[~2000-12-13 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 14:53 Bryce McKinlay
2000-12-13 14:58 ` Jeffrey A Law
2000-12-13 20:40 ` Tim Prince
2000-12-13 20:59 ` Gabriel Dos Reis
2000-12-13 21:05 ` Jeffrey A Law [this message]
2000-12-14 7:36 ` Gerald Pfeifer
2000-12-14 8:59 Mike Stump
2001-01-02 21:51 ` Jeffrey A Law
2001-01-03 10:15 Mike Stump
2001-01-15 23:44 ` Bryce McKinlay
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=20994.976770462@upchuck \
--to=law@redhat.com \
--cc=bryce@albatross.co.nz \
--cc=gcc@gcc.gnu.org \
--cc=tprince@computer.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).