You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Michael Armbrust (Created) (JIRA)" <ji...@apache.org> on 2011/10/14 02:10:11 UTC
[jira] [Created] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
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
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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142668#comment-13142668 ]
jiraposter@reviews.apache.org commented on MESOS-37:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2663/
-----------------------------------------------------------
(Updated 2011-11-02 23:16:55.919606)
Review request for mesos.
Summary (updated)
-------
Currently, tests/process_spawn.cpp uses INT_MAX but only includes <iostreambq. which is not gaurenteed (and apparently does not on some systems) to define INT_MAX, causing a compilation error.
This addresses bug MESOS-37.
https://issues.apache.org/jira/browse/MESOS-37
Diffs
-----
src/tests/process_spawn.cpp 4f60296
Diff: https://reviews.apache.org/r/2663/diff
Testing
-------
Thanks,
Charles
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Benjamin Hindman (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127978#comment-13127978 ]
Benjamin Hindman commented on MESOS-37:
---------------------------------------
Hmm, accessing the VM directly might make the most sense. Feel free to contact me directly so we can set that up. Thanks Michael.
> 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
>
> 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
[jira] [Resolved] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Andy Konwinski (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Konwinski resolved MESOS-37.
---------------------------------
Resolution: Fixed
Assignee: Ed Kohlwey
I just committed this. Thanks Ed Kohlwey and Charles Reiss for contributing this patch!
> 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
> Assignee: Ed Kohlwey
> Priority: Blocker
> Attachments: 0001-include-limits.h-in-process_spawn-to-fix-compilati.patch, 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137659#comment-13137659 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
Andy, see: https://issues.apache.org/jira/browse/MESOS-39
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149882#comment-13149882 ]
jiraposter@reviews.apache.org commented on MESOS-37:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2663/#review3222
-----------------------------------------------------------
src/tests/process_spawn.cpp
<https://reviews.apache.org/r/2663/#comment7174>
For posterity: we've tried to keep the ordering consistent in the code base.
C headers
C++ headers
Project headers (i.e., those that use "" instead of <>).
- Benjamin
On 2011-11-02 23:16:55, Charles Reiss wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2663/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-02 23:16:55)
bq.
bq.
bq. Review request for mesos.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Currently, tests/process_spawn.cpp uses INT_MAX but only includes <iostream> which is not gaurenteed (and apparently does not on some systems) to define INT_MAX, causing a compilation error.
bq.
bq.
bq. This addresses bug MESOS-37.
bq. https://issues.apache.org/jira/browse/MESOS-37
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. src/tests/process_spawn.cpp 4f60296
bq.
bq. Diff: https://reviews.apache.org/r/2663/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Charles
bq.
bq.
> 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
> Assignee: Ed Kohlwey
> Priority: Blocker
> Attachments: 0001-include-limits.h-in-process_spawn-to-fix-compilati.patch, 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Benjamin Hindman (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127704#comment-13127704 ]
Benjamin Hindman commented on MESOS-37:
---------------------------------------
This is great, but are you sure this is the thread that was segfaulting? There are probably a couple dozen threads, so posting all of their backtraces might not be a good use of your time, but can you hunt around a bit and see if anything pops up?
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Andy Konwinski (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137477#comment-13137477 ]
Andy Konwinski commented on MESOS-37:
-------------------------------------
Michael, I think you mentioned the other day that you figured out the reason the JVM was seg faulting, right? Can we document that here?
> 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
>
> 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
[jira] [Updated] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Andy Konwinski (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Konwinski updated MESOS-37:
--------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Benjamin Hindman (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127277#comment-13127277 ]
Benjamin Hindman commented on MESOS-37:
---------------------------------------
Can you provide a backtrace of the segfault? Thanks!
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127184#comment-13127184 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
Its unclear to me if this is related to the bugs above, but I'm also getting the following JVM segfault when trying to launch a framework:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc2e87701d0, pid=1246, tid=140475092670208
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x4f31d0] unsigned+0xd0
#
# An error report file with more information is saved as:
# /home/ubuntu/hs_err_pid1246.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
//home/ubuntu/jrun: line 5: 1246 Aborted $JAVA $CLASSPATH $MESOS $@
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142669#comment-13142669 ]
jiraposter@reviews.apache.org commented on MESOS-37:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2663/
-----------------------------------------------------------
(Updated 2011-11-02 23:16:39.597586)
Review request for mesos.
Changes
-------
Also add <cstdio> (needed for Ubuntu according to MESOS-37 reporter) and <unistd.h>.
This problem suggests we should run include-what-you-use over the Mesos codebase in the future.
Summary
-------
Currently, tests/process_spawn.cpp uses INT_MAX but only includes <iostreambq. which is not gaurenteed (and apparently does not on some systems) to define INT_MAX, causing a compilation error.
This addresses bug MESOS-37.
https://issues.apache.org/jira/browse/MESOS-37
Diffs (updated)
-----
src/tests/process_spawn.cpp 4f60296
Diff: https://reviews.apache.org/r/2663/diff
Testing
-------
Thanks,
Charles
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138905#comment-13138905 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
Segfaults were a separate issues which has been solved.
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147552#comment-13147552 ]
jiraposter@reviews.apache.org commented on MESOS-37:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2663/#review3152
-----------------------------------------------------------
Ship it!
Looks great, thanks Charles!
- Andy
On 2011-11-02 23:16:55, Charles Reiss wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2663/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-02 23:16:55)
bq.
bq.
bq. Review request for mesos.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Currently, tests/process_spawn.cpp uses INT_MAX but only includes <iostream> which is not gaurenteed (and apparently does not on some systems) to define INT_MAX, causing a compilation error.
bq.
bq.
bq. This addresses bug MESOS-37.
bq. https://issues.apache.org/jira/browse/MESOS-37
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. src/tests/process_spawn.cpp 4f60296
bq.
bq. Diff: https://reviews.apache.org/r/2663/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Charles
bq.
bq.
> 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
> Priority: Blocker
> Attachments: 0001-include-limits.h-in-process_spawn-to-fix-compilati.patch, 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127163#comment-13127163 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
After commenting out that test in the makefile I then get the following error:
Installed /usr/local/mesos/lib/python/mesos-1.0-py2.6-linux-x86_64.egg
Processing dependencies for mesos==1.0
Finished processing dependencies for mesos==1.0
PYTHONPATH=third_party/distribute-0.6.19/distribute-0.6.19-py2.6.egg:/usr/local/mesos/lib/python python2.6 -m easy_install --install-dir /usr/local/mesos/lib/python ./third_party/protobuf-2.3.0/python/dist/*.egg
error: Not a URL, existing file, or requirement spec: './third_party/protobuf-2.3.0/python/dist/*.egg'
make: *** [install] Error 1
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127296#comment-13127296 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff67aa700 (LWP 1431)]
0x00007ffff6f211d0 in jni_GetObjectClass () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
(gdb) bt
#0 0x00007ffff6f211d0 in jni_GetObjectClass () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#1 0x00007ffff0c2c878 in JNIEnv_::GetObjectClass (env=0x401149d0, jobj=0x7ffff7ff7000) at /usr/lib/jvm/java-6-sun/include/jni.h:868
#2 construct<mesos::ExecutorInfo> (env=0x401149d0, jobj=0x7ffff7ff7000) at java/jni/construct.cpp:298
#3 0x00007ffff0c2fc17 in Java_org_apache_mesos_MesosSchedulerDriver_initialize (env=0x401149d0, thiz=0x7ffff67a8e20) at java/jni/org_apache_mesos_MesosSchedulerDriver.cpp:463
#4 0x00007ffff2925d6e in ?? ()
#5 0x0000000040114800 in ?? ()
#6 0x00000000828081a0 in ?? ()
#7 0x00007ffff67a8dc0 in ?? ()
#8 0x00000000832e69b8 in ?? ()
#9 0x00007ffff67a8e20 in ?? ()
#10 0x00000000832e7050 in ?? ()
#11 0x0000000000000000 in ?? ()
> 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
>
> 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
[jira] [Commented] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Michael Armbrust (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127819#comment-13127819 ]
Michael Armbrust commented on MESOS-37:
---------------------------------------
I'm not sure how to tell which one is seg faulting, but here are all the backtraces. Let me know if there is any other information you need. I can also give you access to the server causing the problem if that is helpful.
Starting program: /usr/bin/java -cp /mnt/deploylibFileCache/2cde75eb98198aaeebcbcc8e04e8b84c.jar:/mnt/deploylibFileCache/c67767fd12a3eb91c68c38ad5493858b.jar:/mnt/deploylibFileCache/823d2ad0a83a101aa4d74286bf3fb573.jar:/mnt/deploylibFileCache/fb34808c01d0da4d8eff558e145c4b6b.jar:/mnt/deploylibFileCache/4e0a7288be46ede8dc54b105350dc4c1.jar:/mnt/deploylibFileCache/9132591ba3b1ba9c89781f7a5a5f1d45.jar:/mnt/deploylibFileCache/78a49ecb566915e886646a94ba4d43bb.jar:/mnt/deploylibFileCache/6a74994ebc053692aa022233eaeae692.jar:/mnt/deploylibFileCache/5fd891a7365655c202e7204ba4cb8024.jar:/mnt/deploylibFileCache/b03d4c6ff4cedcd731d6a6d1a3149f65.jar:/mnt/deploylibFileCache/09901cb3c61a2a630457e377b5780c14.jar:/mnt/deploylibFileCache/4d4609998fbc124ce6f0d1d48fca2614.jar:/mnt/deploylibFileCache/8ae38e87cd4f86059c0294a8fe3e0b18.jar:/mnt/deploylibFileCache/c358a58492a9c7933454179704296d96.jar:/mnt/deploylibFileCache/70dfba19642b172d5ac5f6271d8243a0.jar:/mnt/deploylibFileCache/4a1e41354de6311793cd8bcb035eb748.jar:/mnt/deploylibFileCache/46235c960277206f00fe24714437bc89.jar:/mnt/deploylibFileCache/3499eb7c432b206b2057a07eeb4e1a73.jar:/mnt/deploylibFileCache/5293de57274ebf0d7f288c5bb1b77329.jar:/mnt/deploylibFileCache/b6512df13345e27a4fc6865b177125e9.jar:/mnt/deploylibFileCache/e3060bebfe449abeb277e77c4c3388cb.jar:/mnt/deploylibFileCache/dd2fca03bb4f80374aff97e5d0b21d3c.jar:/mnt/deploylibFileCache/bff6016da57e19fb736d0f5742ce60ac.jar:/mnt/deploylibFileCache/9581f652c5305d94fb480b43ba48667b.jar:/mnt/deploylibFileCache/12b65438bbaf225102d0396c21236052.jar:/mnt/deploylibFileCache/450fedce4f7f8ad3761577b10a664200.jar:/mnt/deploylibFileCache/083898d794cc261853922ca941aee390.jar:/mnt/deploylibFileCache/b81a1e68e5751e6135b9dc1609b8cd20.jar:/mnt/deploylibFileCache/3692dd72f8367cb35fb6280dc2916725.jar:/mnt/deploylibFileCache/13bc641afd7fd95e09b260f69c1e4c91.jar:/mnt/deploylibFileCache/237a8e845441bad2e535c57d985c8204.jar:/mnt/deploylibFileCache/6f35a1b03d4b70487a480a56ab0b6120.jar:/mnt/deploylibFileCache/2c9b4374cfe3f65ff1c4b39311f1f4cc.jar:/mnt/deploylibFileCache/c4ed69f32b735bd9bc4cac8bcbbcd879.jar:/mnt/deploylibFileCache/9534ce6506dc96bac3944423d804be30.jar:/mnt/deploylibFileCache/7d18b63063580284c3f5734081fdc99f.jar:/mnt/deploylibFileCache/333139fffc6c9d4bc3d2495d9613f092.jar:/mnt/deploylibFileCache/99fc0f610ce6a703f9074544c17952e3.jar:/mnt/deploylibFileCache/ed448347fc0104034aa14c8189bf37de.jar:/mnt/deploylibFileCache/8ad8c9229ef2d59ab9f59f7050e846a5.jar:/mnt/deploylibFileCache/8e149c1053741c03736a52df83974dcc.jar:/mnt/deploylibFileCache/c06b8a2b9159eb30feb363487f785c12.jar:/mnt/deploylibFileCache/f30453ae9ee252c802d349009742065f.jar:/mnt/deploylibFileCache/7d436a53c64490bee564c576babb36b4.jar:/mnt/deploylibFileCache/d898fe406a32b5c55283c719cb48328b.jar:/mnt/deploylibFileCache/4374238076ab08e60e0d296234480837.jar:/mnt/deploylibFileCache/f170ab1887bf86b5eda9f4f662b5c3ad.jar:/mnt/deploylibFileCache/777885be4974155fb26fb68e68c2d8a5.jar:/mnt/deploylibFileCache/35cf279e0fae25ab5f7ce91de997c31e.jar -Djava.library.path=/usr/local/mesos/lib/java deploylib.mesos.ServiceSchedulerDaemon --mesosMaster x --zooKeeperAddress x
[Thread debugging using libthread_db enabled]
process 1176 is executing new program: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/bin/java
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff67aa700 (LWP 1179)]
[New Thread 0x7ffff227c700 (LWP 1180)]
[New Thread 0x7ffff217b700 (LWP 1181)]
[New Thread 0x7ffff1b83700 (LWP 1182)]
[New Thread 0x7ffff1a82700 (LWP 1183)]
[New Thread 0x7ffff1981700 (LWP 1184)]
[New Thread 0x7ffff1841700 (LWP 1185)]
[New Thread 0x7ffff1740700 (LWP 1186)]
[New Thread 0x7ffff163f700 (LWP 1187)]
[New Thread 0x7ffff153e700 (LWP 1188)]
[New Thread 0x7ffff143d700 (LWP 1189)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff67aa700 (LWP 1179)]
0x00007ffff6f211d0 in jni_GetObjectClass () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
(gdb) thread apply all bt
Thread 12 (Thread 0x7ffff143d700 (LWP 1189)):
#0 0x00007ffff7bcbbc9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e256 in os::PlatformEvent::park(long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff72460ab in WatcherThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#5 0x00007ffff771f70d in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 11 (Thread 0x7ffff153e700 (LWP 1188)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fae5 in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff71102ae in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff70afdf2 in LowMemoryDetector::low_memory_detector_thread_entry(JavaThread*, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff72470f1 in JavaThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#8 0x00007ffff771f70d in clone () from /lib/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 10 (Thread 0x7ffff163f700 (LWP 1187)):
---Type <return> to continue, or q <return> to quit---
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fae5 in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff711014d in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6dd3eff in CompileQueue::get() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff6dd5d31 in CompileBroker::compiler_thread_loop() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff724dbe9 in compiler_thread_entry(JavaThread*, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff72470f1 in JavaThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#8 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#9 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#10 0x00007ffff771f70d in clone () from /lib/libc.so.6
#11 0x0000000000000000 in ?? ()
Thread 9 (Thread 0x7ffff1740700 (LWP 1186)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fae5 in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff711014d in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6dd3eff in CompileQueue::get() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff6dd5d31 in CompileBroker::compiler_thread_loop() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff724dbe9 in compiler_thread_entry(JavaThread*, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff72470f1 in JavaThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#8 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#9 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#10 0x00007ffff771f70d in clone () from /lib/libc.so.6
#11 0x0000000000000000 in ?? ()
Thread 8 (Thread 0x7ffff1841700 (LWP 1185)):
#0 0x00007ffff7bcdb50 in sem_wait () from /lib/libpthread.so.0
#1 0x00007ffff713eea5 in check_pending_signals(bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff713745c in signal_thread_entry(JavaThread*, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff72470f1 in JavaThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#6 0x00007ffff771f70d in clone () from /lib/libc.so.6
#7 0x0000000000000000 in ?? ()
Thread 7 (Thread 0x7ffff1981700 (LWP 1184)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff712f18a in ObjectMonitor::wait(long, bool, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff7214243 in ObjectSynchronizer::wait(Handle, long, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6f7a497 in JVM_MonitorWait () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff2925d6e in ?? ()
#6 0x0000000040177dc0 in ?? ()
#7 0x0000000040178198 in ?? ()
#8 0x0000000040177800 in ?? ()
#9 0x00007fff000000b6 in ?? ()
#10 0x00007ffff1980700 in ?? ()
#11 0x0000000000000000 in ?? ()
Thread 6 (Thread 0x7ffff1a82700 (LWP 1183)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff712f18a in ObjectMonitor::wait(long, bool, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff7214243 in ObjectSynchronizer::wait(Handle, long, Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6f7a497 in JVM_MonitorWait () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff2925d6e in ?? ()
#6 0x0000000040175b90 in ?? ()
#7 0x0000000040175f68 in ?? ()
#8 0x0000000040175000 in ?? ()
#9 0x00007ffff1a817e8 in ?? ()
#10 0x0000000082808998 in ?? ()
#11 0x00007ffff1a81858 in ?? ()
#12 0x00000000828a84e8 in ?? ()
#13 0x0000000000000000 in ?? ()
Thread 5 (Thread 0x7ffff1b83700 (LWP 1182)):
#0 0x00007ffff7bcbbc9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e256 in os::PlatformEvent::park(long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fc1b in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff71102ae in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff729af63 in VMThread::loop() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff729ab5e in VMThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#8 0x00007ffff771f70d in clone () from /lib/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 4 (Thread 0x7ffff217b700 (LWP 1181)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fae5 in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff71102ae in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6e93ba5 in GCTaskManager::get_task(unsigned int) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff6e94eb3 in GCTaskThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#8 0x00007ffff771f70d in clone () from /lib/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 3 (Thread 0x7ffff227c700 (LWP 1180)):
#0 0x00007ffff7bcb85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff713e0fe in os::PlatformEvent::park() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#2 0x00007ffff710fae5 in Monitor::IWait(Thread*, long) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#3 0x00007ffff71102ae in Monitor::wait(bool, long, bool) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#4 0x00007ffff6e93ba5 in GCTaskManager::get_task(unsigned int) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#5 0x00007ffff6e94eb3 in GCTaskThread::run() () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#6 0x00007ffff713eadf in java_start(Thread*) () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#7 0x00007ffff7bc69ca in start_thread () from /lib/libpthread.so.0
#8 0x00007ffff771f70d in clone () from /lib/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7ffff67aa700 (LWP 1179)):
#0 0x00007ffff6f211d0 in jni_GetObjectClass () from /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server/libjvm.so
#1 0x00007ffff0c2b878 in JNIEnv_::GetObjectClass (env=0x401149d0, jobj=0x7ffff7ff7000) at /usr/lib/jvm/java-6-sun/include/jni.h:868
#2 construct<mesos::ExecutorInfo> (env=0x401149d0, jobj=0x7ffff7ff7000) at java/jni/construct.cpp:298
#3 0x00007ffff0c2ec17 in Java_org_apache_mesos_MesosSchedulerDriver_initialize (env=0x401149d0, thiz=0x7ffff67a8e20) at java/jni/org_apache_mesos_MesosSchedulerDriver.cpp:463
#4 0x00007ffff2925d6e in ?? ()
#5 0x0000000040114800 in ?? ()
#6 0x00000000828081a0 in ?? ()
#7 0x00007ffff67a8dc0 in ?? ()
#8 0x00000000832e69e0 in ?? ()
#9 0x00007ffff67a8e20 in ?? ()
#10 0x00000000832e7078 in ?? ()
#11 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7ffff7ee8700 (LWP 1176)):
#0 0x00007ffff7bc803d in pthread_join () from /lib/libpthread.so.0
#1 0x000000004000591c in ContinueInNewThread ()
#2 0x0000000040001ef4 in main ()
> 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
>
> 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
[jira] [Updated] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Andy Konwinski (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Konwinski updated MESOS-37:
--------------------------------
Attachment: 0001-include-limits.h-in-process_spawn-to-fix-compilati.patch
Patch updated by Charles Reiss in https://reviews.apache.org/r/2663/
> 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
> Priority: Blocker
> Attachments: 0001-include-limits.h-in-process_spawn-to-fix-compilati.patch, 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
[jira] [Updated] (MESOS-37) Compilation broken on Ubuntu Lucid
(twitter branch)
Posted by "Ed Kohlwey (Updated) (JIRA)" <ji...@apache.org>.
[ 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