Re: Unable to build current CVS: coreutils.pot not built

[Paul Eggert]

Ed Avis <address@hidden> writes:

> shouldn't the configure script have a 'checking for gettext' stage?

When you check source out directly from CVS, you're assumed to be an
expert, and to have the correct build tools even if they're not on the
standard list of tools all users are assumed to have.  (The set of
"expert" tools includes CVS itself.  :-) The "checking for" stuff is
designed more for non-experts, who are assumed to have tarballs
instead of checking things out directly from CVS.

It would be nice if it'd be easier to get things directly from CVS and
that is on my list of things to help out with.