On 11/26/2010 06:39 AM, Stefano Lattarini wrote:
On Wednesday 24 November 2010, xufeng zhang wrote:
Hi,
I want to modify m4/tar.m4 in automake-1.11.1, however, after I made the
change, build automake failed, here is the build error:
-------------------------------------------------------
Compiling: automake
-------------------------------------------------------
CDPATH="${ZSH_VERSION+.}:"&& cd .&&
perllibdir="/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/lib:./lib"
"/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/aclocal"
--acdir=m4 -I m4
/bin/sh:
/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/aclocal:
No such file or directory
Makefile:337: *** [aclocal.m4] Error 127
Could you please show the *exact* sequence of commands that caused
this error? Also, are you building from an automake tarball, or
from a cloned git repository?
Hi Stefano,
Thanks very much for your reply.
This problem has troubled me about two weeks, some info has been
provided as you required.
Here is my reproduce steps:
1. I download automake source: automake-1.11.1-1.fc12.src.rpm and unpack it.
2. Here is the origin time stamp of tar.m4:
\> ls -l tar.m4
-rw-r--r-- 1 seaspray seaspray 3103 2009-12-04 08:38 tar.m4
Then I patch the tar.m4:
\> patch -p1 < tar-m4.patch
And here is the new time stamp of tar.m4 after patched:
\> ls -l tar.m4
-rw-r--r-- 1 seaspray seaspray 3224 2010-11-26 09:59 tar.m4
3. Next I configure automake:
\> ./configure
4. Last compile automake, and the error happens:
CDPATH="${ZSH_VERSION+.}:" && cd . &&
perllibdir="/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/lib:./lib"
"/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/aclocal"
--acdir=m4 -I m4
/bin/sh:
/home/xufeng/WindRiver/common_pc_automake/build-tools/automake-1.11.1/aclocal:
No such file or directory
make: *** [aclocal.m4] Error 127
5. However, If the change the time stamp of tar.m4 to origin:
\> touch -t 0912040838 tar.m4
Then run 'make' command can be successful and aclocal file is created.
I know it is caused by the timestamp mess up,
It's not a mess-up: automake's own aclocal.m4 uses the contents of tar.m4,
and so, when tar.m4 is modified, the automake build system wants to rebuild
aclocal.m4 too. That's absolutely correct.
Just based on the above reproduce steps, I think it's caused by time
stamp mess-up,
maybe it's not correct.
so I want to know if there is a way to do this?
Just a hunch: have you built the automake and aclocal scripts *before*
modifying tar.m4? If you haven't, well, you should build them first,
because the Automake build system uses the very automake and aclocal
scripts it ships, so you must be sure to build them before hacking any
other part of automake.
You can see I do nothing before modify tar.m4, I don't think it's
necessary for me to
do that.
Thanks,
Xufeng Zhang
Thanks,
Xufeng Zhang
HTH,
Stefano
