From jelte at NLnetLabs.nl Thu Jan 5 14:18:34 2006 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Thu, 05 Jan 2006 15:18:34 +0100 Subject: [ldns-users] ldns-1.0.1 release announcement Message-ID: <43BD2ABA.1040704@NLnetLabs.nl> Hi, we have released ldns-1.0.1 a bugfix release for 1.0. You can get it at http://www.nlnetlabs.nl/ldns We are working hard on ldns-1.1, which will probably be the next release. Most important changes since 1.0.0: 03 Jan 2006: 1.0.1: ldns-team * BUG #110 fixed: drill now handles unreachable servers gracefully * BUG #109 fixed: Don't include i386 .o files in the distr. tar file Miek & Jelte NLnetLabs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature URL: From xdtrq at ananzi.co.za Tue Jan 10 21:20:30 2006 From: xdtrq at ananzi.co.za (T kyer) Date: Tue, 10 Jan 2006 23:20:30 +0200 Subject: [ldns-users] Build On Windows Message-ID: Hi again I applaud your efforts to promote open source software. Unfortunately much as I dislike proprietary software I'm stuck with windows for the present. This may change in the future. Although I'm trying to use as much open source software within the Windows environment as possible as evidenced by the use of Dev-cpp instead of MSVC++, the fact is I have personally found open/free source code to be a disadvantage within the C language windows environment as much of it is compiled with the proprietary libraries within MSVC making it almost impossible to use with open source compilers such as gcc without investing great effort and time. Even so I am committed to open source. It is the way of the future and will leave the dinosaurs soon behind. As a side note I will continue to periodically check whether the email posting "black hole" has transformed into a wormhole that delivers my email postings to the appropriate address. Please inform me from your end if you have found the solution to the problem. It's too bad as this discussion is not being posted to the archives for the benefit of other ldns users. Sorry to have taken so long in answering back, but I was considering your last email. I had to look at the source code for ldns, and ponder as to the best way to proceed to compile the source. I came to the conclusion and please correct me if I'm wrong that it would be best to split the source into two separate packages. The very first thing to try compiling would be DRILL in order to first port this software to windows successfully. I will try to build a static library in the form of libDRILL.a that is compatible with the gcc compiler. After it has been successfully compiled the static library then can be linked to build the remaining source code. I will need your support if this is to be a successful endeavour. Following please find the compile log for the static library build of DRILL: WITH MAKEFILE Compiler: Default compiler Executing make... make.exe -f "Makefile.in" all process_begin: CreateProcess((null), CC@ @CFLAGS@ @LDFLAGS@ -o drill drill.o drill_util.o error.o root.o work.o chasetrace.o dnssec.o @LIBS@, ...) failed. make (e=2): The system cannot find the file specified. make.exe: *** [drill] Error 2 Execution terminated WITHOUT MAKEFILE Compiler: Default compiler Building Makefile: "F:\New Folder (6)\Makefile.win" Executing make... make.exe -f "F:\New Folder (6)\Makefile.win" all ar r Project1.a work.o dnssec.o drill.o drill_util.o error.o root.o chasetrace.o ar: creating Project1.a ranlib Project1.a Execution terminated Do let me know your thoughts. Thnx Tom From miekg at atoom.net Wed Jan 11 09:12:09 2006 From: miekg at atoom.net (Miek Gieben) Date: Wed, 11 Jan 2006 10:12:09 +0100 Subject: [ldns-users] Build On Windows In-Reply-To: References: Message-ID: <20060111091209.GA7563@atoom.net> [On 10 Jan, @22:20, T kyer wrote in "[ldns-users] Build On Windows ..."] > As a side note I will continue to periodically check > whether the email posting "black hole" has transformed into > a wormhole that delivers my email postings to the It looks like everything is in working order. Sadly I don't know exactly why your mails weren't coming through. > correct me if I'm wrong that it would be best to split the > source into two separate packages. We would like it very much for ldns to work natively on Windows. But note that I have very limited knowledge of the windows api. > The very first thing to try compiling would be DRILL in > order to first port this software to windows successfully. I think this is a good way to start, but I don't follow you all the way through. You want to build drill as a library? Let me try to write down the ldns lib. structure: We have ldns - which is of course the library. This is pure C with little dependencies, except libc. The only problem will be the networking/socket interface in net.c On top of ldns we have built drill. Drill is also very simple, so drill should compile on windows, but it will then fail to link because the ldns library isn't yet ported. Having said that, any compilation problems you will find in drill should/may also apply to ldns. > I will try to build a static library in the form of > libDRILL.a that is compatible with the gcc compiler. After > it has been successfully compiled the static library then > can be linked to build the remaining source code. I will > need your support if this is to be a successful endeavour. > > Following please find the compile log for the static > library build of DRILL: > > > WITH MAKEFILE > > Compiler: Default compiler > Executing make... > make.exe -f "Makefile.in" all > process_begin: CreateProcess((null), CC@ @CFLAGS@ @LDFLAGS@ > -o drill drill.o drill_util.o error.o root.o work.o > chasetrace.o dnssec.o @LIBS@, ...) failed. > make (e=2): The system cannot find the file specified. > make.exe: *** [drill] Error 2 Execution terminated I can only guess here that it cannot find the ldns library? Looking at the output, I see that the .o object files are created. This would mean that the compilation of drill has succeeded. > WITHOUT MAKEFILE > > Compiler: Default compiler > Building Makefile: "F:\New Folder (6)\Makefile.win" > Executing make... > make.exe -f "F:\New Folder (6)\Makefile.win" all > ar r Project1.a work.o dnssec.o drill.o drill_util.o > error.o root.o chasetrace.o ar: creating Project1.a ranlib > Project1.a Execution terminated I don't know what make.exe does under windows without a Makefile... What happens if you do this with ldns? -- grtz, - Miek http://www.miek.nl http://www.nlnetlabs.nl key fingerprint: 6A3C F450 6D4E 7C6B C23C F982 258B 85CF 3880 D0F6 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From jelte at NLnetLabs.nl Wed Jan 11 09:16:32 2006 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Wed, 11 Jan 2006 10:16:32 +0100 Subject: [ldns-users] Build On Windows In-Reply-To: <20060111091209.GA7563@atoom.net> References: <20060111091209.GA7563@atoom.net> Message-ID: <43C4CCF0.6070303@NLnetLabs.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >>WITH MAKEFILE >> >>Compiler: Default compiler >>Executing make... >>make.exe -f "Makefile.in" all >>process_begin: CreateProcess((null), CC@ @CFLAGS@ @LDFLAGS@ >>-o drill drill.o drill_util.o error.o root.o work.o >>chasetrace.o dnssec.o @LIBS@, ...) failed. >>make (e=2): The system cannot find the file specified. >>make.exe: *** [drill] Error 2 Execution terminated > > > I can only guess here that it cannot find the ldns library? Looking > at the output, I see that the .o object files are created. This would > mean that the compilation of drill has succeeded. > - From the command line there i gather that you are using Makefile.in directly as a make file, while it should only be the input file from which the Makefile itself is generated (by the configure script) Is this so? And if so, does configure run? (or should Make.exe do that automatically?) If not, you could try to copy the Makefile.in to a new Makefile and edit all values between the @ signs, Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDxMzv4nZCKsdOncURArKaAKC7ADj+jWYtuXP16mmgrDiE2KSv+wCgtlbA vCwBHi82lmcKkBb3I36NKyk= =BDay -----END PGP SIGNATURE----- From jelte at NLnetLabs.nl Wed Jan 11 09:49:44 2006 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Wed, 11 Jan 2006 10:49:44 +0100 Subject: [ldns-users] Build On Windows In-Reply-To: <43C4CCF0.6070303@NLnetLabs.nl> References: <20060111091209.GA7563@atoom.net> <43C4CCF0.6070303@NLnetLabs.nl> Message-ID: <43C4D4B8.4090608@NLnetLabs.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > - From the command line there i gather that you are using Makefile.in > directly as a make file, while it should only be the input file from > which the Makefile itself is generated (by the configure script) > > Is this so? And if so, does configure run? (or should Make.exe do that > automatically?) If not, you could try to copy the Makefile.in to a new > Makefile and edit all values between the @ signs, > By the way, on linux, if you have successfully run ./configure in ldns and ./configure --with-ldns=../ in the drill/ directory (in ldns-1.0.1) you can statically compile drill with the command gcc -I . -I .. -lssl *.c ../*.c ../compat/*.c -o drill (in the drill/ directory) This does require that the openssl library is installed. If something like this even works, you will probably run into a lot of compiler errors (for starters, as miek has said, the network API in windows is very different than on other systems), but it might get you started. (configures are needed because some .h files are also generated by it) Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDxNS44nZCKsdOncURAkB7AKC6D7DO0QoUY+ut8/+3ruDVnoiPAwCgwpGP aYBBfs6p+1WIwSoB8eO8SNQ= =MR22 -----END PGP SIGNATURE-----