[MacPorts] #60053: grass7 build failure utf-8 error with nviz.py

MacPorts noreply at macports.org
Fri Feb 7 16:09:39 UTC 2020


#60053: grass7 build failure utf-8 error with nviz.py
-------------------------+--------------------
  Reporter:  bal-agates  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.2
Resolution:              |   Keywords:
      Port:  grass7      |
-------------------------+--------------------

Comment (by bal-agates):

 Sorry, I didn't capture the main.log.  I think the error message I
 originally included was deceiving.  I suspect poor error handling in the
 build process obfuscated the problem.  I mainly studied the make in
 ../ctypes.  It appears to build a command, run that command in a Python
 subprocess, and capture the output.  I modified the source to see what
 command was issued when the error appears.  The command is in <3a-
 command.txt> and the manually captured output is in <3b-make in
 ctypes.txt>.  The output shows 3 errors.  Search for 'error:'.  All appear
 related to unknown architecture.  I suspect that when compile errors occur
 the compiler is injecting some control characters, possible a return code,
 in the output stream that causes problems with the subprocess output
 capture.

 When I tried building grass7 (7.8.2_1) yesterday I had an existing
 MacPorts tree with many projects built over the last year or two.  I may
 have even attempted to build grass7 before.  Thinking the grass7 build
 problem was file corruption or incompatibility I uninstalled and cleaned
 all MacPort projects and started from scratch.  I got the same build
 error.  I ended up 1) Rebuilding all other projects.  No problems.
 Thinking the problem was with compiler defines I tried 2) using 'port
 select' to set clang=mp-clang-9.0, gcc=mp-gcc9 and llvm=mp-llvm-9.0 and 3)
 I rebooted my computer.  After doing 1-3 grass7 (7.8.2_1) did successfully
 build.  I am not certain exactly what fixed the problem.  My orginal clang
 was /usr/bin/clang (10.0.0) which was part of Xcode.  That seems newer
 than MacPorts clang (9.0.1).  Is there a compiler dependency?

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


More information about the macports-tickets mailing list