Trying to use libidn in a port but get this error ld: library not found for -lidn

Ben Greenfield ben at cogs.com
Sat Aug 15 09:14:39 PDT 2015


Hello,

Everything I’m working on is research and the first goal is to a repeatable macports install of Prosody. The current Prosody Portfile is for an older version and I’m trying to get an experimental branch to work that can use Lua versions above 5.1.

I’m also using Xcode-beta and on release software. 

I’m working on a Portfile for prosody that can use the Lua 5.2 and I’m issues with libidn. If I manually run make I get these results.

lim# make                                                     
sed "1s| lua$| lua|; \
		s|^CFG_SOURCEDIR=.*;$|CFG_SOURCEDIR='/opt/local/lib/prosody';|; \
		s|^CFG_CONFIGDIR=.*;$|CFG_CONFIGDIR='/opt/local/etc/prosody';|; \
		s|^CFG_DATADIR=.*;$|CFG_DATADIR='/opt/local/var/lib/prosody';|; \
		s|^CFG_PLUGINDIR=.*;$|CFG_PLUGINDIR='/opt/local/lib/prosody/modules/';|;" < prosody > prosody.install
sed "1s| lua$| lua|; \
		s|^CFG_SOURCEDIR=.*;$|CFG_SOURCEDIR='/opt/local/lib/prosody';|; \
		s|^CFG_CONFIGDIR=.*;$|CFG_CONFIGDIR='/opt/local/etc/prosody';|; \
		s|^CFG_DATADIR=.*;$|CFG_DATADIR='/opt/local/var/lib/prosody';|; \
		s|^CFG_PLUGINDIR=.*;$|CFG_PLUGINDIR='/opt/local/lib/prosody/modules/';|;" < prosodyctl > prosodyctl.install
sed 's|certs/|/opt/local/etc/prosody/certs/|' prosody.cfg.lua.dist > prosody.cfg.lua.install
test -e .hg/dirstate && \
		hexdump -n6 -e'6/1 "%02x"' .hg/dirstate > prosody.version || true
test -f prosody.release && \
		cp prosody.release prosody.version || true
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make -C util-src install
gcc -fPIC -Wall -ggdb -I/opt/local/include -c -o encodings.o encodings.c
MACOSX_DEPLOYMENT_TARGET="10.3"; export MACOSX_DEPLOYMENT_TARGET;
gcc -o encodings.so encodings.o -bundle -undefined dynamic_lookup -lidn
ld: library not found for -lidn
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [encodings.so] Error 1
make: *** [all] Error 2

I don’t expect an exact answer but if someone can some ideas of how to diagnose or solve the problem that would be great. 

Thanks,

Ben




More information about the macports-users mailing list