[MacPorts] #62580: swig fails test suite on Lion

[MacPorts]

#62580: swig fails test suite on Lion
-------------------------------+-------------------------
  Reporter:  RobK88            |      Owner:  michaelld
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.6.4
Resolution:                    |   Keywords:  Lion Hamlib
      Port:  swig swig-python  |
-------------------------------+-------------------------

Comment (by RobK88):

 Replying to [comment:12 kencu]:
 >
 > Now you might need to compromise a bit; it is not trivial to run
 multiple different make sessions in one MacPorts build. It's just not set
 up that way. So can you live with just one of the python bindings? or have
 a variant for either python2 or python3?

 Yes, I can live with Macports building hamlib with just the python 3
 bindings.  Better yet, update the hamlib port so one can choose between
 two the variants - hamlib with either the python2 bindings or the python3
 bindings.

 P.S.  My initial approach was to build hamlib with just python3 bindings
 using python 3.9.  I tried doing that by changing the "python" command
 from python 2 to python 3 (i.e.  sudo port select --set python python39 ).
 That does not seem to work either using Macports or manually from source.
 It looks like Macports cannot find the symbols for "swig" when python 3 is
 being used.  (In contrast, Macports can find the symbols for "swig" when
 python 2 is being used).

 If you can figure out how to get Macports to build hamlib with python3
 bindings that would be fantastic!

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