Timshel Knoll <[EMAIL PROTECTED]> writes:
> I've had a request for a libnettle package in Debian.
Ah, that's cool.
> However, the problem is that nettle only builds as a static library
> ... which isn't really an ideal situation. I've changed nettle's
> build system to use libtool, a trivial but useful change, IMHO. The
> patch is attached ...
Given the size of Nettle, I don't think it's a big problem to link it
statically, but I agree that having shared libraries too would be
nice.
> All you should need to do is apply the patch, run "libtoolize
> --copy",
I'm not really on friendly terms with libtool, but this is not the
place to go into details (mail me privately if you want to discuss
that).
Would you consider hacking it to generate ELF shared libraries
directly, without libtool? For an example on how to do that, look at
adns (available on the GNU mirrors).
To make it work right (no matter of one uses libtool or not), one
would also need to have a second look at the assembler files to make
sure that they're pure, I think the sparc code is ok (at least the
current version, a while ago I fixed a bug that made it crash if
loaded dynamically) but I'm not so sure about the x86 code. Or simply
disable the assembler code when building the shared library.
> I've also added an AC_PREREQ(2.50) since you are using the
> AC_HELP_STRING macro, which only exists in >= 2.50 versions, and
> Debian's autoconf automatically selects whether to run 2.13 or 2.50
> based on whether there is a AC_PREREQ(2.50)
That's fixed in the current version (included with recent lsh). I
guess that means that I ought to make a new standalone Nettle release.
Thanks,
/Niels
PS. I'm soon going away for two weeks, so don't expect quick answers
to mail.
