[MacPorts] #63745: virt-viewer @7.0 Failed to build libgcc11: command execution failed

MacPorts noreply at macports.org
Sun Oct 31 16:42:24 UTC 2021


#63745: virt-viewer @7.0 Failed to build libgcc11: command execution failed
--------------------------+-------------------------
 Reporter:  soundpassion  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.7.1
 Keywords:                |       Port:  virt-viewer
--------------------------+-------------------------
 Hi all,

 I must say at the beginning that i'm not a guru in these kind of things so
 please be patient if I ask no sense questions.
 I'm trying to install virt-viewer port [https://ports.macports.org/port
 /virt-viewer/] on macOS Monterey 12.0.1 on a mac mini M1.
 I followed the guide on this link [https://www.macports.org/install.php]
 before to execute the installation command for virt-viewer port.

 I got an error during the installation of virt-viewer port on libgcc11
 build execution, I already checked "Problem Hotlist" and did port clean).

 ''Error: Failed to build libgcc11: command execution failed
 Error: See
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log
 for details.
 Error: Follow https://guide.macports.org/#project.tickets if you believe
 there is a bug.
 Error: Processing of port virt-viewer failed''

 Looking into the main.log file I see:

 {{{
 :info:build checking whether the C compiler works... yes
 :info:build checking for C compiler default output file name... a.out
 :info:build checking for suffix of executables...
 :info:build checking whether we are cross compiling... configure: error:
 in
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/arm64
 -apple-darwin21/libgomp':
 :info:build configure: error: cannot run C compiled programs.
 :info:build If you meant to cross compile, use `--host'.
 :info:build See `config.log' for more details
 :info:build make[2]: *** [configure-stage1-target-libgomp] Error 1
 :info:build make[2]: Leaving directory
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build'
 :info:build make[1]: *** [stage1-bubble] Error 2
 :info:build make[1]: Leaving directory
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build'
 :info:build make: *** [bootstrap-lean] Error 2
 :info:build make: Leaving directory
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build'
 :info:build Command failed:  cd
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build"
 && /usr/bin/make -j8 -w bootstrap-lean
 :info:build Exit code: 2
 :error:build Failed to build libgcc11: command execution failed
 :debug:build Error code: CHILDSTATUS 42664 2
 :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"
 }}}

 and looking into config.log I see

 {{{
 configure:5205: checking whether g++ accepts -static-libstdc++ -static-
 libgcc
 configure:5222: /usr/bin/clang++ -arch arm64 -o conftest -pipe -Os
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
 -I/opt/local/include
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
 -L/opt/local/lib -Wl,-headerpad_max_install_names
 -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
 -static-libstdc++ -static-libgcc conftest.cpp  >&5
 clang: error: unsupported option '-static-libgcc'
 configure:5222: $? = 1
 configure: failed program was:
 | /* confdefs.h */
 | #define PACKAGE_NAME ""
 | #define PACKAGE_TARNAME ""
 | #define PACKAGE_VERSION ""
 | #define PACKAGE_STRING ""
 | #define PACKAGE_BUGREPORT ""
 | #define PACKAGE_URL ""
 | /* end confdefs.h.  */
 |
 | #if (__GNUC__ < 4) || (__GNUC__ == 4 && __GNUC_MINOR__ < 5)
 | #error -static-libstdc++ not implemented
 | #endif
 | int main() {}
 }}}

 I read old threads on the web regarding gcc and Clang but they were
 referring to old OSX versions so I'm not sure that was the same case..
 Anyway this is the output of gcc --version command:

 {{{
 Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
 --with-gxx-include-
 dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
 Apple clang version 13.0.0 (clang-1300.0.29.3)
 Target: arm64-apple-darwin21.1.0
 Thread model: posix
 InstalledDir:
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
 }}}

 I attach both main.log and config.log files.

 Thank you in advance for your support.

 Best regards

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


More information about the macports-tickets mailing list