using zlib, or find out how could I solve the "connection refused
problem", I have no idea why that happens and can't find information about this
exact problem. Any ideas?
Thanks,
Mihai
--
Mihai Militaru
___
freebsd-ports
The solution I found was to copy and compile in my source:
crypto/comp/c_zlib.c, from the openssl source tree (extracting the
distfile) and include that in the sources that require it. It is a bit
dirty, but in the end it is the same thing as creating my zlib BIOs,
except that I don't create them m
suppose to maintain. They are only interested in the
> > > > >> statistics generated by their unprofessional ports, but not
> > > > >> in their quality.
> >
> > QED ***
>
> Indeed!
>
> To qu
;
> -Warren Block * Rapid City, South Dakota USA
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> Return-Path:
> X-Flags: 1000
> Delivered
--
Mihai Militaru
_
that it
builds both libraries or is it mandatory to make a separate build for
FIP by modifying the makefile in such way to use the existing
libs/header in the other port, instead of rebuilding?
I'm talking about doing and submitting it to the collection.
Cheers,
Mihai
