-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compilation error on mongo 3.6.5 #146
Comments
Which branch of mongo-rocks are you using? |
i don t checkout from any branch but directly used the tarball from r3.6.5 of mongorocks |
I now see that SERVER-33743 was backported to 3.6.5 and broke compilation for mongo-rocks. Please use 3.6.4 until this can be fixed. @igorcanadi this can probably be fixed by backporting something from the 4.0 branch here? |
Compilation with r3.6.4 works fine |
Yeah, this is a result from
mongodb/mongo@2ee6908,
but that diff hasn't been applied to MongoRocks 4.0 either, so a simple
backport is not an option unfortunately.
…On Wed, Jul 18, 2018 at 8:54 AM Jérémy RAVERDY ***@***.***> wrote:
Compilation with r3.6.4 works fine
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABClzwBUCccBNLWkgyuxW_wwUq65Syusks5uH1oYgaJpZM4VUaZQ>
.
|
is this issue resolved ? |
Hi , 0x55e5278952c2 0x55e5278946b9 0x55e527894c97 0x7f5dd9808330 0x55e526097076 0x55e5262a91df 0x55e5262ab133 0x55e5262791dd 0x55e5262e1cbb 0x55e525ee8975 0x55e526092e35 0x55e525f55389 0x7f5dd9450f45 0x55e526091475 |
I use this command to build the rocksdb part |
Output of the core file: |
2019-01-02T13:37:08.376+0000 I CONTROL [initandlisten] target_arch: x86_64 +1, but my mongodb is 3.4.20 mongo-rocks is 3.4 |
I ought to think mongoRocks3.6 is a skipped version. I guess Perhaps you want to use changeStream? |
Hi,
I encounter the following error when trying to compile mongo 3.6.5 with rocksdb 5.14.2 on ubuntu 14.04:
I used the following command to proceed:
note that using the same environment/command with mongo 3.4.X, i never had any problem
The text was updated successfully, but these errors were encountered: