[MacPorts] #57032: mozjs52 @52.6.0, mozjs60 @60.1.0: Target C compiler target CPU (unknown) does not match --target CPU (powerpc)

MacPorts noreply at macports.org
Fri Aug 23 21:56:16 UTC 2019


#57032: mozjs52 @52.6.0, mozjs60 @60.1.0: Target C compiler target CPU (unknown)
does not match --target CPU (powerpc)
-------------------------------+----------------------
  Reporter:  ballapete         |      Owner:  dbevans
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.5.3
Resolution:                    |   Keywords:  powerpc
      Port:  mozjs52, mozjs60  |
-------------------------------+----------------------

Comment (by khepler):

 The config script detects arch fine when run outside of Macports:
 {{{
 [xserve:mozjs-52.6.0gnome1/js/src] kris% sudo -u macports ./configure
 Creating Python environment
 New python executable in
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mozjs52/mozjs52/work/mozjs-52.6.0gnome1/_virtualenv/bin/python
 Installing setuptools, pip, wheel...done.
 running build_ext
 copying build/lib.macosx-10.5-ppc-2.7/psutil/_psutil_osx.so -> psutil
 copying build/lib.macosx-10.5-ppc-2.7/psutil/_psutil_posix.so -> psutil

 Reexecuting in the virtualenv
 checking for a shell... /bin/sh
 checking for host system type... powerpc-apple-darwin9.8.0
 checking for target system type... powerpc-apple-darwin9.8.0
 checking for the Android toolchain directory... not found
 checking whether cross compiling... no
 checking for pkg_config... /opt/local/bin/pkg-config
 checking for pkg-config version... 0.29.2
 checking for yasm... not found
 checking for android platform directory... no
 checking for the target C compiler... /opt/local/bin/clang
 checking whether the target C compiler can be used... yes
 checking the target C compiler version... 3.4.2
 checking the target C compiler works... yes
 checking for the target C++ compiler... /opt/local/bin/clang++
 checking whether the target C++ compiler can be used... no
 DEBUG: <truncated - see config.log for full output>
 DEBUG: | #elif __linux__
 DEBUG: | %KERNEL "Linux"
 DEBUG: | #elif _WIN32 || __CYGWIN__
 DEBUG: | %KERNEL "WINNT"
 DEBUG: | #elif __NetBSD__
 DEBUG: | %KERNEL "NetBSD"
 DEBUG: | #elif __APPLE__
 DEBUG: | %KERNEL "Darwin"
 DEBUG: | #endif
 DEBUG: | #if _MSC_VER || __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
 DEBUG: | %ENDIANNESS "little"
 DEBUG: | #elif __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
 DEBUG: | %ENDIANNESS "big"
 DEBUG: | #endif
 DEBUG: Executing: `/opt/local/bin/clang++ -std=gnu++11 -E
 /tmp/conftest.PmEJ4p.cpp`
 DEBUG: COMPILER = clang
 DEBUG: cplusplus = 201103L
 DEBUG: CPU = ppc
 DEBUG: KERNEL = Darwin
 DEBUG: ENDIANNESS = big
 ERROR: Only clang/llvm 3.6 or newer is supported.
 [xserve:mozjs-52.6.0gnome1/js/src] kris%
 }}}

 I don't believe the macros the script looks for are GCC macros; they seem
 to be defined by python.  I tested GCC v4.2-apple, v4.9-mp, v5-mp, v6-mp
 and v7-mp and none of them defined those macros.  I'm still investigating,
 but right now it looks like there's no issue with Mozilla's configure
 script, but there's an incompatibility with Apple's python2.7 while
 Macports' python2.7 works.

-- 
Ticket URL: <https://trac.macports.org/ticket/57032#comment:20>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list