at build time.
Some distributions have ways to get all the build-dependencies for a
particular package which might get you somewhat on the way, but I'd
recommend that you verify that you've actually got -devel packages for
the things you think you do.
--
Lars Viklund | z...@acc.umu.se
ficates***
<--- HTTP/1.1 204 No Content
<--- Server: milton.io-2.0.0
<--- Date: Wed, 03 Dec 2014 07:43:17 GMT
<--- Accept-Ranges: bytes
<--- ETag: "A73292177EA5491A981A6C6C6E7AA862_253383220"
<---
---- Receiving body...
rm ok,
s from 'debug 10'.
You may want to tcpdump/wireshark the traffic and see the actual
request, see if it looks truly malformed, or if it's just the server
being picky?
--
Lars Viklund | z...@acc.umu.se
___
lftp mailing list
lftp@uniyar
ot can you help make a ‘.mod’ file for installation,
> not sure how?
> ___
> lftp mailing list
> lftp@uniyar.ac.ru
> http://univ.uniyar.ac.ru/mailman/listinfo/lftp
--
Lars Viklund | z...@acc.umu.se
___
lftp mailing list
lftp@uniyar.ac.ru
http://univ.uniyar.ac.ru/mailman/listinfo/lftp
" that should be used when putting this together?
>
> Thanks
>
> Steven
> ___
> lftp mailing list
> lftp@uniyar.ac.ru
> http://univ.uniyar.ac.ru/mailman/listinfo/lftp
--
Lars Viklund | z...@acc.umu.se
___
lftp mailing list
lftp@uniyar.ac.ru
http://univ.uniyar.ac.ru/mailman/listinfo/lftp
Hi,
Among other things, OpenSSL 1.1 apparently turns all previously
inspectable structs opaque.
They now require you to hold them by pointer, use accessor functions to
access their fields, and use the new/free functions to make/destroy them.
A quick Bing search revealed this wiki page:
https
