bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#16530: Bootstrapping fails with missing "m4/cu-progs.m4"


From: Pádraig Brady
Subject: bug#16530: Bootstrapping fails with missing "m4/cu-progs.m4"
Date: Fri, 24 Jan 2014 02:05:39 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2

tag 16530 notabug
close 16530
stop

On 01/23/2014 06:22 PM, Assaf Gordon wrote:
> Follow-up:
> 
> On 01/23/2014 11:47 AM, Assaf Gordon wrote:
>>
>> Just tried to compile coreutils from scratch, and encountered the following
>> problem:
>> ===
>> $ git clone git://git.sv.gnu.org/coreutils
>> $ cd coreutils
>> $ ./bootstrap
> <...snip...>
>> /usr/bin/m4: m4_esyscmd subprocess failed
>> /usr/bin/m4:configure.ac:444: cannot open `m4/cu-progs.m4': No such file or
>> directory
>> autom4te: /usr/bin/m4 failed with exit status: 1
>> autopoint: *** Missing version: please specify in configure.ac through a
>> line 'AM_GNU_GETTEXT_VERSION(x.yy.zz)' the gettext version the package is
>> using
>> autopoint: *** Stop.
>> ===
>>
> 
> Upgrading to autoconf version 2.69 and M4 version 1.4.17 solved this issue 
> (but note that "bootstrap" required autoconf>=2.59 and I had 2.65 installed).

coreutils bootstrap.conf actually has >= 2.64 specified.

Anyway using this documented method for getting specific versions:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=blob;f=README-prereq;hb=HEAD
I tried to reproduce with autoconf-2.65 and I couldn't.
Then I tried with m4-1.4.13 and still couldn't.
So my next guess is that it's an incompat between your newer
automake-1.14 and your autoconf-2.65.
Indeed when I went to build automake-1.14 it bailed
saying it needed autoconf 2.69 or higher.
So where did you get this automake-1.14?
I suspect it is bumping the autoconf version requirement up.

I'm closing this for now.

thanks,
Pádraig.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]