[
https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Kohlwey updated MESOS-37:
----------------------------
Attachment: MESOS-37.patch
Not sure about the segfaults, but I'm able to compile under the current head
(5a10b2ed7a5c31223a37f0044bdf9748cdf9b25d) on lucid with the fix from MESOS-50
and the attached patch which fixes some omitted header files in a test.
> Compilation broken on Ubuntu Lucid (twitter branch)
> ---------------------------------------------------
>
> Key: MESOS-37
> URL: https://issues.apache.org/jira/browse/MESOS-37
> Project: Mesos
> Issue Type: Bug
> Reporter: Michael Armbrust
> Attachments: MESOS-37.patch
>
>
> The first problem is as follows:
> WAR [20111013-16:53:27.595] deploylib: /bin/sh: pushd: not found
> WAR [20111013-16:53:27.595] deploylib: python2.6: can't open file 'setup.py':
> [Errno 2] No such file or directory
> WAR [20111013-16:53:27.595] deploylib: /bin/sh: popd: not found
> WAR [20111013-16:53:27.595] deploylib: make[1]: *** [../lib/python/mesos.py]
> Error 127
> WAR [20111013-16:53:27.595] deploylib: make: *** [src] Error 2
> WAR [20111013-16:53:27.595] deploylib: install: cannot stat
> `./bin/killtree.sh': No such file or directory
> WAR [20111013-16:53:27.595] deploylib: make: *** [install] Error 1
> I was able to work around this issue by running "rm /bin/sh; ln -s /bin/bash
> /bin/sh". However then I ran into this issue:
> g++ -o ../../bin/tests/process_spawn process_spawn.cpp
> process_spawn.cpp: In function 'void dummywait()':
> process_spawn.cpp:16: error: 'getchar' was not declared in this scope
> process_spawn.cpp:16: error: 'EOF' was not declared in this scope
> process_spawn.cpp:17: error: 'INT_MAX' was not declared in this scope
> make[2]: *** [../../bin/tests/process_spawn] Error 1
> make[2]: Leaving directory `/home/ubuntu/mesos/src/tests'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/ubuntu/mesos/src'
> make: *** [src] Error 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
