lang/lua: It does need gmake.

Matthias Andree mandree at FreeBSD.org
Fri Mar 16 18:18:52 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 15.03.2012 20:50, schrieb Jeremy Messenger:
> I get a build failure on amd64:
> 
> ---------------------------------
> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_'
> can not be used when making a shared object; recompile with -fPIC
> lapi.o: could not read symbols: Bad value
> *** Error code 1
> ---------------------------------
> 
> I got it fixed by add USE_GMAKE=yes in the Makefile and now I can get
> it built ok. If you compare the build log between make and gmake. You
> will see it has different output. This
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/162279 has broken it.
> 
> May I commit it by add USE_GMAKE=yes back in?

Jeremy,

rather not -- let's not add dependencies if we can help it;

MAKE_ARGS= CFLAGS="${CFLAGS}"

seems to do the trick for me (I could reproduce your problem on 9-STABLE
amd64).

I've committed that (without bumping port revision) after short
discussion with Niclas and some Tinderbox and "port test" smoke tests,
please let us know if it doesn't help.

I suppose the issue is that GNU make passes variables from environment
in a different way than BSD make does, or CFLAGS are assembled in a
different way, but I lack the time to investigate before end of March.
Since stuffing CFLAGS onto the command line helps, I think we should be
fine though.

Feel free to shed some light and/or investigate.

Best regards
Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk9jg/4ACgkQvmGDOQUufZWMoACg0maMPVq0vYhk9fq+vOHB8+TG
ua8AoIp6CzQ8/kBunjja1V8pL0q9Ae66
=ITMi
-----END PGP SIGNATURE-----


More information about the freebsd-ports mailing list