[MacPorts] #46621: Update: lua 5.3.0
MacPorts
noreply at macports.org
Tue Sep 15 12:39:01 PDT 2015
#46621: Update: lua 5.3.0
-----------------------------+--------------------------------
Reporter: mschamschula@… | Owner: macports-tickets@…
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: lua |
-----------------------------+--------------------------------
Comment (by m7.thon@…):
Replying to [comment:12 mojca@…]:
> ... any port that uses
> {{{
> #include <lua.h>
> }}}
> and tries to use `-L/opt/local/include -L/opt/local/include/lua-5.2`
flags will pick up `lua.h` from `lua`, not from `lua52`. I'm thinking of
trying to temporarily deactivate `lua` before compiling the port and then
activating `lua` again after compilation is done, but I need to remember
how to do that.
This does not sound like a solution to me. How about putting all lua
versions in their own subdirectory, i.e., also /opt/local/include/lua-5.3
? And consequently have no port "lua" at all, but only the (sub-)ports
lua50 lua51 lua52 and lua53 that can be installed in their respective
subdirectories without conflicting?
Clearly, the ports depending on lua would all need to be modified, but at
least this would be a consistent approach. Or how exact is the similar
problem dealt with in the case of python?
--
Ticket URL: <https://trac.macports.org/ticket/46621#comment:14>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list