mongo-tools @3.1.9: build fails

[andrew.oxenburgh@…]

Hi,

I'm not sure if you support mongo-tools, as it's not in your list of 'available ports', but it is when I do an 'sudo port install mongo-tools'.

The error seems to be 404 on mongo-tools-3.1.9_0.darwin_15.x86_64.tbz2.

I installed mongodb fine.

Please find enclosed a copy of the log, with trace enabled.

[andrew.oxenburgh@…]

output from sudo port install -t mongo-tools

[ryandesign (Ryan Carsten Schmidt)]

Replying to andrew.oxenburgh@…:

I'm not sure if you support mongo-tools, as it's not in your list of 'available ports',

Yes, I support mongo-tools. The list of available ports on the web site is currently truncated for an unknown reason; see #49179.

but it is when I do an 'sudo port install mongo-tools'.

The error seems to be 404 on mongo-tools-3.1.9_0.darwin_15.x86_64.tbz2.

That's not a problem. That's a binary archive. Binary archives are optional in MacPorts. There are no binary archives for any port for OS X 10.11 El Capitan yet; see #48609.

When a binary archive is not available, MacPorts fetches and builds the source. That's what's failing, and that's what we need to investigate.

Please find enclosed a copy of the log, with trace enabled.

Does the same problem happen with trace mode disabled? I have not tested this port with trace mode.

[jean.helie@…]

Hi, yes it does, I ran sudo port install mongo-tools and couldn't build either.

Replying to ryandesign@…:

Replying to andrew.oxenburgh@…:

I'm not sure if you support mongo-tools, as it's not in your list of 'available ports',

Yes, I support mongo-tools. The list of available ports on the web site is currently truncated for an unknown reason; see #49179.

but it is when I do an 'sudo port install mongo-tools'.

The error seems to be 404 on mongo-tools-3.1.9_0.darwin_15.x86_64.tbz2.

That's not a problem. That's a binary archive. Binary archives are optional in MacPorts. There are no binary archives for any port for OS X 10.11 El Capitan yet; see #48609.

When a binary archive is not available, MacPorts fetches and builds the source. That's what's failing, and that's what we need to investigate.

Please find enclosed a copy of the log, with trace enabled.

Does the same problem happen with trace mode disabled? I have not tested this port with trace mode.

[da@…]

I also have this problem. Output:

--->  Computing dependencies for mongo-tools
--->  Building mongo-tools
Error: org.macports.build for port mongo-tools returned: command execution failed
Please see the log file for port mongo-tools for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mongo-tools/mongo-tools/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port mongo-tools failed

OSX 10.9, MacPorts 2.3.4

[da@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to 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 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 ​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 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.

[coviex@…]

I just added the log from my system as I hope the problem is almost the same.

sudo port install mongo-tools

[da@…]

No, I do not use any of that (or any other) protection software. What trace mode do you mean? MacPorts? I do not remember that i ever enabled it in MacPorts.

[jean.helie@…]

Hi Ryan, Thanks for looking into this. I've just updated but still can't build, I've attached the log file.

:~$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.3.4 installed,
MacPorts base version 2.3.4 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated

:~$ sudo port upgrade outdated
Nothing to upgrade.

:~$ sudo port install mongo-tools
--->  Computing dependencies for mongo-tools
--->  Building mongo-tools
Error: org.macports.build for port mongo-tools returned: command execution failed
Please see the log file for port mongo-tools for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mongo-tools/mongo-tools/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port mongo-tools failed

[ryandesign (Ryan Carsten Schmidt)]

Replying to jean.helie@…:

Thanks for looking into this. I've just updated but still can't build, I've attached the log file.

Replying to coviex@…:

I just added the log from my system as I hope the problem is almost the same.

Both your logs contain the "usage: link [options] main.o" message, so yes, this is the problem I've already fixed.

But it seems the rsync server is no longer pulling changes from the Subversion server, meaning that for users who use the rsync server for syncing (it is the default), running "sudo port sync" or "sudo port selfupdate" won't pick up this (or any other) fix. We've reported this problem to the administrator and hope he will resolve it soon. You can either wait for that, or reconfigure your MacPorts to contact the Subversion server directly instead of using rsync. Instructions for that are in the wiki.

Replying to da@…:

No, I do not use any of that (or any other) protection software.

You must be using some software that detects library insertion, or else it would not be complaining that a library was inserted.

What trace mode do you mean? MacPorts? I do not remember that i ever enabled it in MacPorts.

Your log shows that you are using MacPorts trace mode, which is off by default. You enabled it either by supplying the "-t" flag when installing the port, or else you changed a setting in macports.conf to turn it on all the time.

[da@…]

What setting in macports.conf switches trace mode? I did not find anything about it in documentation.

[jean.helie@…]

Replying to ryandesign@…:

You can either wait for that, or reconfigure your MacPorts to contact the Subversion server directly instead of using rsync. Instructions for that are in the wiki.

I've updated using svn and can confirm I can now build mongo-tools. Thanks!

[coviex@…]

selfupdate was fixed and mongo-tools install ok.

[ryandesign (Ryan Carsten Schmidt)]

Replying to da@…:

What setting in macports.conf switches trace mode? I did not find anything about it in documentation.

I'm not sure. We don't advertise one, but I assumed one existed. You can compare your macports.conf file with the macports.conf.default file in the same directory to see what changes you've made.

[ryandesign (Ryan Carsten Schmidt)]

I no longer remember what needs to be done for this issue. If anybody still experiences the problem with mongo-tools 3.2.4, please attach a new main.log file

[ryandesign (Ryan Carsten Schmidt)]

Presumed fixed.