From: Daniel Jacobowitz <drow@mvista.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Andrew Haley <aph@redhat.com>, Andreas Jaeger <aj@suse.de>,
gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: Java/parellel build(?) related bootstrap failure
Date: Wed, 02 Apr 2003 00:13:00 -0000 [thread overview]
Message-ID: <20030401233819.GA15125@nevyn.them.org> (raw)
In-Reply-To: <Pine.BSF.4.53.0304020052260.84822@acrux.dbai.tuwien.ac.at>
On Wed, Apr 02, 2003 at 12:54:00AM +0200, Gerald Pfeifer wrote:
> On Mon, 31 Mar 2003, Andrew Haley wrote:
> > You perhaps need a module that checks out an approopriate subset of
> > gcc. It should be quite easy to create one.
>
> Thanks for the hint. Unfortunately, modules don't work nicely with
> `cvs update` (one of the design bugs of CVS, that it after checkout,
> it simpley ignores modules).
>
> In case someone else has a similar problem, here is what I wound up
> using now:
>
> cvs -q $CVS_EXT update -Pd -I\! -I CVS libjava \
> && cvs -q $CVS_EXT update -P -I\! -I CVS
> if [ ! $? ]; then
> echo "Error updating. Build aborted."
> exit 1
> fi
> contrib/gcc_update --touch
I generally just use checkout again:
ln -s . gcc
cvs co gcc-core gcc-java (or whatever)
rm -f gcc
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-01 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 15:44 Gerald Pfeifer
2003-03-29 17:16 ` Andreas Jaeger
2003-03-30 22:02 ` Andreas Jaeger
2003-03-31 7:47 ` Gerald Pfeifer
2003-03-31 8:38 ` Andrew Haley
2003-04-01 23:38 ` Gerald Pfeifer
2003-04-01 23:44 ` Gerald Pfeifer
2003-04-02 0:13 ` Daniel Jacobowitz [this message]
2003-04-02 12:06 ` Andrew Haley
2003-03-30 7:36 ` Tom Tromey
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=20030401233819.GA15125@nevyn.them.org \
--to=drow@mvista.com \
--cc=aj@suse.de \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).