petterreinholdtsen

[eao197] > It looks like Debian on MIPS lacks not only `std::atomic` but also > `std::thread`. Or there are some specific compiler/linker options for > proper linking with the implementation...

So, how can the issue be solved then?

[eao197] > As I said earlier: > >> Anyway, without an access to that platform, we can't play with >> compiler/linker options. So I have no idea now how this...

[eao197] >> My best idea there is to set up a mipsel instance in qemu. > > Is there any description of how it can be done? A quick search...

Apparently the floor fix broke something. Btw, did you consider divinding by 2.0 instead of casting the value?

Note, https://gitlab.xiph.org/xiph/vorbis/ is the upstream project, I've been told the github repository is a convenience copy. Perhaps it is an idea to submit the patch there?

[ihsinme] > Oh no. I don't have an account there. maybe a better idea would be if > you fix the code there yourself. > do I close PR? I...

A related question is if this github project or the sourceforge project (http://portablesigner.sourceforge.net), the current authorative source for the package?

I was able to compile the source by modifying line 360 in src/net/pflaeging/PortableSigner/PDFSigner.java, replacing sap.setCrypto(GetPKCS12.privateKey, GetPKCS12.certificateChain, null, null); with sap.setCertificate(GetPKCS12.certificateChain[0]); I doubt that change is correct, but have not been...

I notice the commit message for https://github.com/jaapgeurts/PortableSigner2/commit/e6eb6468ac6d07f239868ef63cd4634aaac93e05 claim to update to newer itext version. Perhaps it is related?