Created attachment 160930 [details]
work in progress.
It builds until
[389/398] BUILD v8_184.108.40.206
and needs a little more patching.
Created attachment 160942 [details]
next, builds until v8, but fails to link v8.
Created attachment 160949 [details]
Builds up to a point, then fails to link v8.
for the build-log.
Created attachment 161007 [details]
this builds on current-amd64.
It still needs more cleanup.
Created attachment 161139 [details]
New version, builds in poudriere on current-amd64.
Testing on other versions @work.
Created attachment 161162 [details]
This builds on 11-current-amd64, 10.2 i+a.
It fails on 9.3a.
(In reply to Kurt Jaeger from comment #7)
I'm going to take a look.
Created attachment 161299 [details]
More progress trying to fix rethinkdb build errors on 9.3-a.
Created attachment 161302 [details]
poudriere testport on 93x64
v7 fails to build on 11-amd64.
Additional test-builds @work. Logfile will be provided soonish.
(In reply to Kurt Jaeger from comment #11)
Yes, the latest added patches should be only be applied to 9.3a release.
I made some changes in rethinkdb/Makefile. Testing work@
Created attachment 161400 [details]
Both patches were removed because they are wrong.
dependency www/node fails to build on 9.3a 8-(
9.3a build seems to be problematic, Carlos reports:
And there's an PR that has a bit more on the C++ issues:
So, we'll add this with BROKEN on 9.
There's a version 2.1.5-2 out.
In a 10.1p19 I got this with shar-v8:
./src/arch/io/timer/timer_signal_provider.hpp:23:5: error: unknown type name 'timer_t';
which I could overcome with:
--- src/arch/io/timer/timer_signal_provider.hpp.orig 2015-11-07 00:40:37.000000000 +0100
+++ src/arch/io/timer/timer_signal_provider.hpp 2015-11-06 23:49:19.000000000 +0100
@@ -20,7 +20,7 @@
friend void timer_signal_provider_signal_handler(UNUSED int signum, siginfo_t *siginfo, UNUSED void *uctx);
- timer_t timerid;
+ __timer_t timerid;
But then (with external re2/v8 and pkg installed re2/v8) I got this:
/usr/local/src/rethinkdb/work/rethinkdb-2.1.4/build/external/re2_20140111/lib/libre2.a(nfa.o): In function `re2::NFA::Search(re2::StringPiece const&, re2::StringPiece const&, bool, bool, re2::StringPiece*, int)':
re2/nfa.cc:(.text+0x11b2): undefined reference to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)'
re2/nfa.cc:(.text+0x11e7): undefined reference to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)'
/usr/local/src/rethinkdb/work/rethinkdb-2.1.4/build/external/re2_20140111/lib/libre2.a(tostring.o): In function `re2::ToStringWalker::PostVisit(re2::Regexp*, int, int, int*, int)':
re2/tostring.cc:(.text+0xb9a): undefined reference to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)'
/usr/local/src/rethinkdb/work/rethinkdb-2.1.4/build/external/v8_220.127.116.11/lib/libv8_base.a(code-stubs-hydrogen.o): In function `v8::internal::ToNumberStub::GenerateCode()':
../src/code-stubs-hydrogen.cc:(.text._ZN2v88internal12ToNumberStub12GenerateCodeEv+0xcd): undefined reference to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)'
/usr/local/src/rethinkdb/work/rethinkdb-2.1.4/build/external/v8_18.104.22.168/lib/libv8_base.a(code-stubs-hydrogen.o): In function `v8::internal::NumberToStringStub::GenerateCode()':
../src/code-stubs-hydrogen.cc:(.text._ZN2v88internal18NumberToStringStub12GenerateCodeEv+0xcd): undefined reference to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)'
/usr/local/src/rethinkdb/work/rethinkdb-2.1.4/build/external/v8_22.214.171.124/lib/libv8_base.a(code-stubs-hydrogen.o):../src/code-stubs-hydrogen.cc:(.text._ZN2v88internal25FastCloneShallowArrayStub12GenerateCodeEv+0xcd): more undefined references to `std::__1::basic_ostream<char, std::__1::char_traits<char> >::operator<<(void const*)' follow
c++: error: linker command failed with exit code 1 (use -v to see invocation)
I'm not to much a c/++ programmer, so that I'm not in the position to solve this on my own. Any idea/workaround which is known?
There's a version 2.2.1 out now.
Ive tried the v8 shar on 10.3-RELEASE FreeBSD 10.3-RELEASE
and below id what resulted. seems to have built fine, though there is no rc script for it i tried it manually
rethinkdb --config-file /usr/local/etc/rethinkdb/instances.d/default.conf
Recursively removing directory /var/db/rethinkdb_data/tmp
In recursion: removing file /var/db/rethinkdb_data/tmp
Version: rethinkdb 2.1.4 (CLANG 3.4.1 (tags/RELEASE_34/dot1-final 208032))
error: Error in src/utils.cc at line 533:
error: Guarantee failed: [res == 0] (errno 2 - No such file or directory) Fatal error: failed to delete '/var/db/rethinkdb_data/tmp'.
error: Wed Jun 8 05:36:59 2016
1: 0x804ec2 <_ZN11backtrace_tC1Ev+0x42> at /usr/local/bin/rethinkdb at 0x804ec2 ()
2: 0x8055d4 <_ZN26lazy_backtrace_formatter_tC2Ev+0x24> at /usr/local/bin/rethinkdb at 0x8055d4 ()
3: 0x804b29 <_Z16format_backtraceb+0x19> at /usr/local/bin/rethinkdb at 0x804b29 ()
4: 0x8a22a8 <_Z18report_fatal_errorPKciS0_z+0x178> at /usr/local/bin/rethinkdb at 0x8a22a8 ()
5: 0x80fa5d <_Z23remove_directory_helperPKcPK4statiP3FTW+0x8d> at /usr/local/bin/rethinkdb at 0x80fa5d ()
6: 0x8061c2f5e <nftw+0xfe> at /lib/libc.so.7 at 0x8061c2f5e ()
7: 0x80faf3 <_Z26remove_directory_recursivePKc+0x53> at /usr/local/bin/rethinkdb at 0x80faf3 ()
8: 0x80fef6 <_Z28recreate_temporary_directoryRK11base_path_t+0xc6> at /usr/local/bin/rethinkdb at 0x80fef6 ()
9: 0xa58936 <_Z24main_rethinkdb_porcelainiPPc+0x2f6> at /usr/local/bin/rethinkdb at 0xa58936 ()
10: 0x8a0d03 <main+0x303> at /usr/local/bin/rethinkdb at 0x8a0d03 ()
11: 0x78b74f <_start+0x16f> at /usr/local/bin/rethinkdb at 0x78b74f ()
Trace/BPT trap (core dumped)
Created attachment 174373 [details]
v9 2.3.5 of this port
Updated the port and patched to 2.3.5, the port compiles but fail to link the executable itself, need to track it down. There are some compilation issues from v8 headers if the package is installed system wide, probably the headers is parsed in the wrong order; for now the only way is to remove it. I hope that someone is interested in this.
To keep track of current event:
- Company behind rethink is closing
Yes, it seems that RethinkDB has a second chance after the project has been donated to the Linux Foundation.
We can try to fix our port.