From: DJ Delorie <dj@redhat.com>
To: neroden@doctormoo.dyndns.org
Cc: gcc@gcc.gnu.org, neroden@twcny.rr.com
Subject: Re: autoconfiscating top level directory -- info wanted
Date: Thu, 03 Jan 2002 11:13:00 -0000 [thread overview]
Message-ID: <200201031913.g03JDpn17234@greed.delorie.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0201030821210.29366-100000@nerodeguest> (message from Nathanael Nerode on Thu, 3 Jan 2002 08:22:40 -0500 (EST))
> * I'd love to know what subdirectories still exist which are configured
> using this toplevel script.
The correct procedure would be to autoconfiscate all the
subdirectories before the top directory. The only two
repositories you need to worry about IMHO are gcc and src.
GCC you know about. For src, you need this:
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src login
{enter "anoncvs" as the password}
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src co .
See also http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/?cvsroot=src
The directories you need to worry about are the ones with configure.in
but no configure. The only one I could find was the utils/
subdirectory.
I stronly suggest you test each autoconfiscation with a native, cross,
canadian, and host-x-host build. Yes, this is time consuming, but
build bugs are usually quite subtle.
next prev parent reply other threads:[~2002-01-03 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 5:22 Nathanael Nerode
2002-01-03 11:13 ` DJ Delorie [this message]
[not found] ` <3C34AE17.4090701@twcny.rr.com>
2002-01-03 11:58 ` DJ Delorie
2002-01-03 11:28 ` Phil Edwards
2002-01-03 11:47 ` Zack Weinberg
2002-01-03 12:34 ` Tom Tromey
2002-01-25 14:49 Nathanael Nerode
2002-01-27 23:50 ` DJ Delorie
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=200201031913.g03JDpn17234@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@doctormoo.dyndns.org \
--cc=neroden@twcny.rr.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).