mongodb 2.4 branch can't install on Mavericks

[moderndeveloperllc (Mark Garrett)]

It looks like mongodb 2.4.x won't be supported on OSX 10.9/Xcode 5.0.1 by default due to changes Apple made with their compilers:

​https://jira.mongodb.org/browse/SERVER-10644

The bottom comments may provide a patch solution, though I don't know enough about scons to even attept it. The in-development 2.5.x master supposedly works. Perhaps a mongodb-dev port?

[emirotin (Eugene Mirotin)]

+1 for this, quite critical — mongo stopped working after the OS upgrade, I removed it and now I cannot re-install it

[emirotin (Eugene Mirotin)]

Cc Me!

[juanhernandezgomez@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I'll see what I can do. Meanwhile, anyone needing mongodb (or anything else that doesn't work on Mavericks yet) should not upgrade to Mavericks! :) Check compatibility of your apps before you upgrade your OS.

[p.perroud@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #40890.

[dominik.zogg@…]

+1

[skler84@…]

+1 ! :)

[skler84@…]

Cc Me!

[moderndeveloperllc (Mark Garrett)]

For those of us who run with scissors in dark rooms filled with marbles and install major OS releases on the first day:

If you MUST get mongo running now, download the binaries from ​http://www.mongodb.org/downloads. You can then start the server up manually with (assuming default paths):

sudo -u _mongo <<path_to_mongod_binary>> --dbpath /opt/local/var/db/mongodb --logpath /opt/local/var/log/mongodb/mongodb.log --logappend

MacPorts will not know mongodb is installed, so any libraries that have it as a prereq will not build. If you are using PHP, install the needed extension via pecl:

port install pear-install-phar pear-PEAR
pecl install mongo

You will need to follow the install directions to make sure the .so gets loaded. I just duplicated a file that already existed in /opt/local/var/db/php<<your_php_version>> and changed its extension= declaration to mongo.so. I'm not a Python user, but I think y'all can use pip to ​install your extension.

Since this is a trouble ticket and not a help forum, please direct questions about the above directly to my email. I may be able to help, I may not.

[phuoc@…]

+1

Currently, I have to use the workaround suggested by Mark!

[hacker@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I have a mongodb-devel in progress, but it doesn't build on Mavericks either. Next I'll want to try it on earlier OS X versions.

[slava@…]

patch for mavericks

[slava@…]

Hi I created patch that work on Mavericks. Maybe someone test it on Mountain Lion and Lion.

[slava@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Thanks. That patch looks very simple. The developers of mongodb made it sound like backporting Mavericks compatibility to the 2.4 branch would be prohibitively difficult. Have you run these changes by them to see if this is really all that's needed?

[slava@…]

I don't fully understand the question. On my machine these patch works. I tried make patch more universal, in order to be able suggest it to upstream.

[slava@…]

Here is linker info ​https://gist.github.com/bacher09/81c803544d9bde1ee54e .

[ryandesign (Ryan Carsten Schmidt)]

I'm suggesting that you attach your patch to the ​upstream bug report and get confirmation from the developers that it is the correct fix for the problem.

[slava@…]

Hi I've attached this patch to upstream bug tracker. I was a bit confused, because bug has resolved status in theirs bug tracker.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #40976.

[srogers (Steve Rogers)]

This is the error that's preventing build for me: ​https://jira.mongodb.org/browse/SERVER-10644

[csaltos@…]

Cc Me!

[csaltos@…]

As commented in the mongodb ticket SERVER-10644: The patch is already applied by mongodb at the master branch: ​https://github.com/mongodb/mongo/commit/c70a72b151fcfab26d0db5e8ceeb7c04a96ce449 but I think this is the 2.5 !!

[slava@…]

Yes this for 2.5, my patch works on 2.4.

[p.perroud@…]

This defect was first reported 2+ months ago but nothing seems to be done about it: is'nt time to move on? The proposal made in ticket header about a mongodb-dev port is interesting but what would happen about it in the long terms? If 2 different ports were the solution then I would recommand a stable mongodb port and an unstable mongodb-dev port. But this leads to version issues since 2.4 was actually an unstable - the last stable being 2.2.6 as shown here: ​http://www.mongodb.org/downloads. Is it possible to downgrade the existing port to 2.2.6 to build a stable port then create a mongodb-dev unstable port with patched 2.4 or 2.5? To put all this in perspective, I am also using mongodb on a Debian 7 server and the version it runs is 2.0.6: ​http://packages.debian.org/wheezy/mongodb-server.

[brandon.zacharie@…]

Cc Me!

The submitted patch worked for me.

[ryandesign (Ryan Carsten Schmidt)]

Replying to p.perroud@…:

But this leads to version issues since 2.4 was actually an unstable - the last stable being 2.2.6 as shown here: ​http://www.mongodb.org/downloads.

When the second digit is even, it is stable. 2.4.x is the latest stable series. When the second digit is odd, it is unstable/development. 2.5.x is the latest unstable/development series.

[p.perroud@…]

Replying to ryandesign@…:

When the second digit is even, it is stable. 2.4.x is the latest stable series. When the second digit is odd, it is unstable/development. 2.5.x is the latest unstable/development series.

But they do have a 2.4 "nightly" classified as "unstable"...

May be we could agree on a different terminolgy: even (2.4) standing for "production" and odd (2.5) for "development".

In my understanding the Mavericks issue was addressed in the 2.5 branch 2 months ago and will never reach the 2.4: this is why we are stuck in this issue today.

Since a port is supposed to provide the original package, patching the official 2.4.7 to build on Mavericks is hardly an option. Which means the next "production" release that builds on Mavericks will be 2.6 - in many months from now.

For Mavericks users a new mongodb-dev 2.5.x port that would compile on XCode 5 should be provided ASAP - assuming the issue was really fixed in the 2.5 branch indeed. The existing 2.4.7 mongodb "production" port should require XCode 4, redirecting Mavericks users to mongodb-dev port.

In the future, the "production" port would increment even versions and the "development" port would increment odd versions.

When both ports will be installed on same machine, only one should be "active" at a time: doing it that way it would be possible to switch from "development" to "production" (and back) simply by changing the active mongodb port on this machine.

Is this making sense?

[oliver.bock@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to p.perroud@…:

Is this making sense?

Yes; you've described how -devel ports work in MacPorts. But as I said, though I have locally developed a mongodb-devel (sub)port, it does not compile. Meanwhile we already have a patch above that should allow mongodb 2.4.x to build on Mavericks. I intend to compare it with the fix that was committed to the official sources for 2.5.x and then add a version of it to our mongodb port and forgo adding a mongodb-devel (sub)port for now.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #41067, #41081.

[p.perroud@…]

Replying to ryandesign@…:

I intend to compare it with the fix that was committed to the official sources for 2.5.x and then add a version of it to our mongodb port and forgo adding a mongodb-devel (sub)port for now.

OK so what you are telling us is: be patient - a new 2.4.x port that builds on Mavericks will show up as soon as you could solved it up from the fix the mongodb team put in their 2.5 branch 2 months ago. Is that correct?

Now about the postpone -dev port: I don't know if it's only me but I would have the use for such a cutting edge port, just to let you know. My production server being a 2.0 on debian 7 linux, a 2.4 on macosx is not as good as a 2.5 would be for R&D ...

[mitch@…]

Cc Me!

[mitch@…]

Trying to figure if we need to ditch macports support for mongo for now, or wait... My development team is waiting on the mavericks update, as I told them to wait for me to blow up my laptop (which I'm glad I did, as we cannot afford to lose productivity right now).

How long before macports and mavericks can support mongo? Can I do anything to help?

[pleusmann@…]

Found the button for CC ;)

[pleusmann@…]

Cc Me!

[jchauvel@…]

Cc Me!

[roger.clivio@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to slava@…:

Hi I created patch that work on Mavericks. Maybe someone test it on Mountain Lion and Lion.

Thanks. I wanted to understand why the patch was different from what upstream committed in ​c70a72b151fcfab26d0db5e8ceeb7c04a96ce449. I've now had a chance to look into it, tried the build with just the upstream patch, saw the build problems, found that most of the remaining parts of the patch were also from upstream changes in ​bafd5c286f824ddcacc4376af1db35e5e8f11ea1 and ​a25c25b030cd2f35db1e0e0e9e32ca9efbc8a5f1. So that's fine.

I've committed the fixes in r112860 though I split it into a few patches, one per upstream change.

[p.perroud@…]

Replying to ryandesign@…:

I've committed the fixes in r112860 though I split it into a few patches, one per upstream change.

2.4.8 is building fine on Mavericks but mongo shell is still not working:

--->  Installing mongodb @2.4.8_0
--->  Activating mongodb @2.4.8_0
--->  Cleaning mongodb
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.
$ sudo port load mongodb
$ mongo
MongoDB shell version: 2.4.8
connecting to: test
Sun Nov  3 11:05:10.924 Error: couldn't connect to server 127.0.0.1:27017 at src/mongo/shell/mongo.js:145
exception: connect failed
$ ps -afx | grep mongodb
    0 76771     1   0 11:05AM ??         0:00.00 /opt/local/bin/daemondo --label=mongodb --start-cmd sudo -u _mongo /opt/local/bin/mongod --dbpath /opt/local/var/db/mongodb --logpath /opt/local/var/log/mongodb/mongodb.log --logappend ; --pid=exec
    0 76772 76771   0 11:05AM ??         0:00.01 sudo -u _mongo /opt/local/bin/mongod --dbpath /opt/local/var/db/mongodb --logpath /opt/local/var/log/mongodb/mongodb.log --logappend
  500 76773 76772   0 11:05AM ??         0:00.49 /opt/local/bin/mongod --dbpath /opt/local/var/db/mongodb --logpath /opt/local/var/log/mongodb/mongodb.log --logappend
  

[ryandesign (Ryan Carsten Schmidt)]

Replying to p.perroud@…:

Replying to ryandesign@…:

I've committed the fixes in r112860 though I split it into a few patches, one per upstream change.

2.4.8 is building fine on Mavericks but mongo shell is still not working:

It is working for me. Could you file a new ticket? Let's consider this issue, which was about getting mongodb to build on Mavericks, solved.

[emirotin (Eugene Mirotin)]

Replying to ryandesign@…:

It is working for me. Could you file a new ticket? Let's consider this issue, which was about getting mongodb to build on Mavericks, solved.

Mongo shell works for me as well.

Thank you for the fix.

[p.perroud@…]

Replying to ryandesign@…:

Replying to p.perroud@…:

Replying to ryandesign@…:

I've committed the fixes in r112860 though I split it into a few patches, one per upstream change.

2.4.8 is building fine on Mavericks but mongo shell is still not working:

It is working for me. Could you file a new ticket? Let's consider this issue, which was about getting mongodb to build on Mavericks, solved.

Well - that won't be necessary: after I re-installed it once again the shell seems to be working fine - more verbose than usual but it works - thank you.

$ mongo
MongoDB shell version: 2.4.8
connecting to: test
Welcome to the MongoDB shell.
For interactive help, type "help".
For more comprehensive documentation, see
	http://docs.mongodb.org/
Questions? Try the support group
	http://groups.google.com/group/mongodb-user
> db
test
>