mongodb @6.0.5: configure failure

[drawlusyk]

Trying to install mongodb on new macbook air m2.

sudo port install mongodb
Password:
--->  Computing dependencies for mongodb
--->  Fetching archive for mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from https://packages.macports.org/mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from https://pek.cn.packages.macports.org/macports/packages/mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from http://jog.id.packages.macports.org/macports/packages/mongodb
--->  Fetching distfiles for mongodb
--->  Verifying checksums for mongodb
--->  Extracting mongodb
--->  Applying patches to mongodb
--->  Configuring mongodb
Error: Failed to configure mongodb: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port mongodb failed

--->  Configuring mongodb
Error: Failed to configure mongodb: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port mongodb failed
dr@Denniss-MacBook-Air scripts % tail -f /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/main.log
:info:configure Removed psutil<=5.8.0 from file:///opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/distfiles/psutil-5.8.0.tar.gz (from -r etc/pip/components/core.req (line 2)) from build tracker '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/.tmp/pip-build-tracker-ozyalvj_'
:info:configure Removed build tracker: '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/.tmp/pip-build-tracker-ozyalvj_'
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/mongodb-src-r6.0.5" && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/venv/bin/pip install --find-links /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/work/distfiles --no-index --requirement etc/pip/compile-requirements.txt --verbose --verbose 
:info:configure Exit code: 1
:error:configure Failed to configure mongodb: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log so we can see what went wrong.

There was another recent report of a build failure; maybe it's the same problem. See #67746

[drawlusyk]

main log

[drawlusyk]

Since first posting I performed restart of the mac. I did a sudo port install mongodb again. It resulted in a number of ports being installed which was not the case prior to the restart.

Attached is the log file. This is clean file with only the most recent install command.

Below it the short summary of the install.

Error: Cannot install mongodb for the arch 'x86_64' because
Error: its dependency cyrus-sasl2 is only installed for the arch 'arm64'
Error: and does not have a universal variant.
Error: Unable to execute port: architecture mismatch

[ryandesign (Ryan Carsten Schmidt)]

It's true that cyrus-sasl2 does not have a universal variant, but why are you now building mongodb for x86_64 when your processor is arm64? Your original transcript showed you installing for arm64.

Which terminal application are you using? If it is an x86_64 terminal application, it will cause the shell and MacPorts to run as x86_64 processes and MacPorts will think it is on an x86_64 processor and will try to install your ports for x86_64. The solution, if that's the case, is to use an arm64 terminal application, such as /Applications/Utilities/Terminal.app.

[drawlusyk]

Not sure why arch id diff. I pressed the power button this computer yesterday so not sure how or why its i386. So entered the following "$env /usr/bin/arch -arm64 /bin/zsh" Now arch shows arm64.

sudo port install mongodb 
--->  Computing dependencies for mongodb
--->  Fetching archive for mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from https://packages.macports.org/mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from https://pek.cn.packages.macports.org/macports/packages/mongodb
--->  Attempting to fetch mongodb-6.0.5_0.darwin_22.arm64.tbz2 from http://jog.id.packages.macports.org/macports/packages/mongodb
--->  Configuring mongodb
Error: Failed to configure mongodb: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mongodb/mongodb/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port mongodb failed

new log attached.

[drawlusyk]

log 2

[ryandesign (Ryan Carsten Schmidt)]

Yes, using arch -arm64 to start your shell is one way to force an x86_64 terminal to start an arm64 shell, which will then run arm64 processes. But it would be good to figure out why you apparently have an x86_64 terminal and to replace it with an arm64 terminal.

Thanks for the log. Diffing it with the one from #67746, I think the relevant parts are identical, so I'll close this as a duplicate. I need to update the port anyway so I will have to look into it then.