niuys / gperftools

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

Compilation errors while compiling a C++ file that includes google/heap-checker.h #186

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Write C++ code that #includes <google/heap-checker.h>
2. The compiler would produce errors about a missing config.h
3. It seems to be genuine error - in all the files that get installed by
doing a 'make install', config.h is not installed.

What is the expected output? What do you see instead?

The expectation is that the code should compile. It doesn't.

What version of the product are you using? On what operating system?

Version 1.4. Ubuntu 9.10 running on x86_64 platform.

Please provide any additional information below.

Original issue reported on code.google.com by mohit.a...@gmail.com on 6 Nov 2009 at 3:22

GoogleCodeExporter commented 9 years ago
Doh!  So it is.  I've removed config.h for the next release.  I guess not many 
people
use this header file...

If you want to fix this up before the next release, remove the config.h line, 
and
also the #ifdef around #include <stdint.h> (keep the #include line though).

I want to do more testing about how portable stdint.h actually is, before 
pushing
this fix more widely.  I'm hoping it's portable enough I can just blindly 
include it,
and not have to use autotools nonsense to fix up the file at compile time.

Original comment by csilv...@gmail.com on 6 Nov 2009 at 5:40

GoogleCodeExporter commented 9 years ago
I did something slightly different. I changed the '#include "config.h"' in heap-
checker.h to '#include <google/config.h' and copied the config.h that was 
produced 
while compiling the google-perftools-1.4 package to the appropriate location in 
the 
install directory. That worked for me. That way, I didn't have to mess with 
stdint.h 
either.

Thanks for the quick response.

Original comment by mohit.a...@gmail.com on 6 Nov 2009 at 5:54

GoogleCodeExporter commented 9 years ago
This should be fixed in perftools 1.5, just released.

Original comment by csilv...@gmail.com on 20 Jan 2010 at 11:09