Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Alex Remily
Yeah. There's a couple tickets that could probably be subsumed by a new one. I'll have a look. On Thu, Jun 16, 2022 at 8:04 PM Gilles Sadowski wrote: > Hello. > > Le jeu. 16 juin 2022 à 19:36, Alex Remily a écrit > : > > > > Do you think we could simply use CRYPTO-120 > >

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Gilles Sadowski
Hello. Le jeu. 16 juin 2022 à 19:36, Alex Remily a écrit : > > Do you think we could simply use CRYPTO-120 > ? Maybe. Or open a new one with an up-to-date description, and signal that it replaces old/obsolete reports... Gilles > On Thu, Jun 16,

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Gary Gregory
I don't think you can do a "full" build with one Docker file. The premise I had back when I did the release, IIRC, was that the macOS binaries had to be built on real mac hardware to be legal. I think I built the Windows binaries on a real Windows PC hardware too and then merged everything together

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Alex Remily
Right. Thanks for the pointer. Ran a quick test on some of the build profiles, and dockerfile-luw is missing dependencies for some of the linux builds, for example: [exec] /bin/sh: 1: aarch64-linux-gnu-gcc: not found That should be an easy fix that I'm happy to do, but to the larger question o

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread sebb
On Thu, 16 Jun 2022 at 18:18, Alex Remily wrote: > > I just ran [2], and whatever it does, it doesn't appear to do a build of > commons-crypto. That's correct; all it does is set up the environment. You have to then run Maven in the container. > I'd appreciate it if any developers who have the

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Alex Remily
Do you think we could simply use CRYPTO-120 ? On Thu, Jun 16, 2022 at 1:31 PM Gilles Sadowski wrote: > Hello. > > Since there is an issue to be solved, could you file a report on JIRA? > [And post there patches or new files, and instructions.] >

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Gilles Sadowski
Hello. Since there is an issue to be solved, could you file a report on JIRA? [And post there patches or new files, and instructions.] Thanks, Gilles Le jeu. 16 juin 2022 à 19:18, Alex Remily a écrit : > > I just ran [2], and whatever it does, it doesn't appear to do a build of > commons-crypto

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Alex Remily
I just ran [2], and whatever it does, it doesn't appear to do a build of commons-crypto. I'd appreciate it if any developers who have the time would take a look at the dockerfile here: https://github.com/aremily/commons-crypto If you're copying the dockerfile into your own fork, you'll need the

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Alex Remily
Interesting. Since I just finished up writing yet a third dockerfile, I'll try running both of them and see what happens. Hopefully, one of them was used to perform the last release and we can just update the build documentation to reflect. On Thu, Jun 16, 2022 at 1:00 PM sebb wrote: > As the

Re: [CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread Jochen Wiedmann
On Thu, Jun 16, 2022 at 7:00 PM sebb wrote: > [1] src/docker/Dockerfile > [2] src/conf/Docker/Dockerfile-luw Have to admit, that I wasn't aware of [2], when I created [1]. Mine is incomplete, and can easily be removed. Was basically just an attempt to reproduce the build instructions in the hope

[CRYPTO] Multiple Docker files - are they both needed?

2022-06-16 Thread sebb
As the subject says: are the following both needed? [1] src/docker/Dockerfile [2] src/conf/Docker/Dockerfile-luw [1] uses a more recent version of ubuntu, but every install runs as a separate step, which increases resource usage [2] uses quite an old Ubuntu, and has a non-standard file name Can