[MacPorts] #62580: swig fails test suite on Lion
MacPorts
noreply at macports.org
Tue Mar 30 16:15:55 UTC 2021
#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 kencu):
well -- progress!
But once again, your easiest way to success is likey going to be to sort
out how to put the proper args into the MacPorts hamlib Portfile rather
than try to redo all the configuration yourself. I suggest you don't
export a PYTHONPATH, don't install into /usr/local, and don't try to
duplicate a huge amount of MacPorts setup.
For example -- Josh Root has put about -- I won't guess how many hours --
into setting up all the python setup scripts so they properly find the
right parts during a build. This is very complicated!
Even just the compilers need setup, and that is trivial to do -- look at
what you found on your own:
{{{
Preprocessor gcc -E
C Compiler gcc -g -O2
C++ Compiler g++ -g -O2
}}}
There is no way that trying to build much of anything with gcc and g++ is
going to work on MacOS, especially not on 10.7 where we almost certainly
need some newer compiler.
So let's figure out the options you need for python3 and try to get that
working.
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?
--
Ticket URL: <https://trac.macports.org/ticket/62580#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list