[
https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042508#comment-16042508
]
vandita commented on MESOS-7634:
--------------------------------
Hi Vinod,
I had started building Mesos from the link given
https://github.com/vinodkone/mesos/tree/vinod/s390x.Cloned the branch
vinod/s390x.
Followed steps given here
https://github.com/linux-on-ibm-z/docs/wiki/Building-Apache-Mesos . On make
command the build initially failed @ 3rd party module of protobuf for no s390x
support. Added that support and the build went ahead. The build latter got
stuck @ 3rd party module of leveldb for no support of atomic operations.Added
that.Now the build is stuck @ zookeeper module with error src/mt_adaptor.c:487:
Error: Unrecognized opcode: `lock'.
Please let me know if there is something I have to do to get the build
successful. Moreover please tell me the branch of mesos I need to clone from
the above mentioned repository.
> OsTest.ChownNoAccess fails on s390x machines
> --------------------------------------------
>
> Key: MESOS-7634
> URL: https://issues.apache.org/jira/browse/MESOS-7634
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
>
> Running a custom branch of Mesos (with some fixes in docker build scripts for
> s390x) on s390x based CI machines throws the following error when running
> stout tests.
> {code}
> [ RUN ] OsTest.ChownNoAccess
> ../../../../3rdparty/stout/tests/os_tests.cpp:839: Failure
> Value of: os::chown(uid.get(), gid.get(), "one", true).isError()
> Actual: false
> Expected: true
> ../../../../3rdparty/stout/tests/os_tests.cpp:840: Failure
> Value of: os::chown(uid.get(), gid.get(), "one/two", true).isError()
> Actual: false
> {code}
> One can repro this by building Mesos from my custom branch here:
> https://github.com/vinodkone/mesos/tree/vinod/s390x
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
