cargo-c @0.7.3_1 error: pasting formed 'RUST_VERSION_OPENSSL_(

[khorton (Kevin Horton)]

cargo-c @0.7.3_1 fails to build, failing with:

:info:build   cargo:warning=build/expando.c:10:1: error: pasting formed 'RUST_VERSION_OPENSSL_(', an invalid preprocessing token
:info:build   cargo:warning=VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
:info:build   cargo:warning=^
:info:build   cargo:warning=build/expando.c:5:23: note: expanded from macro 'VERSION'
:info:build   cargo:warning=#define VERSION(n, v) VERSION2(n, v)
:info:build   cargo:warning=                      ^
:info:build   cargo:warning=build/expando.c:4:43: note: expanded from macro 'VERSION2'
:info:build   cargo:warning=#define VERSION2(n, v) RUST_VERSION_##n##_##v
:info:build   cargo:warning=                                          ^
:info:build   cargo:warning=1 error generated.
:info:build   exit status: 1
:info:build   --- stderr
:info:build   thread 'main' panicked at '
:info:build   Header expansion error:
:info:build   Error { kind: ToolExecError, message: "Command \"/usr/bin/clang\" \"-O3\" \"-ffunction-sections\" \"-fdata-sections\" \"-fPIC\" \"--target=x86_64-apple-darwin\" \"-I\" \"/opt/local/include\" \"-Wall\" \"-Wextra\" \"-E\" \"build/expando.c\" with args \"clang\" did not execute successfully (status code exit status: 1)." }
:info:build   Failed to find OpenSSL development headers.
:info:build   You can try fixing this setting the `OPENSSL_DIR` environment variable
:info:build   pointing to your OpenSSL installation or installing OpenSSL headers package
:info:build   specific to your distribution:
:info:build       # On Ubuntu
:info:build       sudo apt-get install libssl-dev
:info:build       # On Arch Linux
:info:build       sudo pacman -S openssl
:info:build       # On Fedora
:info:build       sudo dnf install openssl-devel
:info:build   See rust-openssl README for more information:
:info:build       https://github.com/sfackler/rust-openssl#linux
:info:build   ', /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cargo-c/cargo-c/work/.home/.cargo/macports/openssl-sys-0.9.61/build/main.rs:147:13
:info:build   stack backtrace:
:info:build      0: _rust_begin_unwind
:info:build      1: std::panicking::begin_panic_fmt
:info:build      2: build_script_main::validate_headers
:info:build      3: build_script_main::main
:info:build      4: core::ops::function::FnOnce::call_once
:info:build   note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
:info:build warning: build failed, waiting for other jobs to finish...
:info:build error: build failed
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cargo-c/cargo-c/work/cargo-c-0.7.3" && /opt/local/bin/cargo build --release --frozen -v -j16 
:info:build Exit code: 101
:error:build Failed to build cargo-c: command execution failed
:debug:build Error code: CHILDSTATUS 97426 101
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback 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_devel_cargo-c/cargo-c/main.log for details.

[khorton (Kevin Horton)]

main.log

[mascguy (Christopher Nielsen)]

Marcus, I'm seeing this locally too. As for the buildbots, their builds are failing due to the following (perhaps because the port is depending on openssl, rather than the version-specific one):

--->  Building cargo-c
DEBUG: system -W /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_devel_cargo-c/cargo-c/work/cargo-c-0.7.3: /opt/local/bin/cargo update
dyld: Library not loaded: /opt/local/libexec/openssl11/lib/libssl.1.1.dylib
  Referenced from: /opt/local/bin/cargo
  Reason: image not found
Command failed: /opt/local/bin/cargo update

Even with the openssl portgroup added, this port is still not finding the OpenSSL include directory. Is there an environment variable/build arg that needs to be set, like OPENSSL_DIR...?

[mascguy (Christopher Nielsen)]

FYI, this definitely isn't a Monterey-specific issue; I'm also seeing it on macOS 10.13.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #63851.

[catap (Kirill A. Korinsky)]

A fix for this issue is trivial: simple update port.

PR: ​https://github.com/macports/macports-ports/pull/12850

[catap (Kirill A. Korinsky)]

In 1854d028f7824578d715b456348053ec21830c08/macports-ports (master):

cargo-c: update to 0.9.5

Fixes: #63848