[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unable to build current CVS: coreutils.pot not built
From: |
Ed Avis |
Subject: |
Re: Unable to build current CVS: coreutils.pot not built |
Date: |
Mon, 10 May 2004 20:22:37 +0100 (BST) |
On Mon, 10 May 2004, Paul Eggert wrote:
>>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.
That makes perfect sense. So when I check out of CVS, am I getting a
slightly different code base from what goes into the tarballs?
--
Ed Avis <address@hidden>