Mercurial > masqmail

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

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 5cecc214afc9
children
line wrap: on
line source

Howto link masqmail statically?
-------------------------------

With gcc (don't know anything about other compilers), you simply
build masqmail with:

	LDFLAGS=-static make -e


On Debian GNU/Linux, I received a bunch warnings of that kind:

	interface.o: In function `init_sockaddr':
	interface.c:55: warning: Using 'gethostbyname' in statically
	linked applications requires at runtime the shared libraries
	from the glibc version used for linking

On NetBSD I no warnings were printed.

I don't have enough knowledge to tell the reasons and implications.
Maybe you can.



meillo