This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Should boehm-gc/config.guess be a copy of gcc/config.guess?
- From: Per Bothner <per at bothner dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Andreas Jaeger'" <aj at suse dot de>, rbrown64 at csc dot com dot au, hboehm at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, "'tromey at redhat dot com'" <tromey at redhat dot com>
- Date: Tue, 11 Dec 2001 15:04:57 -0800
- Subject: Re: Should boehm-gc/config.guess be a copy of gcc/config.guess?
- References: <40700B4C02ABD5119F000090278766443BEE18@hplex1.hpl.hp.com>
Boehm, Hans wrote:
> I'm not an expert in this stuff. It would be nice if the GC library could
> be built without the rest of gcc from the boehm-gc subdirectory. This seems
> to argue for a separate copy. On the other side, there's the obvious
> argument for a single copy. But that must be a standard issue that also
> applies to other pieces like libffi? Does it have a standard solution?
There should only be a single config.guess in the cvs repository.
You should still be able to build the GC library byt itself - the
boehm-gc/configure should be able to find the configure.guess in its
parent directory.
If you make a separate GC tar-file, then you need to make sure it
includes config.guess. The easiest and standard way is to make a
tar-file containing something like this:
boehm-gc-$VERSION: // top-level-directory
boehm-gc directory
configure.in, configure, Makefile.am, Makefile.in, config.guess and
maybe some other files as needed from the gcc root.
README // tweaked as you like, perhaps a pointer to boehm-gc/README.
This is admittedly not too elegenat. The layout derives from the
"integrated source tree" model, may seem rather strange by itself.
An alternative is to combine the top-levels.
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/