You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Florian Leibert (flo) (JIRA)" <ji...@apache.org> on 2013/03/07 02:38:13 UTC
[jira] [Commented] (MESOS-381) Problem building on Ubuntu 12.04 LTE
[ https://issues.apache.org/jira/browse/MESOS-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595412#comment-13595412 ]
Florian Leibert (flo) commented on MESOS-381:
---------------------------------------------
Sorry for the premature post - I actually read through the INSTALL in the perftool libarary and installing "- libunwind7-dev" fixed it as well.
Still, I would make this the default option?
--Flo
> Problem building on Ubuntu 12.04 LTE
> ------------------------------------
>
> Key: MESOS-381
> URL: https://issues.apache.org/jira/browse/MESOS-381
> Project: Mesos
> Issue Type: Bug
> Reporter: Florian Leibert (flo)
> Assignee: Benjamin Mahler
> Priority: Blocker
>
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I./src -I./src -pthread -DNDEBUG -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -fno-builtin-malloc -fno-builtin-free -fno-builtin-realloc -fno-builtin-calloc -fno-builtin-cfree -fno-builtin-memalign -fno-builtin-posix_memalign -fno-builtin-valloc -fno-builtin-pvalloc -Wno-unused-result -DNO_FRAME_POINTER -fno-exceptions -g -O2 -MT libtcmalloc_internal_la-memory_region_map.lo -MD -MP -MF .deps/libtcmalloc_internal_la-memory_region_map.Tpo -c src/memory_region_map.cc -fPIC -DPIC -o libtcmalloc_internal_la-memory_region_map.o
> In file included from src/stacktrace.cc:57:0:
> src/stacktrace_config.h:58:5: error: #error Cannnot calculate stack trace: need either libunwind or frame-pointers (see INSTALL file)
> src/stacktrace.cc:109:3: error: #error Cannot calculate stack trace: will need to write for your environment
> make[6]: *** [stacktrace.lo] Error 1
> make[6]: *** Waiting for unfinished jobs....
> mv -f .deps/libtcmalloc_internal_la-maybe_threads.Tpo .deps/libtcmalloc_internal_la-maybe_threads.Plo
> mv -f .deps/libtcmalloc_internal_la-symbolize.Tpo .deps/libtcmalloc_internal_la-symbolize.Plo
> mv -f .deps/libtcmalloc_internal_la-raw_printer.Tpo .deps/libtcmalloc_internal_la-raw_printer.Plo
> mv -f .deps/libtcmalloc_internal_la-malloc_extension.Tpo .deps/libtcmalloc_internal_la-malloc_extension.Plo
> mv -f .deps/libtcmalloc_internal_la-low_level_alloc.Tpo .deps/libtcmalloc_internal_la-low_level_alloc.Plo
> mv -f .deps/libtcmalloc_internal_la-thread_cache.Tpo .deps/libtcmalloc_internal_la-thread_cache.Plo
> mv -f .deps/libtcmalloc_internal_la-heap-profiler.Tpo .deps/libtcmalloc_internal_la-heap-profiler.Plo
> mv -f .deps/libtcmalloc_internal_la-malloc_hook.Tpo .deps/libtcmalloc_internal_la-malloc_hook.Plo
> mv -f .deps/libtcmalloc_internal_la-memory_region_map.Tpo .deps/libtcmalloc_internal_la-memory_region_map.Plo
> mv -f .deps/libtcmalloc_internal_la-heap-profile-table.Tpo .deps/libtcmalloc_internal_la-heap-profile-table.Plo
> mv -f .deps/libtcmalloc_minimal_la-tcmalloc.Tpo .deps/libtcmalloc_minimal_la-tcmalloc.Plo
> mv -f .deps/libtcmalloc_la-heap-checker.Tpo .deps/libtcmalloc_la-heap-checker.Plo
> mv -f .deps/libtcmalloc_la-tcmalloc.Tpo .deps/libtcmalloc_la-tcmalloc.Plo
> mv -f .deps/libtcmalloc_minimal_debug_la-debugallocation.Tpo .deps/libtcmalloc_minimal_debug_la-debugallocation.Plo
> make[6]: Leaving directory `/srv/mesos/src/build/third_party/libprocess/third_party/gperftools-2.0'
> make[5]: *** [gperftools-2.0-build-stamp] Error 2
> make[5]: Leaving directory `/srv/mesos/src/build/third_party/libprocess/third_party'
> make[4]: *** [check] Error 2
> make[4]: Leaving directory `/srv/mesos/src/build/third_party/libprocess/third_party'
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory `/srv/mesos/src/build/third_party/libprocess'
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory `/srv/mesos/src/build/third_party'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/srv/mesos/src/build/third_party'
> make: *** [check-recursive] Error 1
> failed: /var/lib/cloud/instance/scripts/part-030 [2]
> Configuring postfix with hostname ip-10-148-145-49
> * Reloading Postfix configuration...
> ...done.
> rsyslog start/running, process 21673
> Reading package lists...
> Building dependency tree...
> Reading state information...
> runit is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
> * Starting Nginx Server...
> ...fail!
> 2013-03-07 01:15:48,595 - cc_scripts_user.py[WARNING]: failed to run-parts in /var/lib/cloud/instance/scripts
> 2013-03-07 01:15:50,539 - __init__.py[WARNING]: Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 117, in run_cc_modules
> cc.handle(name, run_args, freq=freq)
> File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py", line 78, in handle
> [name, self.cfg, self.cloud, cloudinit.log, args])
> File "/usr/lib/python2.7/dist-packages/cloudinit/__init__.py", line 326, in sem_and_run
> func(*args)
> File "/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_scripts_user.py", line 31, in handle
> util.runparts(runparts_path)
> File "/usr/lib/python2.7/dist-packages/cloudinit/util.py", line 223, in runparts
> raise RuntimeError('runparts: %i failures' % failed)
> RuntimeError: runparts: 3 failures
> 2013-03-07 01:15:50,540 - __init__.py[ERROR]:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira