This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: v850 branch status
- From: Geoff Keating <geoffk at geoffk dot org>
- To: "Martin M. Hunt" <hunt at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 02 Jul 2002 13:33:25 -0700
- Subject: Re: v850 branch status
- References: <200207012319.15245.hunt@redhat.com><200207021021.24730.hunt@redhat.com><or3cv2t0ho.fsf@free.redhat.lsd.ic.unicamp.br><mailman.1025637060.31634.gcc-local@ges.redhat.com>
"Martin M. Hunt" <hunt@redhat.com> writes:
> On Tuesday 02 July 2002 12:04 pm, Alexandre Oliva wrote:
> > On Jul 2, 2002, "Martin M. Hunt" <hunt@redhat.com> wrote:
> > > On Tuesday 02 July 2002 09:12 am, Alexandre Oliva wrote:
> > >> Status: RO
> > >> X-Status: G
> > >>
> > >> On Jul 2, 2002, "Martin M. Hunt" <hunt@redhat.com> wrote:
> > >> > I fixed a sanitization error in gcc. There is another gcc error that
> > >> > breaks the build and I haven't figured out how to fix it.
> > >>
> > >> I'm afraid you need a new version of texinfo.
> > >
> > > GCC requires a later version than the one checked into devo?
> >
> > Yup. And, guess what: the later version depends on autoconf 2.5x :-(
> >
> > I think Synk had merged some bits of net texinfo into devo (branch?)
> > to be able to build GCC. Synk, do I misremember?
>
> So what am I supposed to do here? We can't send the customers a toolchain
> that doesn't compile when they type "make". Perhaps we disable building the
> docs?
I don't think you can disable building the docs, customers usually
prefer releases that come with documentation.
You'll have to fix the problem. Upgrade texinfo in devo to the
version that net gcc requires. If that means we have to have two
autoconf versions in maintainer-tools, then we have to do that. If
upgrading texinfo breaks other info files, fix them, and feed the
results back.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>