You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. ./configure
2. gmake
What is the expected output? What do you see instead?
the following error happens:
src/base/linux_syscall_support.h: In function `void* sys_mmap(void*,
size_t, int, int, int, __off64_t)':
src/base/linux_syscall_support.h:339: error: invalid conversion from `long
int' to `void*'
gmake: *** [libtcmalloc_minimal_la-malloc_hook.lo] Error 1
What version of the product are you using? On what operating system?
> ls -l ../google-perftools-0.8.tar.gz
-rw-r--r-- 1 user group 759810 Mar 27 15:33 ../google-perftools-0.8.tar.gz
> uname -a
Linux hostname 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64
x86_64 x86_64 GNU/Linux
Please provide any additional information below.
Original issue reported on code.google.com by cheser...@gmail.com on 27 Mar 2007 at 1:47
The text was updated successfully, but these errors were encountered:
Hi,
Today I reproduce the same problem.
Solution:
I take a patch from debian package. See the attachment. With the patch I was
able to
compile on RHEL4U4 x86_64.
Original comment by niki_nay...@yahoo.com on 12 Apr 2007 at 2:42
Yeah, there are definitely known problems with compiling on 64-bit systems.
We're
*that* close to a new release of perftools, which should fix this and many other
64-bit problems.
Original comment by csilv...@gmail.com on 12 Apr 2007 at 6:16
We've just released perftools 0.90, which has much improved 64-bit support.
I've
verified the new code builds in a wide variety of redhat/fedora systems (though
not
RHEL). I believe this issue is fixed. If the new perftools does not work for
you,
feel free to reopen this issue.
Original comment by csilv...@gmail.com on 16 Apr 2007 at 9:10
Original issue reported on code.google.com by
cheser...@gmail.com
on 27 Mar 2007 at 1:47The text was updated successfully, but these errors were encountered: