This just means you have not installed the binary to where the original copy of the lynx browser is located on the system (you need root to do that).
You can use the binary you built in your home directory; if you put ~/bin in your PATH and allow lynx to find a lynx.cfg file you will be able to use your new lynx. ./lynx -version will confirm your build with ssl ./lynx -cfg ./lynx.cfg will start the new copy of the browser. __Stef http://caunter.ca/contact.html On Tue, 15 Mar 2005, Joel Salomon wrote: > On Tue, 15 Mar 2005 21:12:35 -0500, Joel Salomon <[EMAIL PROTECTED]> wrote: > > Thanks, it's working. > > > Spoke too soon: > Alert!: This client does not contain support for HTTPS URLs. > > I'm sure I missed something trivial, but I don't see it handy in the archives. > > --Joel > > > _______________________________________________ > Lynx-dev mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lynx-dev > _______________________________________________ Lynx-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lynx-dev
