I have confirmation from another user that it *did* now build
successfully. What version of this package are you using? If it's
1.4.17-1004 rather than 1.4.17-1005, your selfupdate did not yet pick
up the latest fixes.
dan
On Wed, 3 Oct 2012 12:47:45 +1000, Andrew Buckeridge
On Tue, 02 Oct 2012 21:06:21 -0700
Alexander Hansen alexanderk.han...@gmail.com wrote:
On 10/2/12 7:47 PM, Andrew Buckeridge wrote:
Did selfupdate, but build of msmtp-ssl still failed due to change in API
of openssl100-dev which is apparently now fixed upstream.
If API is deprecated
On 10/2/2012 7:59 AM, Andrew Buckeridge wrote:
Did fink self-update and then fink update-all, but it failed.
See attached.
gcc -std=gnu99 -DHAVE_CONFIG_H -DSYSCONFDIR=\/sw/etc\
-DLOCALEDIR=\/sw/share/locale\ -I. -I.. -I../gnulib -I../gnulib
-I/sw/include -g -O2 -MT tls.o -MD -MP -MF
On Tue, 02 Oct 2012 15:13:06 -0400, Hanspeter Niederstrasser
f...@snaggledworks.com wrote:
On 10/2/2012 7:59 AM, Andrew Buckeridge wrote:
Did fink self-update and then fink update-all, but it failed.
See attached.
gcc -std=gnu99 -DHAVE_CONFIG_H -DSYSCONFDIR=\/sw/etc\
Did selfupdate, but build of msmtp-ssl still failed due to change in API
of openssl100-dev which is apparently now fixed upstream.
If API is deprecated then msmtp-ssl could just depend on old
openssl098-dev. Any security or other show stoppers with openssl098-dev?
On Tue, 02 Oct 2012 17:05:44
On 10/2/12 7:47 PM, Andrew Buckeridge wrote:
Did selfupdate, but build of msmtp-ssl still failed due to change in API
of openssl100-dev which is apparently now fixed upstream.
If API is deprecated then msmtp-ssl could just depend on old
openssl098-dev. Any security or other show stoppers
