-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build error "msync not declared" on ubuntu trusty, when building on virtual box guest->host filesystem #1008
Comments
Missing symbols belong to glibc. I am unsure how they might be missing on your machine. I just tested building gperftools 2.7 in docker image of ubuntu 14.04 and everything works fine. |
I have the same error on Ubuntu 18.04.1 LTS. |
@alk - it does not seem to be an issue with glibc. This appears to be a problem with the autotools
to The configure script worked fine for me on older Ubuntu with older gperftools. |
Hm, no issues for me under docker. docker run -i -t ubuntu:trusty |
I also tried docker thing for 18.04. I need someone to attach config.log to try to figure out what happened. |
Fresh VM of ubuntu trusty also has no issues building gperftools 2.7. I need more details about your setup. |
ok - my tests are on Ubuntu 18.04 LTS Desktop... I'll try to capture a configure.log later this week. |
Also please attach output of dpkg -l in addition to config.log. In case it is some sort of packages combination. |
Here is a config.log of the issue. With gperftools 2.7 release. This was specifically a vanilla install of Ubuntu 18.04.1 LTS 64-bit on VirtualBox. Only |
error code 6 is failing of mmap of file that is smaller than mapping length. Can you also give output of /proc/mounts and echo $HOME ? I think we should still get rid of testing mmap, but I would like to understand what is happening here. |
Sure thing:
I guess it would seem reasonable to assume mmap is always there. |
Great. This explains "breakage". You're building from directory mounted via vboxsf. I guess it is virtual box thingy that propagates host FS to guest. And apparently it does so in broken, or at least unexpected way. I am not 100% sure about broken. autoconf code that checks for working mmap is arguably doing it wrong too. It creates files smaller than page size and tries to mmap entire first page. Apparently vboxfs doesn't like it. And I am not sure if it is correctly not liking it. Anyways, I'll get rid of mmap testing |
OK - totally get that @alk . |
This should alleviate vboxfs problems from issue #1008.
Merged a fix. |
I'm trying to compile gperftools-2.7 under ubuntu trusty. Under Vagrant on a mac. When I configure gperftools-2.7 it confirms libunwind is installed, which I installed first.
But make in gperftools-2.7 gives these errors:
src/heap-checker.cc: In static member function ‘static void HeapLeakChecker::IgnoreLiveObjectsLocked(const char*, const char*)’: src/heap-checker.cc:1436:52: error: ‘MS_ASYNC’ was not declared in this scope if (msync(const_cast<char*>(object), size, MS_ASYNC) != 0) { ^ src/heap-checker.cc:1436:60: error: ‘msync’ was not declared in this scope if (msync(const_cast<char*>(object), size, MS_ASYNC) != 0) {
Am I missing a pre-requisite here?
The text was updated successfully, but these errors were encountered: