[jira] [Created] (MESOS-8765) Add a check in cmake to validate linker
David Forsythe created MESOS-8765: - Summary: Add a check in cmake to validate linker Key: MESOS-8765 URL: https://issues.apache.org/jira/browse/MESOS-8765 Project: Mesos Issue Type: Task Reporter: David Forsythe On at least one platform, linking with GNU ld seems to fail. We should figure out why it's failing and add a check to cmake that validates a builds linker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8761) Default linker fails to link tests on FreeBSD
[
https://issues.apache.org/jira/browse/MESOS-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429170#comment-16429170
]
David Forsythe commented on MESOS-8761:
---
ld.bfd from binutils fails to link as well.
ld.gold works.
> Default linker fails to link tests on FreeBSD
> -
>
> Key: MESOS-8761
> URL: https://issues.apache.org/jira/browse/MESOS-8761
> Project: Mesos
> Issue Type: Bug
> Environment: FreeBSD 11.1
>Reporter: David Forsythe
>Assignee: David Forsythe
>Priority: Major
>
> When relying on the default linker:
>
> {code:java}
> [ 82%] Linking CXX executable ../mesos-tests
> cd /mesos-build/src/tests && /usr/local/bin/cmake -E cmake_link_script
> CMakeFiles/mesos-tests.dir/link.txt --verbose=1 /usr/bin/c++
> CMakeFiles/mesos-tests.dir/active_user_test_helper.cpp.o
> CMakeFiles/mesos-tests.dir/cluster.cpp.o CMakeFiles/mesos-tests.dir/container
> izer.cpp.o CMakeFiles/mesos-tests.dir/environment.cpp.o
> CMakeFiles/mesos-tests.dir/flags.cpp.o
> CMakeFiles/mesos-tests.dir/http_server_test_helper.cpp.o
> CMakeFiles/mesos-tests.dir/main.cpp.o CMakeFiles/mesos-tests.dir/mesos.cpp.o
> ...
> ../../3rdparty/leveldb-1.19/src/leveldb-1.19/out-static/libleveldb.a
> ../../3rdparty/googletest-1.8.0/src/googletest-1.8.0-build/googlemock/libgmock.a
>
> ../../3rdparty/googletest-1.8.0/src/googletest-1.8.0-build/googlemock/gtest/libgtest.a
> ../.libs/libload_qos_controller.so ../.libs/libfixed_resource_es timator.so
> ../.libs/liblogrotate_container_logger.so
> -Wl,-rpath-link,/mesos-build/3rdparty/libev-4.22/src/libev-4.22-build/lib
> CMakeFiles/mesos-tests.dir/api_tests.cpp.o: file not recognized: File format
> not recognized
> ...
> root@mesos0:/mesos-build # ld --version
> GNU ld 2.17.50 [FreeBSD] 2007-07-03
> {code}
> lld seems to work, and an updated gnu linker from binutils or gold may work
> as well.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8761) Default linker fails to link tests on FreeBSD
David Forsythe created MESOS-8761:
-
Summary: Default linker fails to link tests on FreeBSD
Key: MESOS-8761
URL: https://issues.apache.org/jira/browse/MESOS-8761
Project: Mesos
Issue Type: Task
Environment: FreeBSD 11.1
Reporter: David Forsythe
Assignee: David Forsythe
When relying on the default linker:
{code:java}
[ 82%] Linking CXX executable ../mesos-tests
cd /mesos-build/src/tests && /usr/local/bin/cmake -E cmake_link_script
CMakeFiles/mesos-tests.dir/link.txt --verbose=1 /usr/bin/c++
CMakeFiles/mesos-tests.dir/active_user_test_helper.cpp.o
CMakeFiles/mesos-tests.dir/cluster.cpp.o CMakeFiles/mesos-tests.dir/container
izer.cpp.o CMakeFiles/mesos-tests.dir/environment.cpp.o
CMakeFiles/mesos-tests.dir/flags.cpp.o
CMakeFiles/mesos-tests.dir/http_server_test_helper.cpp.o
CMakeFiles/mesos-tests.dir/main.cpp.o CMakeFiles/mesos-tests.dir/mesos.cpp.o
...
../../3rdparty/leveldb-1.19/src/leveldb-1.19/out-static/libleveldb.a
../../3rdparty/googletest-1.8.0/src/googletest-1.8.0-build/googlemock/libgmock.a
../../3rdparty/googletest-1.8.0/src/googletest-1.8.0-build/googlemock/gtest/libgtest.a
../.libs/libload_qos_controller.so ../.libs/libfixed_resource_es timator.so
../.libs/liblogrotate_container_logger.so
-Wl,-rpath-link,/mesos-build/3rdparty/libev-4.22/src/libev-4.22-build/lib
CMakeFiles/mesos-tests.dir/api_tests.cpp.o: file not recognized: File format
not recognized
...
root@mesos0:/mesos-build # ld --version
GNU ld 2.17.50 [FreeBSD] 2007-07-03
{code}
lld seems to work, and an updated gnu linker from binutils or may work as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8749) CSI proto is always included in the build when using CMake
David Forsythe created MESOS-8749:
-
Summary: CSI proto is always included in the build when using CMake
Key: MESOS-8749
URL: https://issues.apache.org/jira/browse/MESOS-8749
Project: Mesos
Issue Type: Task
Environment: FreeBSD 11.1-RELEASE
Reporter: David Forsythe
cmake ../mesos
make LDFLAGS='-lexecinfo -lm'
{code:java}
...
[ 36%] Building CXX object
src/CMakeFiles/mesos-protobufs.dir/__/include/csi/csi.pb.cc.o
cd /mesos-build/src && /usr/bin/c++ -DLIBDIR=\"/usr/local/libmesos\"
-DPKGDATADIR=\"/usr/local/share/mesos\"
-DPKGLIBEXECDIR=\"/usr/local/libexec/mesos\" -DVERSION=\"1.6.0\"
-Dmesos_protobufs_EXPORTS -I/mesos-build/include -I/mesos-build/include/mesos
-I/mesos-build/src -I/mesos/src -I/mesos-build/include/csi -isystem
/mesos-build/3rdparty/protobuf-3.5.0/src/protobuf-3.5.0/src -fPIC -Wall
-Wsign-compare -Wformat-security -fstack-protector-strong -std=c++11 -o
CMakeFiles/mesos-protobufs.dir/__/include/csi/csi.pb.cc.o -c
/mesos-build/include/csi/csi.pb.cc
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: expected member name or ';'
after declaration specifiers
::google::protobuf::uint32 major() const;
~~ ^
/usr/include/sys/types.h:372:20: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: expected ')'
/usr/include/sys/types.h:372:20: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
/mesos-build/include/csi/csi.pb.h:763:30: note: to match this '('
/usr/include/sys/types.h:372:19: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: expected ')'
::google::protobuf::uint32 major() const;
^
/usr/include/sys/types.h:372:37: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
/mesos-build/include/csi/csi.pb.h:763:30: note: to match this '('
/usr/include/sys/types.h:372:25: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: C++ requires a type specifier
for all declarations
::google::protobuf::uint32 major() const;
^
/usr/include/sys/types.h:372:27: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: function cannot return
function type 'int (())'
/usr/include/sys/types.h:372:26: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:763:30: error: expected ')'
/usr/include/sys/types.h:372:42: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
/mesos-build/include/csi/csi.pb.h:763:30: note: to match this '('
/usr/include/sys/types.h:372:24: note: expanded from macro 'major'
#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:769:30: error: expected member name or ';'
after declaration specifiers
::google::protobuf::uint32 minor() const;
~~ ^
/usr/include/sys/types.h:373:20: note: expanded from macro 'minor'
#define minor(x) ((int)((x)&0x00ff)) /* minor number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
/mesos-build/include/csi/csi.pb.h:769:30: error: expected ')'
/usr/include/sys/types.h:373:20: note: expanded from macro 'minor'
#define minor(x) ((int)((x)&0x00ff)) /* minor number */
^
/mesos-build/include/csi/csi.pb.h:769:30: note: to match this '('
/usr/include/sys/types.h:373:19: note: expanded from macro 'minor'
#define minor(x) ((int)((x)&0x00ff)) /* minor number */
^
In file included from /mesos-build/include/csi/csi.pb.cc:4:
[jira] [Updated] (MESOS-8114) DiskUsageCollectorTest.File fails on FreeBSD+ZFS
[ https://issues.apache.org/jira/browse/MESOS-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Forsythe updated MESOS-8114: -- Description: ../../mesos/src/tests/disk_quota_tests.cpp:95: Failure Expected: (usage.get()) >= (Kilobytes(8)), actual: 1KB vs 8KB On ZFS (with default settings), there is a large amount of time (~2s on my test machine) between the write and the time the size reported by du is what we're expecting. was: ../../mesos/src/tests/disk_quota_tests.cpp:95: Failure Expected: (usage.get()) >= (Kilobytes(8)), actual: 1KB vs 8KB On ZFS (with default settings), there is a large amount of time (~2s on my test machine) between the write and the time the metadata from du is what we're expecting. > DiskUsageCollectorTest.File fails on FreeBSD+ZFS > > > Key: MESOS-8114 > URL: https://issues.apache.org/jira/browse/MESOS-8114 > Project: Mesos > Issue Type: Bug > Environment: FreeBSD 11.1-RELEASE >Reporter: David Forsythe >Assignee: David Forsythe > > ../../mesos/src/tests/disk_quota_tests.cpp:95: Failure > Expected: (usage.get()) >= (Kilobytes(8)), actual: 1KB vs 8KB > On ZFS (with default settings), there is a large amount of time (~2s on my > test machine) between the write and the time the size reported by du is what > we're expecting. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MESOS-8114) DiskUsageCollectorTest.File fails on FreeBSD+ZFS
David Forsythe created MESOS-8114: - Summary: DiskUsageCollectorTest.File fails on FreeBSD+ZFS Key: MESOS-8114 URL: https://issues.apache.org/jira/browse/MESOS-8114 Project: Mesos Issue Type: Bug Environment: FreeBSD 11.1-RELEASE Reporter: David Forsythe Assignee: David Forsythe ../../mesos/src/tests/disk_quota_tests.cpp:95: Failure Expected: (usage.get()) >= (Kilobytes(8)), actual: 1KB vs 8KB On ZFS (with default settings), there is a large amount of time (~2s on my test machine) between the write and the time the metadata from du is what we're expecting. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MESOS-6777) IOSwitchboardTest.RecoverThenKillSwitchboardContainerDestroyed hangs on FreeBSD
David Forsythe created MESOS-6777: - Summary: IOSwitchboardTest.RecoverThenKillSwitchboardContainerDestroyed hangs on FreeBSD Key: MESOS-6777 URL: https://issues.apache.org/jira/browse/MESOS-6777 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6776) ExamplesTest.DiskFullFramework fails on FreeBSD
David Forsythe created MESOS-6776: - Summary: ExamplesTest.DiskFullFramework fails on FreeBSD Key: MESOS-6776 URL: https://issues.apache.org/jira/browse/MESOS-6776 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe Disk full framework returned 0 not 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6614) ExamplesTest.DiskFullFramework hangs on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729202#comment-15729202 ] David Forsythe commented on MESOS-6614: --- This is actually just happening inside of a jail, since it wants 127.0.0.1 as the master address. > ExamplesTest.DiskFullFramework hangs on FreeBSD > --- > > Key: MESOS-6614 > URL: https://issues.apache.org/jira/browse/MESOS-6614 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > ExamplesTest.DiskFullFramework hangs on gmake check on FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5643) GLOG_LDFLAGS breaks FreeBSD build.
[ https://issues.apache.org/jira/browse/MESOS-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727890#comment-15727890 ] David Forsythe commented on MESOS-5643: --- Doesn't seem to be an issue anymore. > GLOG_LDFLAGS breaks FreeBSD build. > -- > > Key: MESOS-5643 > URL: https://issues.apache.org/jira/browse/MESOS-5643 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > GLOG_LDFLAGS for FreeBSD has some extra quotation marks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6614) ExamplesTest.DiskFullFramework hangs on FreeBSD
David Forsythe created MESOS-6614: - Summary: ExamplesTest.DiskFullFramework hangs on FreeBSD Key: MESOS-6614 URL: https://issues.apache.org/jira/browse/MESOS-6614 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe ExamplesTest.DiskFullFramework hangs on gmake check on FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6613) OsTest.Mknod fails in a jail
David Forsythe created MESOS-6613: - Summary: OsTest.Mknod fails in a jail Key: MESOS-6613 URL: https://issues.apache.org/jira/browse/MESOS-6613 Project: Mesos Issue Type: Bug Components: stout Reporter: David Forsythe Assignee: David Forsythe mknod can't be run in a jail, so OsTest.Mknod fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6612) RmdirTest.RemoveDirectoryWithDeviceFile fails in a jail
David Forsythe created MESOS-6612: - Summary: RmdirTest.RemoveDirectoryWithDeviceFile fails in a jail Key: MESOS-6612 URL: https://issues.apache.org/jira/browse/MESOS-6612 Project: Mesos Issue Type: Bug Components: stout Reporter: David Forsythe Assignee: David Forsythe mknod can't be run within a jail so RmdirTest.RemoveDirectoryWithDeviceFile fails. If we're in a jail we should just ignore the test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6611) FreeBSD needs wait.h for wait macros
David Forsythe created MESOS-6611: - Summary: FreeBSD needs wait.h for wait macros Key: MESOS-6611 URL: https://issues.apache.org/jira/browse/MESOS-6611 Project: Mesos Issue Type: Bug Components: stout Reporter: David Forsythe Assignee: David Forsythe gtest.hpp needs wait macros on FreeBSD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6607) Configure fails on FreeBSD
David Forsythe created MESOS-6607:
-
Summary: Configure fails on FreeBSD
Key: MESOS-6607
URL: https://issues.apache.org/jira/browse/MESOS-6607
Project: Mesos
Issue Type: Bug
Reporter: David Forsythe
Assignee: David Forsythe
Configure fails when checking on JNI because of undefined pthread calls:
{code}
checking whether or not we can build with JNI...
/usr/local/openjdk8/jre/lib/amd64/server/libjvm.so: undefined reference to
`pthread_getprio'
/usr/local/openjdk8/jre/lib/amd64/server/libjvm.so: undefined reference to
`pthread_getthreadid_np'
/usr/local/openjdk8/jre/lib/amd64/server/libjvm.so: undefined reference to
`pthread_create'
/usr/local/openjdk8/jre/lib/amd64/server/libjvm.so: undefined reference to
`pthread_attr_get_np'
/usr/local/openjdk8/jre/lib/amd64/server/libjvm.so: undefined reference to
`pthread_setprio'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5645) Process.Test expect an init process in a FreeBSD jail
David Forsythe created MESOS-5645: - Summary: Process.Test expect an init process in a FreeBSD jail Key: MESOS-5645 URL: https://issues.apache.org/jira/browse/MESOS-5645 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe The init process is None in a jail, so this check breaks the test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5644) IsJailed() isn't available in process_tests.cpp
David Forsythe created MESOS-5644: - Summary: IsJailed() isn't available in process_tests.cpp Key: MESOS-5644 URL: https://issues.apache.org/jira/browse/MESOS-5644 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe IsJailed() isnt available in process_tests.cpp, so tests don't build on FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5643) GLOG_LDFLAGS breaks FreeBSD build.
David Forsythe created MESOS-5643: - Summary: GLOG_LDFLAGS breaks FreeBSD build. Key: MESOS-5643 URL: https://issues.apache.org/jira/browse/MESOS-5643 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe GLOG_LDFLAGS for FreeBSD has some extra quotation marks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5003) RmdirTest tests crash on FreeBSD
David Forsythe created MESOS-5003: - Summary: RmdirTest tests crash on FreeBSD Key: MESOS-5003 URL: https://issues.apache.org/jira/browse/MESOS-5003 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe gmake check on FreeBSD crashes in RmdirTest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4699) ./bootstrap fails for FreeBSD 10.2 from master.
[ https://issues.apache.org/jira/browse/MESOS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153464#comment-15153464 ] David Forsythe commented on MESOS-4699: --- Cool. Yep, the test suite isn't fully passing on FreeBSD yet (some more things might pass if you're not using a compressed ZFS volume). > ./bootstrap fails for FreeBSD 10.2 from master. > --- > > Key: MESOS-4699 > URL: https://issues.apache.org/jira/browse/MESOS-4699 > Project: Mesos > Issue Type: Bug > Components: build >Affects Versions: 0.27.1 > Environment: FreeBSD 10.2 >Reporter: Mark Blackman >Priority: Blocker > Attachments: 10.2-pkgs.txt > > > $ uname -a > FreeBSD severn 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 > 14:19:39 UTC 2015 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > $ ./bootstrap > ln: .gitignore: File exists > autoreconf-2.69: Entering directory `.' > autoreconf-2.69: configure.ac: not using Gettext > autoreconf-2.69: running: aclocal --warnings=all -I m4 > autoreconf-2.69: configure.ac: tracing > configure.ac:1485: warning: cannot check for file existence when cross > compiling > ../../lib/autoconf/general.m4:2777: AC_CHECK_FILE is expanded from... > configure.ac:1485: the top level > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/libprocess to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/libprocess' > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/stout to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/stout' > autoreconf-2.69: running: aclocal --warnings=all > autoreconf-2.69: configure.ac: not using Libtool > autoreconf-2.69: running: /usr/local/bin/autoconf-2.69 --warnings=all > autoreconf-2.69: configure.ac: not using Autoheader > autoreconf-2.69: running: automake --add-missing --copy --no-force > --warnings=all > autoreconf-2.69: Leaving directory `3rdparty/stout' > 3rdparty/Makefile.am:107: error: Libtool library used but 'LIBTOOL' is > undefined > 3rdparty/Makefile.am:107: The usual way to define 'LIBTOOL' is to add > 'LT_INIT' > 3rdparty/Makefile.am:107: to 'configure.ac' and run 'aclocal' and > 'autoconf' again. > 3rdparty/Makefile.am:107: If 'LT_INIT' is in 'configure.ac', make sure > 3rdparty/Makefile.am:107: its definition is in aclocal's search path. > 3rdparty/Makefile.am:84: warning: source file > '$(RY_HTTP_PARSER)/http_parser.c' is in a subdirectory, > 3rdparty/Makefile.am:84: but option 'subdir-objects' is disabled > automake-1.15: warning: possible forward-incompatibility. > automake-1.15: At least a source file is in a subdirectory, but the > 'subdir-objects' > automake-1.15: automake option hasn't been enabled. For now, the > corresponding output > automake-1.15: object file(s) will be placed in the top-level directory. > However, > automake-1.15: this behaviour will change in future Automake versions: they > will > automake-1.15: unconditionally cause object files to be placed in the same > subdirectory > automake-1.15: of the corresponding sources. > automake-1.15: You are advised to start using 'subdir-objects' option > throughout your > automake-1.15: project, to avoid future incompatibilities. > 3rdparty/Makefile.am:160: warning: source file > '$(STOUT)/tests/adaptor_tests.cpp' is in a subdirectory, > 3rdparty/Makefile.am:160: but option 'subdir-objects' is disabled > > Makefile.am:148: but option 'subdir-objects' is disabled > Makefile.am:190: warning: source file 'src/tests/ssl_tests.cpp' is in a > subdirectory, > Makefile.am:190: but option 'subdir-objects' is disabled > Makefile.am:186: warning: source file 'src/tests/ssl_client.cpp' is in a > subdirectory, > Makefile.am:186: but option 'subdir-objects' is disabled > autoreconf-2.69: automake failed with exit status: 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4699) ./bootstrap fails for FreeBSD 10.2 from master.
[ https://issues.apache.org/jira/browse/MESOS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152942#comment-15152942 ] David Forsythe commented on MESOS-4699: --- At first glance (and based on where it seems to have died) you are missing at least libtool. Can you check out the [getting started|http://mesos.apache.org/documentation/latest/getting-started/], install the FreeBSD equivalents of the required packages, and see if this is still an issue? > ./bootstrap fails for FreeBSD 10.2 from master. > --- > > Key: MESOS-4699 > URL: https://issues.apache.org/jira/browse/MESOS-4699 > Project: Mesos > Issue Type: Bug > Components: build >Affects Versions: 0.27.1 > Environment: FreeBSD 10.2 >Reporter: Mark Blackman >Priority: Blocker > Attachments: 10.2-pkgs.txt > > > $ uname -a > FreeBSD severn 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 > 14:19:39 UTC 2015 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > $ ./bootstrap > ln: .gitignore: File exists > autoreconf-2.69: Entering directory `.' > autoreconf-2.69: configure.ac: not using Gettext > autoreconf-2.69: running: aclocal --warnings=all -I m4 > autoreconf-2.69: configure.ac: tracing > configure.ac:1485: warning: cannot check for file existence when cross > compiling > ../../lib/autoconf/general.m4:2777: AC_CHECK_FILE is expanded from... > configure.ac:1485: the top level > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/libprocess to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/libprocess' > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/stout to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/stout' > autoreconf-2.69: running: aclocal --warnings=all > autoreconf-2.69: configure.ac: not using Libtool > autoreconf-2.69: running: /usr/local/bin/autoconf-2.69 --warnings=all > autoreconf-2.69: configure.ac: not using Autoheader > autoreconf-2.69: running: automake --add-missing --copy --no-force > --warnings=all > autoreconf-2.69: Leaving directory `3rdparty/stout' > 3rdparty/Makefile.am:107: error: Libtool library used but 'LIBTOOL' is > undefined > 3rdparty/Makefile.am:107: The usual way to define 'LIBTOOL' is to add > 'LT_INIT' > 3rdparty/Makefile.am:107: to 'configure.ac' and run 'aclocal' and > 'autoconf' again. > 3rdparty/Makefile.am:107: If 'LT_INIT' is in 'configure.ac', make sure > 3rdparty/Makefile.am:107: its definition is in aclocal's search path. > 3rdparty/Makefile.am:84: warning: source file > '$(RY_HTTP_PARSER)/http_parser.c' is in a subdirectory, > 3rdparty/Makefile.am:84: but option 'subdir-objects' is disabled > automake-1.15: warning: possible forward-incompatibility. > automake-1.15: At least a source file is in a subdirectory, but the > 'subdir-objects' > automake-1.15: automake option hasn't been enabled. For now, the > corresponding output > automake-1.15: object file(s) will be placed in the top-level directory. > However, > automake-1.15: this behaviour will change in future Automake versions: they > will > automake-1.15: unconditionally cause object files to be placed in the same > subdirectory > automake-1.15: of the corresponding sources. > automake-1.15: You are advised to start using 'subdir-objects' option > throughout your > automake-1.15: project, to avoid future incompatibilities. > 3rdparty/Makefile.am:160: warning: source file > '$(STOUT)/tests/adaptor_tests.cpp' is in a subdirectory, > 3rdparty/Makefile.am:160: but option 'subdir-objects' is disabled > > Makefile.am:148: but option 'subdir-objects' is disabled > Makefile.am:190: warning: source file 'src/tests/ssl_tests.cpp' is in a > subdirectory, > Makefile.am:190: but option 'subdir-objects' is disabled > Makefile.am:186: warning: source file 'src/tests/ssl_client.cpp' is in a > subdirectory, > Makefile.am:186: but option 'subdir-objects' is disabled > autoreconf-2.69: automake failed with exit status: 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4699) ./bootstrap fails for FreeBSD 10.2 from master.
[ https://issues.apache.org/jira/browse/MESOS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152586#comment-15152586 ] David Forsythe commented on MESOS-4699: --- I can't seem to repro this on my own 10.2 machines. Do you mind dumping a pkg version run? > ./bootstrap fails for FreeBSD 10.2 from master. > --- > > Key: MESOS-4699 > URL: https://issues.apache.org/jira/browse/MESOS-4699 > Project: Mesos > Issue Type: Bug > Components: build >Affects Versions: 0.27.1 > Environment: FreeBSD 10.2 >Reporter: Mark Blackman >Priority: Blocker > > $ uname -a > FreeBSD severn 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 > 14:19:39 UTC 2015 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > $ ./bootstrap > ln: .gitignore: File exists > autoreconf-2.69: Entering directory `.' > autoreconf-2.69: configure.ac: not using Gettext > autoreconf-2.69: running: aclocal --warnings=all -I m4 > autoreconf-2.69: configure.ac: tracing > configure.ac:1485: warning: cannot check for file existence when cross > compiling > ../../lib/autoconf/general.m4:2777: AC_CHECK_FILE is expanded from... > configure.ac:1485: the top level > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/libprocess to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/libprocess' > autoreconf-2.69: configure.ac: adding subdirectory 3rdparty/stout to > autoreconf > autoreconf-2.69: Entering directory `3rdparty/stout' > autoreconf-2.69: running: aclocal --warnings=all > autoreconf-2.69: configure.ac: not using Libtool > autoreconf-2.69: running: /usr/local/bin/autoconf-2.69 --warnings=all > autoreconf-2.69: configure.ac: not using Autoheader > autoreconf-2.69: running: automake --add-missing --copy --no-force > --warnings=all > autoreconf-2.69: Leaving directory `3rdparty/stout' > 3rdparty/Makefile.am:107: error: Libtool library used but 'LIBTOOL' is > undefined > 3rdparty/Makefile.am:107: The usual way to define 'LIBTOOL' is to add > 'LT_INIT' > 3rdparty/Makefile.am:107: to 'configure.ac' and run 'aclocal' and > 'autoconf' again. > 3rdparty/Makefile.am:107: If 'LT_INIT' is in 'configure.ac', make sure > 3rdparty/Makefile.am:107: its definition is in aclocal's search path. > 3rdparty/Makefile.am:84: warning: source file > '$(RY_HTTP_PARSER)/http_parser.c' is in a subdirectory, > 3rdparty/Makefile.am:84: but option 'subdir-objects' is disabled > automake-1.15: warning: possible forward-incompatibility. > automake-1.15: At least a source file is in a subdirectory, but the > 'subdir-objects' > automake-1.15: automake option hasn't been enabled. For now, the > corresponding output > automake-1.15: object file(s) will be placed in the top-level directory. > However, > automake-1.15: this behaviour will change in future Automake versions: they > will > automake-1.15: unconditionally cause object files to be placed in the same > subdirectory > automake-1.15: of the corresponding sources. > automake-1.15: You are advised to start using 'subdir-objects' option > throughout your > automake-1.15: project, to avoid future incompatibilities. > 3rdparty/Makefile.am:160: warning: source file > '$(STOUT)/tests/adaptor_tests.cpp' is in a subdirectory, > 3rdparty/Makefile.am:160: but option 'subdir-objects' is disabled > > Makefile.am:148: but option 'subdir-objects' is disabled > Makefile.am:190: warning: source file 'src/tests/ssl_tests.cpp' is in a > subdirectory, > Makefile.am:190: but option 'subdir-objects' is disabled > Makefile.am:186: warning: source file 'src/tests/ssl_client.cpp' is in a > subdirectory, > Makefile.am:186: but option 'subdir-objects' is disabled > autoreconf-2.69: automake failed with exit status: 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140173#comment-15140173 ] David Forsythe commented on MESOS-1563: --- This ticket is done, since we can build/configure/run on FreeBSD now. As for MESOS-4176, I haven't really started on it yet. I'll take a look soon. > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko >Assignee: David Forsythe > Fix For: 0.27.0 > > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4502) commit-msg hook does not work on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115888#comment-15115888 ] David Forsythe commented on MESOS-4502: --- https://reviews.apache.org/r/42735/ > commit-msg hook does not work on FreeBSD > > > Key: MESOS-4502 > URL: https://issues.apache.org/jira/browse/MESOS-4502 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > The commit-msg hook expects /bin/bash, which will not exist on FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4502) commit-msg hook does not work on FreeBSD
David Forsythe created MESOS-4502: - Summary: commit-msg hook does not work on FreeBSD Key: MESOS-4502 URL: https://issues.apache.org/jira/browse/MESOS-4502 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe The commit-msg hook expects /bin/bash, which will not exist on FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4504) Split os::memory() into platform specific files
David Forsythe created MESOS-4504: - Summary: Split os::memory() into platform specific files Key: MESOS-4504 URL: https://issues.apache.org/jira/browse/MESOS-4504 Project: Mesos Issue Type: Bug Components: stout Reporter: David Forsythe Assignee: David Forsythe Priority: Minor Currently, all platforms specify their implementations in the same place. Things will be a bit less clumsy if they're split up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4504) Split os::memory() into platform specific files
[ https://issues.apache.org/jira/browse/MESOS-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116256#comment-15116256 ] David Forsythe commented on MESOS-4504: --- https://reviews.apache.org/r/42757/ > Split os::memory() into platform specific files > --- > > Key: MESOS-4504 > URL: https://issues.apache.org/jira/browse/MESOS-4504 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: David Forsythe >Assignee: David Forsythe >Priority: Minor > > Currently, all platforms specify their implementations in the same place. > Things will be a bit less clumsy if they're split up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4251) Implement os::memory() for FreeBSD
David Forsythe created MESOS-4251: - Summary: Implement os::memory() for FreeBSD Key: MESOS-4251 URL: https://issues.apache.org/jira/browse/MESOS-4251 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe Currently there are only Linux and OS X implementations in stouts os::memory(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4251) Implement os::memory() for FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071947#comment-15071947 ] David Forsythe commented on MESOS-4251: --- https://reviews.apache.org/r/41726/ > Implement os::memory() for FreeBSD > -- > > Key: MESOS-4251 > URL: https://issues.apache.org/jira/browse/MESOS-4251 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > Currently there are only Linux and OS X implementations in stouts > os::memory(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4252) HTTPConnectionTest.ClosingResponse is broken/disabled on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071993#comment-15071993 ] David Forsythe commented on MESOS-4252: --- Test seems to work now with no extra changes. https://reviews.apache.org/r/41730/ > HTTPConnectionTest.ClosingResponse is broken/disabled on FreeBSD > > > Key: MESOS-4252 > URL: https://issues.apache.org/jira/browse/MESOS-4252 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > This test was disabled on FreeBSD when the initial support patches came in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4252) HTTPConnectionTest.ClosingResponse is broken/disabled on FreeBSD
David Forsythe created MESOS-4252: - Summary: HTTPConnectionTest.ClosingResponse is broken/disabled on FreeBSD Key: MESOS-4252 URL: https://issues.apache.org/jira/browse/MESOS-4252 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe This test was disabled on FreeBSD when the initial support patches came in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-4211) Use BSD cp in copy provisioner backend on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Forsythe reassigned MESOS-4211: - Assignee: David Forsythe > Use BSD cp in copy provisioner backend on FreeBSD > - > > Key: MESOS-4211 > URL: https://issues.apache.org/jira/browse/MESOS-4211 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > The backend assumes GNU cp unless the system is recognized as darwin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4211) Use BSD cp in copy provisioner backend on FreeBSD
David Forsythe created MESOS-4211: - Summary: Use BSD cp in copy provisioner backend on FreeBSD Key: MESOS-4211 URL: https://issues.apache.org/jira/browse/MESOS-4211 Project: Mesos Issue Type: Bug Reporter: David Forsythe The backend assumes GNU cp unless the system is recognized as darwin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4212) Fix includes in stout/os/freebsd.hpp
[
https://issues.apache.org/jira/browse/MESOS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Forsythe updated MESOS-4212:
--
Description:
The includes in freebsd.hpp are sloppy, and break the FreeBSD build with some
recent changes.
{code}
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:37:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:67:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
{code}
was:
The imports in freebsd.hpp are sloppy, and break the FreeBSD build with some
recent changes.
{code}
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:37:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:67:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
{code}
Summary: Fix includes in stout/os/freebsd.hpp (was: Fix imports in
stout/os/freebsd.hpp)
> Fix includes in stout/os/freebsd.hpp
>
>
> Key: MESOS-4212
> URL: https://issues.apache.org/jira/browse/MESOS-4212
> Project: Mesos
> Issue Type: Bug
>Reporter: David Forsythe
>Assignee: David Forsythe
>
> The includes in freebsd.hpp are sloppy, and break the FreeBSD build with some
> recent changes.
> {code}
> ../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:37:9:
> error: no member named 'sysctl' in namespace 'os'
> os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
> ^
> ../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:67:9:
> error: no member named 'sysctl' in namespace 'os'
> os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
> ^
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4212) Fix imports in stout/os/freebsd.hpp
David Forsythe created MESOS-4212:
-
Summary: Fix imports in stout/os/freebsd.hpp
Key: MESOS-4212
URL: https://issues.apache.org/jira/browse/MESOS-4212
Project: Mesos
Issue Type: Bug
Reporter: David Forsythe
Assignee: David Forsythe
The imports in freebsd.hpp are sloppy, and break the FreeBSD build with some
recent changes.
{code}
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:37:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:67:9:
error: no member named 'sysctl' in namespace 'os'
os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
^
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4211) Use BSD cp in copy provisioner backend on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066140#comment-15066140 ] David Forsythe commented on MESOS-4211: --- https://reviews.apache.org/r/41598/ > Use BSD cp in copy provisioner backend on FreeBSD > - > > Key: MESOS-4211 > URL: https://issues.apache.org/jira/browse/MESOS-4211 > Project: Mesos > Issue Type: Bug >Reporter: David Forsythe >Assignee: David Forsythe > > The backend assumes GNU cp unless the system is recognized as darwin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4212) Fix includes in stout/os/freebsd.hpp
[
https://issues.apache.org/jira/browse/MESOS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066138#comment-15066138
]
David Forsythe commented on MESOS-4212:
---
https://reviews.apache.org/r/41596/
> Fix includes in stout/os/freebsd.hpp
>
>
> Key: MESOS-4212
> URL: https://issues.apache.org/jira/browse/MESOS-4212
> Project: Mesos
> Issue Type: Bug
>Reporter: David Forsythe
>Assignee: David Forsythe
>
> The includes in freebsd.hpp are sloppy, and break the FreeBSD build with some
> recent changes.
> {code}
> ../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:37:9:
> error: no member named 'sysctl' in namespace 'os'
> os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
> ^
> ../../3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp:67:9:
> error: no member named 'sysctl' in namespace 'os'
> os::sysctl(CTL_KERN, KERN_PROC, KERN_PROC_ALL).table();
> ^
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4176) Support CMake build on FreeBSD
David Forsythe created MESOS-4176: - Summary: Support CMake build on FreeBSD Key: MESOS-4176 URL: https://issues.apache.org/jira/browse/MESOS-4176 Project: Mesos Issue Type: Task Reporter: David Forsythe Assignee: David Forsythe As noted on [39634|https://reviews.apache.org/r/39634/], a few changes may be be needed to enable a FreeBSD CMake build. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058485#comment-15058485 ] David Forsythe commented on MESOS-1563: --- [MESOS-4176|https://issues.apache.org/jira/browse/MESOS-4176] > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko >Assignee: David Forsythe > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056227#comment-15056227 ] David Forsythe commented on MESOS-1563: --- [~idownes] If I make the small changes mentioned on the reviews myself, can we land this sooner rather than later? I've sort of put myself into a holding pattern for other FreeBSD changes and filing tickets against the platform until this gets merged (or is discarded). > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko >Assignee: David Forsythe > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021817#comment-15021817 ] David Forsythe commented on MESOS-1563: --- [~idownes] Any chance of getting your eyes back on this some time soon? > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988673#comment-14988673 ] David Forsythe commented on MESOS-1563: --- [~idownes] would it be appropriate to have this ticket assigned to me? Also, what is the etiquette for filing tickets against unsupported platforms? I'd like to start creating issues for things that need to be done after this change set lands. > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Forsythe updated MESOS-1563: -- Comment: was deleted (was: [~idownes] Great! Do you want to make a first pass and have me chop it up when I address feedback, or would you like me to chop it up before you review?) > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973524#comment-14973524 ] David Forsythe commented on MESOS-1563: --- [~idownes] I've discarded the previous review and opened: https://reviews.apache.org/r/39634/ https://reviews.apache.org/r/39635/ https://reviews.apache.org/r/39636/ > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14967688#comment-14967688 ] David Forsythe commented on MESOS-1563: --- [~idownes] Great! Do you want to make a first pass and have me chop it up when I address feedback, or would you like me to chop it up before you review? > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965648#comment-14965648 ] David Forsythe edited comment on MESOS-1563 at 10/20/15 7:52 PM: - [~idownes] is there any way https://reviews.apache.org/r/39345/ will land as is, or do I need to chop it up into multiple commits? was (Author: dforsyth): [~idownes] is there anyway https://reviews.apache.org/r/39345/ will land as is, or do I need to chop it up into multiple commits? > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965648#comment-14965648 ] David Forsythe commented on MESOS-1563: --- [~idownes] is there anyway https://reviews.apache.org/r/39345/ will land as is, or do I need to chop it up into multiple commits? > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14962008#comment-14962008 ] David Forsythe commented on MESOS-1563: --- [~hausdorff] I've been watching your changes (that's actually why I started working on this :), and the changes in 39345 are pretty simple. I'm cautiously confident that our changes won't overlap too much, and I haven't touched anything cmake related yet since I figured that might be churning for a while -- I was planning on picking that up later on if this patch landed. > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14955670#comment-14955670 ] David Forsythe commented on MESOS-1563: --- Great. Is it alright to submit if make check isn't completely passing on FreeBSD? I haven't made a port because I don't know how much actually works (I haven't gotten through a complete check run without disabling some tests that probably shouldn't be disabled, and some output makes me think that certain tests aren't actually working). > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954321#comment-14954321 ] David Forsythe commented on MESOS-1563: --- I've put together a small patch that gets Mesos building on FreeBSD (I've only tried on 10.2). I can run things, but I haven't tested much. If there is interest (and I can find a shepherd), I'd be happy to submit the patch and work on building out some more FreeBSD support. > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
