Mercurial > masqmail
annotate docs/howto-static-linking @ 392:c5fd796ea06e
Heavy refactoring in parts of conf.c.
init_conf()
parse_boolean()
parse_list_file()
Re-arrangement of code.
parse_address_glob_list()
Removed unneccessary parameter.
parse_list()
parse_interface():
Use strtok()/strchr() instead of doing is all by hand.
Removed limitation of fixed size buffer.
eat_comments()
Use a state machine.
eat_line_trailing()
eat_spaces()
read_lval()
Better structured code.
read_conf()
read_route()
Removed magic numbers.
Made all list type in the config files accept pathname entries,
except for `permanent_routes' and `query_routes.' for which this
is impossible.
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Sat, 18 Feb 2012 18:07:55 +0100 |
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 |