#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 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. Good to know the issue was recorded but what about handling this issue on port install / upgrade calls? 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... -- Ticket URL: <https://trac.macports.org/ticket/40247#comment:22> MacPorts <http://www.macports.org/> Ports system for OS X