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 assume
Ed Avis <[EMAIL PROTECTED]> writes:
> when I check out of CVS, am I getting a
> slightly different code base from what goes into the tarballs?
Yes, you're getting a subset of the tarballs.
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.g
Ed Avis <[EMAIL PROTECTED]> 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 hav
On Sun, 9 May 2004, Andreas Schwab wrote:
>>I got a clean checkout, configured with './configure' and tried to
>>build with 'make'. The build fails with
>>
>>make coreutils.pot-update
>>make[4]: Entering directory `/home/ed/cvs_working/coreutils/po'
>>: --default-domain=coreutils --directory=.. \
On Sun, 9 May 2004, Andreas Schwab wrote:
I got a clean checkout, configured with './configure' and tried to
build with 'make'. The build fails with
make coreutils.pot-update
>>>You need to install gettext.
>>But shouldn't the configure script have a 'checking for gettext'
>>st
Ed Avis <[EMAIL PROTECTED]> writes:
> On Sun, 9 May 2004, Andreas Schwab wrote:
>
>>>I got a clean checkout, configured with './configure' and tried to
>>>build with 'make'. The build fails with
>>>
>>>make coreutils.pot-update
>>>make[4]: Entering directory `/home/ed/cvs_working/coreutils/po'
>>
Ed Avis <[EMAIL PROTECTED]> writes:
> (I hope this list is the right place to report bugs in current CVS.)
>
> I got a clean checkout, configured with './configure' and tried to
> build with 'make'. The build fails with
>
> make coreutils.pot-update
> make[4]: Entering directory `/home/ed/cvs_wor
(I hope this list is the right place to report bugs in current CVS.)
I got a clean checkout, configured with './configure' and tried to
build with 'make'. The build fails with
make coreutils.pot-update
make[4]: Entering directory `/home/ed/cvs_working/coreutils/po'
: --default-domain=coreutils -