Opened 3 years ago
Last modified 3 years ago
#62991 closed defect
m4 @ 1.4.19+universal Failed to configure — at Version 13
Reported by: | FaradayLight (Faraday Light) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | arm64 bigsur | Cc: | larryv (Lawrence Velázquez) |
Port: | m4 |
Description (last modified by larryv (Lawrence Velázquez))
M4 failed to configure reporting the following error:
Error: Failed to configure m4: configure failure: command execution failed
The error is created after performing the following:
sudo port clean m4 sudo port upgrade m4
The error was first detected by running the following:
sudo port upgrade gnutls
Thus gnutls is also affected.
Change History (17)
Changed 3 years ago by FaradayLight (Faraday Light)
Attachment: | config.log added |
---|
comment:1 Changed 3 years ago by FaradayLight (Faraday Light)
From the config.log:
configure:6336: checking whether the compiler is clang configure:6358: /usr/bin/clang -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 -arch x86_64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5 conftest.c:13:12: error: unknown type name 'barfbarf'
comment:2 Changed 3 years ago by leavenode
1.4.19 just failed to build on Tiger. 1.4.18 is working fine. gnutls upgraded and installed just fine.
From the build log for 1.4.19
:info:build make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19/lib' :info:build depbase=`echo sigsegv.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\ :info:build /opt/local/bin/gcc-apple-4.2 -std=gnu99 -I. -I/opt/local/include -pipe -Os -arch ppc -MT sigsegv.o -MD -MP -MF $depbase.Tpo -c -o sigsegv.o sigsegv.c &&\ :info:build mv -f $depbase.Tpo $depbase.Po :info:build sigsegv.c: In function 'sigsegv_handler': :info:build sigsegv.c:938: error: 'struct mcontext' has no member named '__ss' :info:build make[3]: *** [sigsegv.o] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19/lib' :info:build make[2]: *** [all] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19/lib' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19" && /usr/bin/make -j1 -w all :info:build Exit code: 2 :error:build Failed to build m4: command execution failed :debug:build Error code: CHILDSTATUS 9996 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" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/main.log for details.
comment:3 follow-up: 8 Changed 3 years ago by kencu (Ken)
the Tiger thing is different -- I think I know what will fix that.
comment:4 Changed 3 years ago by jmroot (Joshua Root)
Are your Command Line Tools perhaps outdated? See wiki:ProblemHotlist#reinstall-clt
comment:5 Changed 3 years ago by FaradayLight (Faraday Light)
Hi, No I checked that the tools where up today and ran the upgrade after a 'clean' to make sure, but I still got the reported error.
I have also since run 'port diagnose' but that has returned a blank.
This is the version number I get from running the check on the CLT receipt: 12.5.0.0.1.1617976050
comment:6 Changed 3 years ago by FaradayLight (Faraday Light)
Having said that, I have just run the pkgutil check without the filter and get the following:
tacitus@malory templates_dev % pkgutil --pkg-info=com.apple.pkg.CLTools_Executables --pkg-info=com.apple.pkg.CLTools_Base --pkg-info=com.apple.pkg.DeveloperToolsCLI --pkg-info=com.apple.pkg.DeveloperToolsCLILeo package-id: com.apple.pkg.CLTools_Executables version: 12.5.0.0.1.1617976050 volume: / location: / install-time: 1622292831 groups: com.apple.FindSystemFiles.pkg-group No receipt for 'com.apple.pkg.CLTools_Base' found at '/'. No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'. No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
I have been installing Xcode updates via App Store.
From - pkgutil --pkgs | grep CL - I get this list:
com.apple.pkg.CLTools_Executables com.apple.pkg.CLTools_SDK_macOS110 com.apple.pkg.CLTools_SDK_macOS1015 com.apple.pkg.CLTools_macOS_SDK
comment:7 Changed 3 years ago by FaradayLight (Faraday Light)
Using the -v switch on another upgrade attempt I get these entries:
checking whether POSIX threads API is available... yes checking whether setlocale (LC_ALL, NULL) is multithread-safe... no checking whether setlocale (category, NULL) is multithread-safe... yes checking whether imported symbols can be declared weak... no checking host CPU and C ABI... grep: conftest.s: No such file or directory arm
checking whether C symbols are prefixed with underscore at the linker level... ggrep: conftest.s: No such file or directory no
checking whether iswblank is declared... no checking whether iswdigit is ISO C compliant... no checking whether iswxdigit is ISO C compliant... ./configure: line 38230: test: !=: unary operator expected ./configure: line 38230: test: !=: unary operator expected guessing yes
checking whether malloc (0) returns nonnull... (cached) no checking whether mbrtowc handles incomplete characters... ./configure: line 39070: test: !=: unary operator expected ./configure: line 39108: test: !=: unary operator expected guessing yes checking whether mbrtowc works as well as mbtowc... guessing yes checking whether mbrtowc handles a NULL pwc argument... ./configure: line 39267: test: !=: unary operator expected guessing yes checking whether mbrtowc handles a NULL string argument... ./configure: line 39340: test: !=: unary operator expected guessing yes checking whether mbrtowc has a correct return value... ./configure: line 39403: test: !=: unary operator expected ./configure: line 39403: test: !=: unary operator expected guessing yes checking whether mbrtowc returns 0 when parsing a NUL character... guessing yes checking whether mbrtowc stores incomplete characters... ./configure: line 39662: test: !=: unary operator expected guessing no
checking whether sleep is declared... no checking for socklen_t... no checking for socklen_t equivalent... configure: error: Cannot find a type to use in place of socklen_t Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_m4/m4/work/m4-1.4.19" && ./configure --prefix=/opt/local --disable-dependency-tracking --disable-silent-rules --program-prefix=g --with-packager=MacPorts --with-packager-version="revision 1" --with-packager-bug-reports=https://trac.macports.org/wiki/Tickets ac_cv_libsigsegv=no Exit code: 1
comment:8 Changed 3 years ago by kencu (Ken)
Replying to kencu:
the Tiger thing is different -- I think I know what will fix that.
Off topic but I have Tiger fixed so we can forget about that comment here.
comment:9 Changed 3 years ago by FaradayLight (Faraday Light)
There is another machine I have access to:
MacBook Pro 16inch, 2019
macOS 11.4
Xcode 12.5
macOS SDK 20.4
M4 upgraded to 1.4.19 without issue on this machine.
comment:10 Changed 3 years ago by jmroot (Joshua Root)
Cc: | larryv added |
---|
comment:11 follow-up: 12 Changed 3 years ago by ryanmcgrath (Ryan McGrath)
I experience the same configure errors on a 2020 M1 MBP - macOS 11.4, Xcode 12.5, reinstalled command line tools recently as well.
The inability to install this +universal is a bit of a sticking point as it blocks a number of other packages. I spent some time looking into it but unfortunately have no real clue what's up - it builds and runs fine if I grab the source and jump through the steps myself, though.
Changed 3 years ago by ryanmcgrath (Ryan McGrath)
Attachment: | config.2.log added |
---|
Extra debugging logs, if it helps.
Changed 3 years ago by ryanmcgrath (Ryan McGrath)
Attachment: | main.2.log added |
---|
comment:12 Changed 3 years ago by larryv (Lawrence Velázquez)
Sorry for the trouble, but I have access to neither Big Sur nor an
Apple Silicon machine. Do you experience the same issue non-universally
(e.g., sudo port clean m4 && sudo port configure m4
)?
Replying to ryanmcgrath:
The inability to install this +universal is a bit of a sticking point as it blocks a number of other packages.
What other ports require m4
, a port that installs no libraries,
to be universal?
comment:13 Changed 3 years ago by larryv (Lawrence Velázquez)
Description: | modified (diff) |
---|
config.log