Build fails when code has been passed through git

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On Ubuntu 9.10, unpackage the sources from the .tar.gz tarball, and check 
them into a new 
git repository:
cd <top level of google-perftools-1.5>
git init
git add .
git commit
2. Clone the git repository
cd ..
mkdir foo
cd foo
git clone ../../google-perftools-1.5
3. Try a build on this clone
cd google-perftools-1.5
./configure
make

What is the expected output? What do you see instead?
I expect the make to complete. Instead, the make fails with a lot of libtool 
failures.

What version of the product are you using? On what operating system?
google-perftools-1.5
Ubuntu 9.10 on x86

Please provide any additional information below.
Meld indicates the file contents are all identical. The only differences 
between the directory that 
builds and the one that doesn't that I can figure out are the mod dates on the 
files.

Original issue reported on code.google.com by bobertmu...@gmail.com on 3 Feb 2010 at 11:06

[GoogleCodeExporter]

My guess is that what is happening is that you are touching the timestamps, 
which
causes perftools to want to regenerate the autotools files (Makefile.in, etc). 
However, your version of autotools is different from mine, and they are 
incompatible
in some way.

The easiest way to fix this is to just touch Makefile.in, configure, ltmain.sh, 
and
any other auto-generated file you need to, so that autotools doesn't feel the 
need to
do anything.

Original comment by csilv...@gmail.com on 4 Feb 2010 at 12:08

• Changed state: NotABug
• Added labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Git's touching the timestamps, not me. :-) I'll take a look at it.

Original comment by bobertmu...@gmail.com on 4 Feb 2010 at 1:06