masqmail

annotate docs/howto-static-linking @ 421:f37384470855

Changed lockdir to /var/lock/masqmail; Create lockdir and piddir on startup. Moved the lockdir out of the spool dir. (When /var/lock is a ramdisk we do well to have the lock files there.) Added the new configure option --with-lockdir to change that location. Nontheless, if we run_as_user, then lock files are always stored in the spool dir directly. Instead of installing the lockdir and piddir at installation time, we create them on startup time now if they are missing. This is necessary if lockdir or piddir are a tmpfs.
author markus schnalke <meillo@marmaro.de>
date Wed, 30 May 2012 09:38:38 +0200
parents
children
rev   line source
meillo@202 1 Howto link masqmail statically?
meillo@202 2 -------------------------------
meillo@202 3
meillo@202 4 With gcc (don't know anything about other compilers), you simply
meillo@202 5 build masqmail with:
meillo@202 6
meillo@202 7 LDFLAGS=-static make -e
meillo@202 8
meillo@202 9
meillo@202 10 On Debian GNU/Linux, I received a bunch warnings of that kind:
meillo@202 11
meillo@202 12 interface.o: In function `init_sockaddr':
meillo@202 13 interface.c:55: warning: Using 'gethostbyname' in statically
meillo@202 14 linked applications requires at runtime the shared libraries
meillo@202 15 from the glibc version used for linking
meillo@202 16
meillo@202 17 On NetBSD I no warnings were printed.
meillo@202 18
meillo@202 19 I don't have enough knowledge to tell the reasons and implications.
meillo@202 20 Maybe you can.
meillo@202 21
meillo@202 22
meillo@202 23
meillo@202 24 meillo