[MacPorts] #58848: Error: Failed to build rust: command execution failed
Dmitri Zaitsev
zaitsev at maths.tcd.ie
Sun Aug 18 08:56:14 UTC 2019
First of all, I appreciate any advice and apologies for any
misunderstanding, I am still very new to MacPorts (after giving up on HB).
I have now ran all of these:
{{{
sudo port clean rust
sudo port selfupdate
sudo port upgrade outdated
sudo port reclaim
}}}
The reclaim command suggested to delete unneeded files that I did.
Then ran again:
{{{
sudo port install rust
}}}
This time it has correctly downloaded all the files without any SSL related
complaints.
Then came the build error. I have ran this again:
{{{
sudo port clean rust
sudo port install rust
}}}
And again no more download attempts.
I have uploaded the new log51 file.
The build error begins on the line 936 until it gets to this:
{{{
:info:build RuntimeError: failed to run:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.36.0-src/build/stage0-x86_64/bin/cargo
build --manifest-path
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.36.0-src/src/bootstrap/Cargo.toml
--frozen
:info:build make: *** [all] Error 1
:info:build make: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.36.0-src'
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.36.0-src"
&& /usr/bin/make -j8 -w all VERBOSE=1 BOOTSTRAP_ARGS="-v -j8"
:info:build Exit code: 2
:error:build Failed to build rust: command execution failed
:debug:build Error code: CHILDSTATUS 42241 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/main.log
for details.
}}}
What I find puzzling:
1. As I did not change anything on my system, why did all the files
download correctly this time but not the last time?
2. Why were existing files not recognized yesterday (the "does not exist
error") but not this time (no such error is in the log)?
3. What kind of build error is that and how to deal with it?
Thank you for any help,
Dmitri.
On Sunday, August 18, 2019, MacPorts <noreply at macports.org> wrote:
> #58848: Error: Failed to build rust: command execution failed
> ------------------------+--------------------
> Reporter: dmitriz | Owner: g5pw
> Type: defect | Status: closed
> Priority: Normal | Milestone:
> Component: ports | Version:
> Resolution: duplicate | Keywords:
> Port: rust |
> ------------------------+--------------------
> Changes (by kencu):
>
> * status: assigned => closed
> * resolution: => duplicate
>
>
> Comment:
>
> There is nothing wrong with `rust`. This is a curl / SSL issue,
> essentially a duplicate of [ticket:51516].
>
> --
> Ticket URL: <https://trac.macports.org/ticket/58848#comment:11>
> MacPorts <https://www.macports.org/>
> Ports system for macOS
>
--
Dmitri Zaitsev
School of Mathematics
Trinity College Dublin
WWW: http://www.maths.tcd.ie/~zaitsev/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190818/8b51a1f2/attachment.html>
More information about the macports-dev
mailing list