Merge branch 'vendor/GDTOA'
[dragonfly.git] / contrib / ldns / README
CommitLineData
b9b3af22
JL
1
2Contents:
3 REQUIREMENTS
4 INSTALLATION
5 libdns
6 examples
7 drill
8 INFORMATION FOR SPECIFIC OPERATING SYSTEMS
9 Mac OS X
10 Solaris
435c04e0 11 Your Support
b9b3af22
JL
12
13Project page:
14http://www.nlnetlabs.nl/ldns/
15On that page you can also subscribe to the ldns mailing list.
16
17* Development
18ldns is mainly developed on Linux and FreeBSD. It is regularly tested to
19compile on other systems like Solaris and Mac OS X.
20
21REQUIREMENTS
22- OpenSSL (Optional, but needed for features like DNSSEC)
23- libpcap (Optional, but needed for examples/ldns-dpa)
24- (GNU) libtool (in OSX, that's glibtool, not libtool)
25- GNU make
26
27INSTALLATION
281. Unpack the tarball
292. cd ldns-<VERSION>
303. ./configure
314. gmake (it needs gnu make to compile, on systems where GNU make is the
32 default you can just use 'make')
335. sudo gmake install
346. Optional. (cd examples; ./configure; gmake), make example programs included.
357. Optional. (cd drill; ./configure; gmake; gmake install), to build drill.
36
37You can configure and compile it in a separate build directory.
38
39* Examples
40There are some examples and dns related tools in the examples/ directory.
41These can be built with:
421. cd examples/
432. ./configure [--with-ldns=<path to ldns installation or build>]
443. gmake
45
46* Drill
47Drill can be built with:
481. cd drill/
492. ./configure [--with-ldns=<path to ldns installation or build>]
503. gmake
51
52Note that you need to set LD_LIBRARY_PATH if you want to run the binaries
53and you have not installed the library to a system directory. You can use
54the make target all-static for the examples to run them if you don't want to
55install the library.
56
57
58* Building from subversion repository
59
60If you are building from the repository you will need to have (gnu)
61autotools like libtool and autoreconf installed. A list of all the commands
62needed to build everything can be found in README.svn. Note that the actual
63commands may be a little bit different on your machine. Most notable, you'll need to run libtoolize (or glibtoolize), if you skip this step, you'll get an error about missing config.sub.
64
65* Developers
66ldns is developed by the ldns team at NLnet Labs. This team currently
67consists of:
b9b3af22 68 o Wouter Wijngaards
435c04e0 69 o Matthijs Mekking
b9b3af22
JL
70
71Former main developers:
435c04e0 72 o Jelte Jansen
b9b3af22
JL
73 o Miek Gieben
74
75* Credits
76We have received patches from the following people, thanks!
77 o Erik Rozendaal
78 o Håkan Olsson
79 o Jakob Schlyter
80 o Paul Wouters
81 o Simon Vallet
82 o Ondřej Surý
83
84
85IFORMATION FOR SPECIFIC OPERATING SYSTEMS
86
87MAC OS X
88
89For MACOSX 10.4 and later, it seems that you have to set the
90MACOSX_DEPLOYMENT_TARGET environment variable to 10.4 before running
91make. Apparently it defaults to 10.1.
92
93This appears to be a known problem in 10.2 to 10.4, see:
94http://developer.apple.com/qa/qa2001/qa1233.html
95for more information.
96
97
98SOLARIS
99
100In Solaris multi-architecture systems (that have both 32-bit and
10164-bit support), it can be a bit taxing to convince the system to
102compile in 64-bit mode. Jakob Schlyter has kindly contributed a build
103script that sets the right build and link options. You can find it in
104contrib/build-solaris.sh
105
435c04e0
JL
106
107Your Support
108NLnet Labs offers all of its software products as open source, most are
109published under a BDS license. You can download them, not only from the
110NLnet Labs website but also through the various OS distributions for
111which NSD, ldns, and Unbound are packaged. We therefore have little idea
112who uses our software in production environments and have no direct ties
113with 'our customers'.
114
115Therefore, we ask you to contact us at users@NLnetLabs.nl and tell us
116whether you use one of our products in your production environment,
117what that environment looks like, and maybe even share some praise.
118We would like to refer to the fact that your organization is using our
119products. We will only do that if you explicitly allow us. In all other
120cases we will keep the information you share with us to ourselves.
121
122In addition to the moral support you can also support us
123financially. NLnet Labs is a recognized not-for-profit charity foundation
124that is chartered to develop open-source software and open-standards
125for the Internet. If you use our software to satisfaction please express
126that by giving us a donation. For small donations PayPal can be used. For
127larger and regular donations please contact us at users@NLnetLabs.nl. Also
128see http://www.nlnetlabs.nl/labs/contributors/.
129