Date: Thu, 27 Aug 1998 11:27:52 +0200 From: Sheldon Hearn <axl@iafrica.com> To: freebsd-ports@FreeBSD.ORG Subject: lynx w/ SSLeay working: crypto.h diff Message-ID: <7602.904210072@axl.training.iafrica.com>
next in thread | raw e-mail | index | archive | help
Hi folks, Disclaimer: I'm not a hacker. I managed to get something to work by guessing, and now I'm offering to share the fruits of my guesswork. ;) I got lynx-2.8 working with SSLeay-0.8.1b on a -STABLE machine last night. I used the ports tree to fetch and build both, having applied to lynx-2.8 the SSL patch found at http://www.moxienet.com/lynx/ . The lynx build required only two changes. The first, which I understand, was to point to the correct include directory to find the installed SSLeay include files. The lynx-2.8 SSL patch assumes that SSLeay's base dir is /usr/local/ssl instead of /usr/local. The second, which I don't understand, was prompted by parse errors (attached below) in SSLeay's crypto.h during the patched lynx-2.8 build. I guessed up a tiny modification to crypto.h (diff attached below) and the lynx-2.8 build completed successfully. That is to say that the compiled binary seems to browse stuff in HTTPS URLs correctly. I am hoping someone here will be able to clarify what's going on. I can think of these possible explanations and associated action to take for each: 1) lynx-2.8 as built from ports does / does not define some small option that influences the way header files are parsed (perhaps -DNOPROTO). I should report my findings to the lynx port maintainer. 2) The SSLeay-0.8.1b port does not correctly tailor crypto.h for FreeBSD. I should report my findings to the SSLeay port maintainer. 3) Something local to my machine influences the lynx-2.8 build in such a way as to break the SSL support patches. I should investigate my system. 4) SSL support for lynx-2.8 is a gimmick that nobody actually cares about. I shouldn't worry about it if it's working for me. I spent a lot of time searching the archives on this one, so if you're going to tell me that this has been discussed already, I'd appreciate some tips on how to find the appropriate thread, not just STFW. Thanks for your time, Sheldon. -------- lynx-2.8 w/ SSL support build errors: >> Checksum OK for lynx2-8.zip. ===> Building for lynx-2.8 cd WWW/Library/unix && make CC="cc" LY_CFLAGS="-O3 -m486 -pipe" CPPFLAGS="" LYFLAGS="-DUSE_SSL -I/usr/local/include" cc -c -o ../../Library/unix/HTTP.o -DHAVE_CONFIG_H -DUSE_SSL -I/usr/local/include -I../../.. -I../../../src -I../../.. -I../../../src -O3 -m486 -pipe -DUSE_SSL -I/usr/local/include -I../../../WWW/Library/Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH ../../../WWW/Library/Implementation/HTTP.c In file included from ../../../WWW/Library/Implementation/HTTP.c:16: /usr/local/include/crypto.h:187: parse error before `free_func' /usr/local/include/crypto.h:187: parse error before `)' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -------- SSLeay crypto.h diff: --- /usr/local/include/crypto.h.ORIG Wed Aug 26 17:43:47 1998 +++ /usr/local/include/crypto.h Wed Aug 26 18:31:52 1998 @@ -184,7 +184,7 @@ char *CRYPTO_get_lock_name(int type); int CRYPTO_add_lock(int *pointer,int amount,int type, char *file,int line); -void CRYPTO_set_mem_functions(char *(*m)(),char *(*r)(), void (*free_func)()); +void CRYPTO_set_mem_functions(char *(*m)(),char *(*r)(), void (*f)()); void CRYPTO_get_mem_functions(char *(**m)(),char *(**r)(), void (**f)()); char *CRYPTO_malloc(int num); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7602.904210072>