This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Adding zlib to GCC
On Tue, Aug 29, 2000 at 11:16:09AM -0300, Alexandre Oliva wrote:
> On Aug 29, 2000, Marc Espie <espie@quatramaran.ens.fr> wrote:
> > If there is a common repository, I don't really see agreement as to
> > synch'ed releases between these.
> There's no need for synchronization. GDB and binutils, for example,
> that have large common parts and live in the same CVS repo, are not
> released at the same time. At some point, the maintainers of each
> separate project decides it's time to create a branch for a release,
> stabilizes it and releases it. Meanwhile, all other projects proceed
> their development in the trunk.
And when you happen to need several of those projects, you end up grabbing
distinct config.guess, bfd, libiberty, possibly zlib, gettext, texinfo,
and what not.
Waste of space. Waste of compile time. Hard to solve problems, like you find
a bug in ONE libiberty, find out it's been fixed in (say) binutils, try
importing the binutils version, and discover that gcc does not like the
new version because hashtab.c changed its interface completely in the
meantime...
`No need for synchronisation' is a vast oversimplification. It assumes those
projects are independant. The existence of libiberty, gettext, bfd, texinfo,
zlib... is proving this to be false (and I'm probably forgetting a few
pieces). And things don't even work as `you need version >=x.y of component
foo to build bar', because zob -release does not work with version x.y of
component foo.