Adjust CFLAGS to pick bundled speex instead of one installed on the system, that is,
apparently, incompatible with the bundled one.
A similar fix was already done for games/ioquake3 in r398218.
PR: 203389
or completing missions. Use your earnings to buy a better ship or
to upgrade the weapons and engines on your current one. Blow up
pirates. Take sides in a civil war. Or leave human space behind and
hope to find some friendly aliens whose culture is more civilized
than your own...
Endless Sky is a sandbox-style space exploration game similar to
Elite, Escape Velocity, or Star Control. You start out as the captain
of a tiny space ship and can choose what to do from there. The game
includes a major plot line and many minor missions, but you can
choose whether you want to play through the plot or strike out on
your own as a merchant or bounty hunter or explorer.
WWW: http://endless-sky.github.io/
- Support multiple values in *_OLD_CMD, i.e. we can now fix both "/usr/bin/python" and "/usr/bin/env python" at the same time
- Default *_OLD_CMD values are now always appended, so you don't need to specify them in individual ports
- Add lua support (depends on USES=lua)
- Add more default values, such as "/usr/bin/env foo" for python, perl, bash, ruby and lua
- Shebangfix now matches whole words, e.g. we will no longer (erroneously) replace "/usr/bin/perl5.005" with "${perl_CMD}5.005" (but "/usr/bin/perl -tt" is still (correctly) replaced with "${perl_CMD} -tt")
Note that *_OLD_CMD items containing spaces must now be quoted (e.g. perl_OLD_CMD=/bin/perl /usr/bin/perl "/usr/bin/env perl")
Update shebangfix usage according to new rules in many ports:
- Remove *_OLD_CMD for patterns now replaced by default
- Quote custom *_OLD_CMD which contain spaces
Fix shebangfix usage in many ports (irrelevant to infrastructure change):
- Remove redundant SHEBANG_LANG (no need to duplicate default langs)
- Remove redundant *_CMD (such as python_CMD=${LOCALBASE}/bin/python${PYTHON_VER} when USES=python is present)
- Never use *_OLD_CMD in REINPLACE_CMD matchers, these should always look for exact string
Approved by: portmgr (bapt)
Differential Revision: D3756
The use of "$(prefix)" in the configure file seems not to be
understand. On FreeBSD, it's ignored but it actually causes failures
on DragonFly. I suspect these flags aren't actually used.
If it turns out they are used, and support for non-standard PREFIX
(not /usr/local) is desired, the REINPLACE_CMD macro can adjust
/usr/local with in a post-patch target.
