On Fri, 1 Jul 2022 at 16:33, Alex Remily wrote:
>
> be shown in the Crypto main output.>
Now committed; seems to work on all 3 main OSes.
> I like the approach. I wrote most of the version code that you're
> touching, and your refactoring is more elegant.
Thanks, but I'm not sure I have done
I like the approach. I wrote most of the version code that you're
touching, and your refactoring is more elegant. I hadn't written much C
since school, so I kind of hacked my way through it. It works, but
definitely room for improvement. At first glance it appears that your
approach would be
Well, not fix the warnings since these are in generated code but it
would be nice to avoid polluting the build output just for generate
code warnings while keeping warnings for our main code...
Gary
On Fri, Jul 1, 2022 at 8:21 AM Gary Gregory wrote:
>
> Not a release blocker but a FTR TODO to
Not a release blocker but a FTR TODO to fix these Javadoc warnings:
[INFO] --- maven-javadoc-plugin:3.3.2:javadoc (default-cli) @
commons-configuration2 ---
[INFO] No previous run data found, generating javadoc.
[INFO]
100 warnings
[WARNING] Javadoc Warnings
[WARNING]
On Fri, 1 Jul 2022 at 04:16, Bernd Eckenfels wrote:
>
> The Java.library.path controls the Java side loadLibrary() but that worked
> since it loaded the commons-crypto JNI lib.
>
> The dlopen In that shim searches various places, including PATH.
According to dlopen(3) it does not search PATH,
