Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    JAMNNTPD    |    Support for the JAMNNTPD software client    |    2,630 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 268 of 2,630    |
|    Björn Felten to Scott Street    |
|    xlat bug?    |
|    27 Jun 12 20:23:21    |
       BF>> when I tried to compile under Windows.               SS> Ok, I've finally gotten it.               Me too. But it was a six hour long hazzle.               First I tried my old GCC install. Didn't work.               Then I tried installing the latest version of it from the DJGPP site. A       real ordeal to select what packages I needed. Didn't work either.               Then I remembered that I installed MinGW by the time I played with the       JamNNTPd source. Now, *that* was much easier than going via DJGPP. The GUI       installer automatically downloaded and isntalled all the packages I needed.               Success! Kinda... A gazillion or so warnings, most of them complaining       about uchar <-> char errors.               Well, I made a global search and replace for uchar to char in all *.c and       *.h files (including those in Björn Stenberg's jamlib subdir). Now it was easy       to find the two places where the uchar was typedef:ed and delete them all. To       make sure I didn't break anything I added the compiler directive       -funsigned-char to the two makefiles (one in src and one in jamlib).               Now I only had three (I think) warnings left -- variables never used.       Deleted.               WOW! A totally clean compile!               SS> In fact, this is the first post using my        SS> Windows 2003 based point - AND - JamNNTPd compiled with SMAPI and        SS> OpenSSL enabled!               I then tried your SMAPI version (1.1). Of course it didn't compile. So much       for C portability. :)               Well, I downloaded the latest smapi package from sourceforge and installed       it in a subdir -- smapi -- under src. Compiled it with the mgw makefile and       got a libsmapimgw.a file. In Makefile.win32 in src I changed line 21 to:               $(CC) -o jamnntpd$(EXESUFFIX) $(OBJS) smapi/libsmapimgw.a -lwsock32               And whaddaya know? It compiled! But then I once again have all the       warnings. I don't think I will go for the SMAPI version -- the resulting EXE       file is twice as big as the Stenberg version.               SS> I did peek at your server, headers transferred fast enough               Thanks. I haven't been able to test it remotely for a long time. Your       feedback highly is appreciated.               SS> - Its crazy that you have messages that are that old.               LOL! Yes, isn't it? I myself just *love* crazy people... 8-)              --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125        * Origin: news://felten.yi.org (2:203/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca