>> Why don't you create a libmcrypt.a and statically link it into your
>> nsca, thereby not requiring mcrypt as an external library at runtime?
>
> That's actually a good question.
> Sadly I have a 128kb size limit on files I can deploy via the
> mechanism we use. A statically linked send_nsca is roundabout 600k.
> Sadly I cannot link _only_ libmcrypt statically, it's all or
> nothing - or my gcc-fu is just too weak, who knows
>
It's your ld-fu that's weak. Basically, you can treat an ar-archive
as an object file when liking them together. That way you can choose
which libraries to link statically and which to link dynamically.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]