#40247: mongodb @2.4.6 build error on v8 dependent code ----------------------+-------------------------- Reporter: gutu@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: fixed | Keywords: Port: mongodb | ----------------------+-------------------------- Comment (by ryandesign@…): Replying to [comment:22 p.perroud@…]:
I confirm rebuilding mongodb after v8 was desactivated is *solving* the issue. Now - be aware that's mongo JS shell that's making use of v8 - not the database server itself. Meaning that v8 must be activated back after mongodb was rebuilt in order to interact with the database server from its shell.
No, that's not necessary. The whole point of this ticket is that the v8 MacPorts provides is now too new for mongodb, therefore the solution was to make mongodb use its own internal version of v8 instead. MacPorts v8 is no longer involved -- except that having it activated while building mongodb causes mongodb to fail to build, therefore I advised how to deactivate it first. If you need MacPorts v8 for other reasons then you should reactivate it after building mongodb, but if you had only needed it for mongodb then you do not need to.
Good to know the issue was recorded but what about handling this issue on port install / upgrade calls?
It is handled automatically, in that if you have the v8 port active while trying to build mongodb, you will be told to deactivate it first, thanks to the conflicts_build portgroup.
By example - when you update v8 you have to rebuild mongodb before or when you install mongodb you have to (re)install v8 later, etc...
If it were necessary to rebuild a port, we would increase its revision, as for example I have done here with mongodb. -- Ticket URL: <https://trac.macports.org/ticket/40247#comment:23> MacPorts <http://www.macports.org/> Ports system for OS X