Subject: Re: Request for comment: moving texinfo build
To: NetBSD Userlevel Technical Discussion List <>
From: Todd Vierling <>
List: tech-userlevel
Date: 07/26/2000 14:58:17
On 26 Jul 2000, Nathan J. Williams wrote:

: a) Maintaining the gcc import in as close to "pristene" fastion as possible.
: b) Permitting cross-compiler builds from this gcc tree on arbitrary
:    host systems. [Is this the same goal as (a)? I'm not sure]
: c) Not having two copies of texinfo in the source tree.
: d) Permitting upgrades of texinfo independent of gcc.
: e) Building documentation with the compiler.

Yes, that's right.

On Wed, 26 Jul 2000, Greg A. Woods wrote:

: Ah, what texinfo is in src/gnu/dist/toolchain/texinfo?

3.12, as is in src/gnu/dist/texinfo.

: > 2. use src/gnu/dist/texinfo with hooks from toolchain
: >    (and remove src/gnu/dist/toolchain/texinfo)
: IMO iff you upgrade src/gnu/dist/texinfo to 4.0 then this is the best
: option of all.
: > 3. comment out building of the .info files in src/gnu/dist/toolchain/gcc/Make*
: >    (and remove src/gnu/dist/toolchain/texinfo)
: I for one wouldn't like this option very much....

The reason I don't like (2) is because that means you can't build the cross
toolchain simply by taking a copy of gnusrc/gnu/dist/toolchain and running
GNU `configure'.  This is one thing I've been begged to provide, so I
personally consider that a requirement.

: I was about to pull in 4.0 and send the changes in a PR because it is
: necessary to read the info files that come with the "current"
: pkgsrc/editors/emacs (i.e. 20.7).

This is a compelling argument not to fiddle with src/gnu/dist/texinfo, so
I'll scratch that.  However, as above, I'd really rather not add hooks to
the gcc build that would prevent use of toolchain as a unified build

Possibly I could keep the duplication in the tree, too.  It's ~5MB, but
that's subjectively paltry in comparison to the rest of `toolchain'.  It
still leaves the NetBSD-makefile build pointing at dist/texinfo, which can
be upgraded to 4.0 or thereabouts.

Based on that, I'm now left with a split of option 3:

3a. comment out building .info files for cross tools and delete

3b. just leave toolchain/texinfo and use it only in the cross compiler

-- Todd Vierling (