Mercurial > 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 | 5cecc214afc9 |
| children |
| rev | line source |
|---|---|
| 202 | 1 Howto link masqmail statically? |
| 2 ------------------------------- | |
| 3 | |
| 4 With gcc (don't know anything about other compilers), you simply | |
| 5 build masqmail with: | |
| 6 | |
| 7 LDFLAGS=-static make -e | |
| 8 | |
| 9 | |
| 10 On Debian GNU/Linux, I received a bunch warnings of that kind: | |
| 11 | |
| 12 interface.o: In function `init_sockaddr': | |
| 13 interface.c:55: warning: Using 'gethostbyname' in statically | |
| 14 linked applications requires at runtime the shared libraries | |
| 15 from the glibc version used for linking | |
| 16 | |
| 17 On NetBSD I no warnings were printed. | |
| 18 | |
| 19 I don't have enough knowledge to tell the reasons and implications. | |
| 20 Maybe you can. | |
| 21 | |
| 22 | |
| 23 | |
| 24 meillo |