search

qchbai / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

What is the proper way to build gperftools? #438

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I am getting two errors when building gperftools:

   No rule to make target 'src/google/tcmalloc.h', needed by 'all-am'.
   src/google/tcmalloc.h: No such file or directory
   src/tests/simple_compat_test.cc:62: error: `tc_new' was not declared in this scope

   configure.ac:93: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

Will either of these errors or warnings affect product functionality?
What is the proper way to build gperftools?

I'm using gperftools 2.0 on CentOS 4.

To build I am running ./configure and make

What specific information could I provide that would be most useful in helping 
to answer this question? I feel like "what steps will reproduce the problem?" 
is very open ended as there are countless variables that go into configure and 
make.

Original issue reported on code.google.com by Ocasta...@gmail.com on 25 Jun 2012 at 12:00

GoogleCodeExporter commented 9 years ago

Original comment by chapp...@gmail.com on 23 Dec 2012 at 3:17

GoogleCodeExporter commented 9 years ago 
Interesting. Is that really on CentOS 4? Somebody still cares about that?

Original comment by alkondratenko on 10 Mar 2013 at 3:55

GoogleCodeExporter commented 9 years ago 
I might be wrong, but since it is RHEL4 I'd guess it might be some 
issue/bug/unsupported feature from the build environment. RHEL4 uses ancient 
build tools and from my point of view we should state minimum supported 
versions for gperftools releases.

Original comment by zatr...@gmail.com on 10 Mar 2013 at 9:53

GoogleCodeExporter commented 9 years ago 
Yes RHEL is quite old at this point. Unless you are willing to dig in and 
figure this out it isn't likely that we are going to spend any time looking 
into this. There are probably some #ifdef guards at play here. The configure.ac 
warning is fixed in current trunk.

Original comment by chapp...@gmail.com on 11 Mar 2013 at 12:14

GoogleCodeExporter commented 9 years ago 
Re-check with latest release. I've tested myself on centos 4.8 or 4.9.

Original comment by alkondratenko on 14 Sep 2013 at 8:32