public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tim Prince" <tprince@computer.org>
To: <law@redhat.com>, "Bryce McKinlay" <bryce@albatross.co.nz>
Cc: <gcc@gcc.gnu.org>
Subject: Re: gcc snapshots -vs- java libraries
Date: Wed, 13 Dec 2000 20:40:00 -0000	[thread overview]
Message-ID: <00b601c06587$ec5e7ea0$9865fea9@intel9txl52pzr> (raw)
In-Reply-To: <8717.976748337@upchuck>

----- Original Message -----
From: "Jeffrey A Law" <law@redhat.com>
To: "Bryce McKinlay" <bryce@albatross.co.nz>
Cc: <gcc@gcc.gnu.org>
Sent: Wednesday, December 13, 2000 2:58 PM
Subject: Re: gcc snapshots -vs- java libraries


>
>   In message < 3A37FF5E.8041334D@albatross.co.nz >you write:
>   > It looks like the java libs are going into the gcc-core archive on
the
>   > snapshots page. Shouldn't zlib, fastjar, boehm-gc, libffi, and
libjava
>   > be put into the gcc-java archive instead?
> Yes.  The snapshot script needs some updates to account for the
> integration of libgcj stuff.
> jeff

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.

  reply	other threads:[~2000-12-13 20:40 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 [this message]
2000-12-13 20:59     ` Gabriel Dos Reis
2000-12-13 21:05     ` Jeffrey A Law
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='00b601c06587$ec5e7ea0$9865fea9@intel9txl52pzr' \
    --to=tprince@computer.org \
    --cc=bryce@albatross.co.nz \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).