Re: cvs commit: src/secure/lib/libcrypto Makefile.inc

2002-11-08 Thread Ruslan Ermilov
Upgrades from RELENG_4 and pre-"static __sF" systems should be working again. On Fri, Nov 08, 2002 at 04:47:51AM -0800, Ruslan Ermilov wrote: > ru 2002/11/08 04:47:51 PST > > Modified files: > secure/lib/libcrypto Makefile.inc > Log: > DON'T EVER PUT THIS BACK! > > Pointy

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Satoshi - Ports Wraith - Asami
* From: Kris Kennaway <[EMAIL PROTECTED]> * It may be useful - although there are a lot of inconsistencies in how the * openssl ports look for it. Dirk Froemberg was going to help with this - * I'm not sure exactly what the best way to do it is. For example, ports * like w3m-ssl pass the loc

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Jim Bloom
Here is the sequence I used for installing thing yesterday when I had the problem. First, I cvsup'ed and did a make world. Next, I installed the rsaref-2.0 port. Finally, I tried to make the lynx-ssl port. The basic problem is that some of the include files are not being found (ssl.h and crypt

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Manfred Antar
At 12:50 PM 1/17/00 -0800, Kris Kennaway wrote: >On Mon, 17 Jan 2000, Jim Bloom wrote: > > > Add lynx-ssl to the list of ports which are broken on current. This was > > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > > world. > >Well, that makes a list of one. Can you pr

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Kris Kennaway
On Mon, 17 Jan 2000, Jim Bloom wrote: > Add lynx-ssl to the list of ports which are broken on current. This was > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > world. Well, that makes a list of one. Can you provide more information (e.g. a transcript?) Are you using

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Jim Bloom
Add lynx-ssl to the list of ports which are broken on current. This was as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make world. Jim Bloom [EMAIL PROTECTED] Kris Kennaway wrote: > > On 17 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > > > Should I add some stuff to ha

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Kris Kennaway
On 17 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > Should I add some stuff to handle the differences in bsd.port.mk (like > we did with perl5)? It may be useful - although there are a lot of inconsistencies in how the openssl ports look for it. Dirk Froemberg was going to help with this - I

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Chris Piazza
On Mon, Jan 17, 2000 at 07:06:55AM -0800, Satoshi - Ports Wraith - Asami wrote: > * From: Kris Kennaway <[EMAIL PROTECTED]> > > * Openssl should now be fully functional for both US and international users > * - please report any problems you have in using it to me. You should be > * able to c

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-17 Thread Satoshi - Ports Wraith - Asami
* From: Kris Kennaway <[EMAIL PROTECTED]> * Openssl should now be fully functional for both US and international users * - please report any problems you have in using it to me. You should be * able to compile all openssl-using code (some of them require rsaref and * therefore cannot be used

Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile

2000-01-15 Thread Kris Kennaway
On Sat, 15 Jan 2000, Kris Kennaway wrote: > Support RSA via RSAref. This autodetects the RSAref package, and if it > is not found, compiles without RSA. Openssl should now be fully functional for both US and international users - please report any problems you have in using it to me. You sho