[MacPorts] #49176: mongo-tools @3.1.9: build fails

MacPorts noreply at macports.org
Sun Oct 11 23:08:52 PDT 2015


#49176: mongo-tools @3.1.9: build fails
---------------------------------+--------------------------
  Reporter:  andrew.oxenburgh@…  |      Owner:  ryandesign@…
      Type:  defect              |     Status:  assigned
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:  2.3.4
Resolution:                      |   Keywords:
      Port:  mongo-tools         |
---------------------------------+--------------------------

Comment (by ryandesign@…):

 Replying to [ticket:49176 andrew.oxenburgh@…]:
 > Please find enclosed a copy of the log, with trace enabled.

 Andrew, the error shown in your log...

 {{{
 usage: link [options] main.o
 }}}

 ...is a duplicate of #49147 which has been fixed. Run "sudo port
 selfupdate" to receive the fix, then try building mongo-tools again.


 Replying to [comment:3 da@…]:
 > I also have this problem. Output:

 Da, your error appears to be different:

 {{{
 fatal error: runtime: bsdthread_register error (unset
 DYLD_INSERT_LIBRARIES)
 }}}

 I searched Google for this error and found a
 [https://groups.google.com/forum/#!topic/golang-nuts/HtcZc3wO-rw
 discussion] which places the blame on security software such as McAfee
 Endpoint Protection or Digital Guardian. Do you have anything like that
 installed? If so try uninstalling it or turning it off. The security
 software is correct to complain about a library being inserted into a
 program; that could be done maliciously. In the case of MacPorts, it's
 done because you enabled trace mode. In trace mode, MacPorts uses
 DYLD_INSERT_LIBRARIES to insert a library into the programs it runs that
 ensures that no program uses files it is not allowed to. So another way to
 avoid the error is not to use trace mode. But of course then you don't get
 the protections that trace mode offers.


 Replying to [comment:2 jean.helie@…]:
 > yes it does, I ran sudo port install mongo-tools and couldn't build
 either.

 Jean, you didn't provide a log so I don't know why your build failed.
 Since I've already committed a fix for one problem, you could run "sudo
 port selfupdate" and see if your build error persists. If so, please
 attach the main.log file.

-- 
Ticket URL: <https://trac.macports.org/ticket/49176#comment:5>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list