Date: Fri, 31 Mar 2000 08:47:10 -0800 (PST) From: Nick Sayer <nsayer@quack.kfu.com> To: freebsd-ports@freebsd.org Subject: Tricky porting -- libmcrypt Message-ID: <200003311647.IAA39756@medusa.kfu.com>
next in thread | raw e-mail | index | archive | help
I'm the maintainer of the libmcrypt port, and after much neglect, I am in the throwes of updating the port to 2.4.0 (and there was much rejoicing). Alas, the beast has become far more complicated than it once was. It is now a base library and a collection of modules. It even builds a thing called libltdl which looks like a portable dlopen() type library. I need some porting wisdom as to how to handle this. First, for some bizarre reason libltdl/Makefile defines INSTALL as ../ which breaks 'make install'. None of the other Makefiles seem to suffer this disease, and I'm at a loss to find out what happened. Looking at the source, it does sort of appear that something like either libltdl or a bunch of #defines would be neccessary for libmcrypt to work, but it appears that libltdl is part of libtool, maybe? Should I install this library or not? Should I have some sort of LIBDEPEND for it? Does any other port use it? The 2.4 distfile is at http://hq.hellug.gr/~mcrypt/lib/libmcrypt-2.4.0.tar.gz if anyone wants to see what I see. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003311647.IAA39756>