On Thu, Feb 04, 2016 at 08:24:52AM +0100, László Böszörményi (GCS) wrote: > On Thu, Feb 4, 2016 at 6:37 AM, Adam Borowski <kilob...@umbar.angband.pl> > wrote: > > Source: libcrypto++ > > Version: 5.6.1-9 > > > > libcrypto++ currently fails to build on x32. This is caused by attempts to > > use x86 assembly -- the package would build if it used the portable generic > > code instead. > Thanks for your patch! I do resend it to the actual upstream > maintainer for information. On the other hand, you may check the > v5.6.3 in experimental which builds and according to the self tests > working right on x32.
Oif, I did not notice. If that's already done, then unless 5.6.3 won't hit unstable anytime soon, I wasted some time. I'm quite confused though. As Jeffrey asked me recently about installation on x32 VMs, I assumed the porting needed to be done, but now, looking in upstream git, I see the porting work was already complete by that time. Looks like my fault for starting with what's in Debian unstable rather than current upstream code. -- A tit a day keeps the vet away.
