[MacPorts] #68185: rust: source build fails when running under rosetta 2

MacPorts noreply at macports.org
Sun Sep 17 23:17:15 UTC 2023


#68185: rust: source build fails when running under rosetta 2
--------------------+--------------------
 Reporter:  lukaso  |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  ports   |    Version:
 Keywords:          |       Port:  rust
--------------------+--------------------
 When I look to build an x86_64 version of rust under rosetta `arch -x86-64
 /bin/zsh`, it fails with:

 {{{
 :info:build DYLD_LIBRARY_PATH="/Users/lukasoberhuber/macports-
 gimp3-x86_64/var/macports/build/_Users_lukasoberhuber_macports-
 gimp3-x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.71.1-src/build/x86_64
 -apple-darwin/stage1/lib" "/Users/lukasoberhuber/macports-
 gimp3-x86_64/var/macports/build/_Users_lukasoberhuber_macports-
 gimp3-x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.71.1-src/build/x86_64
 -apple-darwin/stage1/bin/rustc" "-vV" "-Wrust_2018_idioms"
 "-Wunused_lifetimes" "-Wsemicolon_in_expressions_from_macros" "-Dwarnings"
 "-Clinker=/Users/lukasoberhuber/macports-gimp3-x86_64/var/macports/build
 /_Users_lukasoberhuber_macports-
 gimp3-x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/compwrap/ld/usr/bin/clang"
 "-Zunstable-options" "--check-cfg=values(bootstrap)" "--remap-path-prefix"
 "/Users/lukasoberhuber/macports-gimp3-x86_64/var/macports/build
 /_Users_lukasoberhuber_macports-
 gimp3-x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work=/Users/lukasoberhuber
 /macports-gimp3-x86_64/libexec/rust/src" "-Z" "force-unstable-if-unmarked"
 :info:build -------------
 :info:build --- stderr
 :info:build <jemalloc>: Error allocating TSD
 :info:build rustc exited with signal: 6 (SIGABRT)
 }}}

 Why would I want to do this relatively exotic build? Because Circle CI is
 getting ready to get rid of all Intel build bots and so this is how I will
 have to build the intel version.

 This would not be an issue if macports could use pre-built binaries for
 rust when building in a custom location and without sudo, but I don't
 think that's how it work.

-- 
Ticket URL: <https://trac.macports.org/ticket/68185>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list