Re: [crypto] New Release
On Fri, Jul 24, 2020 at 8:04 PM Alex Remily wrote: > I'd recommend using MinGW. I installed it through brew on my Mac and cross > compiled the windows build with little difficulty. I expect a similar > experience on Linux. The MinGW install contains all the necessary windows > headers. > Yep, that's what I use: MSYS_NT-10.0-16299 *** 3.1.6-340.x86_64 2020-07-17 05:52 UTC x86_64 Msys Gary > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory wrote: > > > Thanks Geoffrey, > > > > Are you available at some point to do a webex to straighten out my local > > set up? Just email me directly so we can coordinate. > > > > Gary > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake < > geoffrey.w.bl...@gmail.com > > > > > wrote: > > > > > Hi Gary, > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > Windows I've found out, the FS is case-insensitive. This is not true > > > on a Linux box though. I submitted a new PR to fix this and get > > > Windows builds working again on a Linux box, as well as testing that > > > windows artifacts will still build via Travis. Hopefully this can > > > unstick the release as you can now cross-compile everything save the > > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > > > -Geoff > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory > > > wrote: > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > geoffrey.w.bl...@gmail.com> > > > > wrote: > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via > virtualbox > > > > > and vagrant, but it looks like the windows build is broken. There > > are > > > > > typos trying to include "Windows.h" which should be "windows.h" to > > > > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > > header, > > > > for example, on my machine: > > > > > > > > C:\Program Files (x86)\Windows > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > ? > > > > > > > > Gary > > > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > > between Linux and windows headers. I won't be able to get to > trying > > > > > to fix and submit any PRs on these this week or next. But anyone > who > > > > > wants to try cross-compiling, here are the packages I installed to > > get > > > > > up and running minimally on Ubuntu: > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > sudo apt-get install libssl-dev git > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab > the > > > > > 3.6 tarball from apache. > > > > > > > > > > -Geoff > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily > > > > wrote: > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is > largely > > > > > > unfamiliar to me, so not sure how far I'll get even if I have the > > > time > > > > > > to look at it. > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > wrote: > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > > Makefile > > > > > > > and saw this above the win64 target: > > > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > > g++-mingw-w64-x86-64 > > > > > package > > > > > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > > > 16.04LTS > > > > > > > box. Or even a 14.04 box if necessary. Anybody have the time > to > > > try? > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily < > > alex.rem...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > > > compile on > > > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > > > > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > > > > : > > > > > > > > > > > > > > > > //#define inline __inline; > > > > > > > > > > > > > > > > I never did learn why it was there in the first place, but > the > > > broken > > > > > > > > build was originally reported as > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > > > > > > > Now I'm wondering if it may have had something to do with > > > > > > > > cross-compiling for the build. > > > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Is there anything needed to help move this release along? > > > From the > > > > > > > > > looks of the Makefile, Windows was using GCC. I don't > think > > > the > > > > > > > > > compiler is going to have much of an impact since the JNI > > > bindings > > > > > are > > > > > > > > > simply calling through to
Re: [crypto] New Release
There is a docker Maven plugin: io.fabric8 docker-maven-plugin 0.33.0 Gary On Sat, Jul 25, 2020, 00:20 Geoffrey Blake wrote: > Docker would be great. Next question, can that be integrated into > Maven for automating these releases that someone knows offhand? > > -Geoff > > On Fri, Jul 24, 2020 at 7:50 PM Alex Remily wrote: > > > > Sounds like a great idea. > > > > On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote: > > > > > Is it possible to cross-compile from Linux to MacOS? > > > > > > Even if it isn't, might be a good idea to write a docker image to do > > > the other cross-builds; then from a Mac you can build the MacOS binary > > > and call docker to build all the others. > > > > > > On Fri, Jul 24, 2020 at 5:04 PM Alex Remily > wrote: > > > > > > > > I'd recommend using MinGW. I installed it through brew on my Mac and > > > cross > > > > compiled the windows build with little difficulty. I expect a > similar > > > > experience on Linux. The MinGW install contains all the necessary > > > windows > > > > headers. > > > > > > > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory > > > wrote: > > > > > > > > > Thanks Geoffrey, > > > > > > > > > > Are you available at some point to do a webex to straighten out my > > > local > > > > > set up? Just email me directly so we can coordinate. > > > > > > > > > > Gary > > > > > > > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake < > > > geoffrey.w.bl...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > Hi Gary, > > > > > > > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > > > > Windows I've found out, the FS is case-insensitive. This is not > true > > > > > > on a Linux box though. I submitted a new PR to fix this and get > > > > > > Windows builds working again on a Linux box, as well as testing > that > > > > > > windows artifacts will still build via Travis. Hopefully this > can > > > > > > unstick the release as you can now cross-compile everything save > the > > > > > > OSX shared-lib on one box by pointing Maven to the proper > targets. > > > > > > > > > > > > -Geoff > > > > > > > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory < > > > garydgreg...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > > > > geoffrey.w.bl...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via > > > virtualbox > > > > > > > > and vagrant, but it looks like the windows build is broken. > > > There > > > > > are > > > > > > > > typos trying to include "Windows.h" which should be > "windows.h" > > > to > > > > > > > > > > > > > > > > > > > > > > Are you sure that this include is not referring the to > Microsoft > > > > > header, > > > > > > > for example, on my machine: > > > > > > > > > > > > > > C:\Program Files (x86)\Windows > > > > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > > > > > > > ? > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > compile with mingw and redefined macros that I think are > mixing > > > > > > > > between Linux and windows headers. I won't be able to get to > > > trying > > > > > > > > to fix and submit any PRs on these this week or next. But > > > anyone who > > > > > > > > wants to try cross-compiling, here are the packages I > installed > > > to > > > > > get > > > > > > > > up and running minimally on Ubuntu: > > > > > > > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > > > > sudo apt-get install libssl-dev git > > > > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just > grab > > > the > > > > > > > > 3.6 tarball from apache. > > > > > > > > > > > > > > > > -Geoff > > > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily < > > > alex.rem...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is > > > largely > > > > > > > > > unfamiliar to me, so not sure how far I'll get even if I > have > > > the > > > > > > time > > > > > > > > > to look at it. > > > > > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at > the > > > > > Makefile > > > > > > > > > > and saw this above the win64 target: > > > > > > > > > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > > > > > g++-mingw-w64-x86-64 > > > > > > > > package > > > > > > > > > > > > > > > > > > > > We could potentially build everything but MacOS on 1 > Ubuntu > > > > > > 16.04LTS > > > > > > > > > > box. Or even a 14.04 box if necessary. Anybody have the > > >
Re: [crypto] New Release
I don't see why it couldn't. I don't think OSX images are publicly accessible in Docker Hub though, and if not we'd need a Mac as the base machine to run the build. From the base machine we should be able to call docker using the Maven exec plugin, use docker to pull in the desired linux arch host, and configure that host to cross compile the Windows build using MinGW. Thoughts? I'm convalescing this weekend so I should have some time to try it out. Alex On Sat, Jul 25, 2020 at 12:21 AM Geoffrey Blake wrote: > > Docker would be great. Next question, can that be integrated into > Maven for automating these releases that someone knows offhand? > > -Geoff > > On Fri, Jul 24, 2020 at 7:50 PM Alex Remily wrote: > > > > Sounds like a great idea. > > > > On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote: > > > > > Is it possible to cross-compile from Linux to MacOS? > > > > > > Even if it isn't, might be a good idea to write a docker image to do > > > the other cross-builds; then from a Mac you can build the MacOS binary > > > and call docker to build all the others. > > > > > > On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote: > > > > > > > > I'd recommend using MinGW. I installed it through brew on my Mac and > > > cross > > > > compiled the windows build with little difficulty. I expect a similar > > > > experience on Linux. The MinGW install contains all the necessary > > > windows > > > > headers. > > > > > > > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory > > > wrote: > > > > > > > > > Thanks Geoffrey, > > > > > > > > > > Are you available at some point to do a webex to straighten out my > > > local > > > > > set up? Just email me directly so we can coordinate. > > > > > > > > > > Gary > > > > > > > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake < > > > geoffrey.w.bl...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > Hi Gary, > > > > > > > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > > > > Windows I've found out, the FS is case-insensitive. This is not > > > > > > true > > > > > > on a Linux box though. I submitted a new PR to fix this and get > > > > > > Windows builds working again on a Linux box, as well as testing that > > > > > > windows artifacts will still build via Travis. Hopefully this can > > > > > > unstick the release as you can now cross-compile everything save the > > > > > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > > > > > > > > > -Geoff > > > > > > > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory < > > > garydgreg...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > > > > geoffrey.w.bl...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via > > > virtualbox > > > > > > > > and vagrant, but it looks like the windows build is broken. > > > There > > > > > are > > > > > > > > typos trying to include "Windows.h" which should be "windows.h" > > > to > > > > > > > > > > > > > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > > > > > header, > > > > > > > for example, on my machine: > > > > > > > > > > > > > > C:\Program Files (x86)\Windows > > > > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > > > > > > > ? > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > > > > > between Linux and windows headers. I won't be able to get to > > > trying > > > > > > > > to fix and submit any PRs on these this week or next. But > > > anyone who > > > > > > > > wants to try cross-compiling, here are the packages I installed > > > to > > > > > get > > > > > > > > up and running minimally on Ubuntu: > > > > > > > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > > > > sudo apt-get install libssl-dev git > > > > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab > > > the > > > > > > > > 3.6 tarball from apache. > > > > > > > > > > > > > > > > -Geoff > > > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily < > > > alex.rem...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is > > > largely > > > > > > > > > unfamiliar to me, so not sure how far I'll get even if I have > > > the > > > > > > time > > > > > > > > > to look at it. > > > > > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > > > > > Makefile > > > > > > > > > > and saw this above the win64 target: > > > > > > > > > >
Re: [crypto] New Release
Docker would be great. Next question, can that be integrated into Maven for automating these releases that someone knows offhand? -Geoff On Fri, Jul 24, 2020 at 7:50 PM Alex Remily wrote: > > Sounds like a great idea. > > On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote: > > > Is it possible to cross-compile from Linux to MacOS? > > > > Even if it isn't, might be a good idea to write a docker image to do > > the other cross-builds; then from a Mac you can build the MacOS binary > > and call docker to build all the others. > > > > On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote: > > > > > > I'd recommend using MinGW. I installed it through brew on my Mac and > > cross > > > compiled the windows build with little difficulty. I expect a similar > > > experience on Linux. The MinGW install contains all the necessary > > windows > > > headers. > > > > > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory > > wrote: > > > > > > > Thanks Geoffrey, > > > > > > > > Are you available at some point to do a webex to straighten out my > > local > > > > set up? Just email me directly so we can coordinate. > > > > > > > > Gary > > > > > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake < > > geoffrey.w.bl...@gmail.com > > > > > > > > > wrote: > > > > > > > > > Hi Gary, > > > > > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > > > Windows I've found out, the FS is case-insensitive. This is not true > > > > > on a Linux box though. I submitted a new PR to fix this and get > > > > > Windows builds working again on a Linux box, as well as testing that > > > > > windows artifacts will still build via Travis. Hopefully this can > > > > > unstick the release as you can now cross-compile everything save the > > > > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > > > > > > > -Geoff > > > > > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory < > > garydgreg...@gmail.com> > > > > > wrote: > > > > > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > > > geoffrey.w.bl...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via > > virtualbox > > > > > > > and vagrant, but it looks like the windows build is broken. > > There > > > > are > > > > > > > typos trying to include "Windows.h" which should be "windows.h" > > to > > > > > > > > > > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > > > > header, > > > > > > for example, on my machine: > > > > > > > > > > > > C:\Program Files (x86)\Windows > > > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > > > > > ? > > > > > > > > > > > > Gary > > > > > > > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > > > > between Linux and windows headers. I won't be able to get to > > trying > > > > > > > to fix and submit any PRs on these this week or next. But > > anyone who > > > > > > > wants to try cross-compiling, here are the packages I installed > > to > > > > get > > > > > > > up and running minimally on Ubuntu: > > > > > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > > > sudo apt-get install libssl-dev git > > > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab > > the > > > > > > > 3.6 tarball from apache. > > > > > > > > > > > > > > -Geoff > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily < > > alex.rem...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is > > largely > > > > > > > > unfamiliar to me, so not sure how far I'll get even if I have > > the > > > > > time > > > > > > > > to look at it. > > > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > > > > Makefile > > > > > > > > > and saw this above the win64 target: > > > > > > > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > > > > g++-mingw-w64-x86-64 > > > > > > > package > > > > > > > > > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > > > > > 16.04LTS > > > > > > > > > box. Or even a 14.04 box if necessary. Anybody have the > > time to > > > > > try? > > > > > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily < > > > > alex.rem...@gmail.com > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > > > > > compile on > > > > > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [crypto] New Release
Sounds like a great idea. On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote: > Is it possible to cross-compile from Linux to MacOS? > > Even if it isn't, might be a good idea to write a docker image to do > the other cross-builds; then from a Mac you can build the MacOS binary > and call docker to build all the others. > > On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote: > > > > I'd recommend using MinGW. I installed it through brew on my Mac and > cross > > compiled the windows build with little difficulty. I expect a similar > > experience on Linux. The MinGW install contains all the necessary > windows > > headers. > > > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory > wrote: > > > > > Thanks Geoffrey, > > > > > > Are you available at some point to do a webex to straighten out my > local > > > set up? Just email me directly so we can coordinate. > > > > > > Gary > > > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake < > geoffrey.w.bl...@gmail.com > > > > > > > wrote: > > > > > > > Hi Gary, > > > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > > Windows I've found out, the FS is case-insensitive. This is not true > > > > on a Linux box though. I submitted a new PR to fix this and get > > > > Windows builds working again on a Linux box, as well as testing that > > > > windows artifacts will still build via Travis. Hopefully this can > > > > unstick the release as you can now cross-compile everything save the > > > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > > > > > -Geoff > > > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory < > garydgreg...@gmail.com> > > > > wrote: > > > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > > geoffrey.w.bl...@gmail.com> > > > > > wrote: > > > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via > virtualbox > > > > > > and vagrant, but it looks like the windows build is broken. > There > > > are > > > > > > typos trying to include "Windows.h" which should be "windows.h" > to > > > > > > > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > > > header, > > > > > for example, on my machine: > > > > > > > > > > C:\Program Files (x86)\Windows > > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > > > ? > > > > > > > > > > Gary > > > > > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > > > between Linux and windows headers. I won't be able to get to > trying > > > > > > to fix and submit any PRs on these this week or next. But > anyone who > > > > > > wants to try cross-compiling, here are the packages I installed > to > > > get > > > > > > up and running minimally on Ubuntu: > > > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > > sudo apt-get install libssl-dev git > > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab > the > > > > > > 3.6 tarball from apache. > > > > > > > > > > > > -Geoff > > > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily < > alex.rem...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is > largely > > > > > > > unfamiliar to me, so not sure how far I'll get even if I have > the > > > > time > > > > > > > to look at it. > > > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > > wrote: > > > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > > > Makefile > > > > > > > > and saw this above the win64 target: > > > > > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > > > g++-mingw-w64-x86-64 > > > > > > package > > > > > > > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > > > > 16.04LTS > > > > > > > > box. Or even a 14.04 box if necessary. Anybody have the > time to > > > > try? > > > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily < > > > alex.rem...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > > > > compile on > > > > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > > > > > : > > > > > > > > > > > > > > > > > > //#define inline __inline; > > > > > > > > > > > > > > > > > > I never did learn why it was there in the first place, but > the > > > > broken > > > > > > > > > build was originally reported as > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > > > > > > > > > Now I'm wondering if it may have
Re: [crypto] New Release
Is it possible to cross-compile from Linux to MacOS? Even if it isn't, might be a good idea to write a docker image to do the other cross-builds; then from a Mac you can build the MacOS binary and call docker to build all the others. On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote: > > I'd recommend using MinGW. I installed it through brew on my Mac and cross > compiled the windows build with little difficulty. I expect a similar > experience on Linux. The MinGW install contains all the necessary windows > headers. > > On Fri, Jul 24, 2020, 7:16 PM Gary Gregory wrote: > > > Thanks Geoffrey, > > > > Are you available at some point to do a webex to straighten out my local > > set up? Just email me directly so we can coordinate. > > > > Gary > > > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake > > > > wrote: > > > > > Hi Gary, > > > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > > Windows I've found out, the FS is case-insensitive. This is not true > > > on a Linux box though. I submitted a new PR to fix this and get > > > Windows builds working again on a Linux box, as well as testing that > > > windows artifacts will still build via Travis. Hopefully this can > > > unstick the release as you can now cross-compile everything save the > > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > > > -Geoff > > > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory > > > wrote: > > > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > > geoffrey.w.bl...@gmail.com> > > > > wrote: > > > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox > > > > > and vagrant, but it looks like the windows build is broken. There > > are > > > > > typos trying to include "Windows.h" which should be "windows.h" to > > > > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > > header, > > > > for example, on my machine: > > > > > > > > C:\Program Files (x86)\Windows > > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > > > ? > > > > > > > > Gary > > > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > > between Linux and windows headers. I won't be able to get to trying > > > > > to fix and submit any PRs on these this week or next. But anyone who > > > > > wants to try cross-compiling, here are the packages I installed to > > get > > > > > up and running minimally on Ubuntu: > > > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > > sudo apt-get install libssl-dev git > > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab the > > > > > 3.6 tarball from apache. > > > > > > > > > > -Geoff > > > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily > > > wrote: > > > > > > > > > > > > I'll see if I have any time this weekend, but this part is largely > > > > > > unfamiliar to me, so not sure how far I'll get even if I have the > > > time > > > > > > to look at it. > > > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > > wrote: > > > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > > Makefile > > > > > > > and saw this above the win64 target: > > > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > > g++-mingw-w64-x86-64 > > > > > package > > > > > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > > > 16.04LTS > > > > > > > box. Or even a 14.04 box if necessary. Anybody have the time to > > > try? > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily < > > alex.rem...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > > > compile on > > > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > > > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > > > > : > > > > > > > > > > > > > > > > //#define inline __inline; > > > > > > > > > > > > > > > > I never did learn why it was there in the first place, but the > > > broken > > > > > > > > build was originally reported as > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > > > > > > > Now I'm wondering if it may have had something to do with > > > > > > > > cross-compiling for the build. > > > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Is there anything needed to help move this release along? > > > From the > > > > > > > > > looks of the Makefile, Windows was using GCC. I don't think > > > the > > > > > > > > > compiler is going to have much of an impact since the JNI >
Re: [crypto] New Release
I'd recommend using MinGW. I installed it through brew on my Mac and cross compiled the windows build with little difficulty. I expect a similar experience on Linux. The MinGW install contains all the necessary windows headers. On Fri, Jul 24, 2020, 7:16 PM Gary Gregory wrote: > Thanks Geoffrey, > > Are you available at some point to do a webex to straighten out my local > set up? Just email me directly so we can coordinate. > > Gary > > On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake > > wrote: > > > Hi Gary, > > > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > > Windows I've found out, the FS is case-insensitive. This is not true > > on a Linux box though. I submitted a new PR to fix this and get > > Windows builds working again on a Linux box, as well as testing that > > windows artifacts will still build via Travis. Hopefully this can > > unstick the release as you can now cross-compile everything save the > > OSX shared-lib on one box by pointing Maven to the proper targets. > > > > -Geoff > > > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory > > wrote: > > > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > > geoffrey.w.bl...@gmail.com> > > > wrote: > > > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox > > > > and vagrant, but it looks like the windows build is broken. There > are > > > > typos trying to include "Windows.h" which should be "windows.h" to > > > > > > > > > > Are you sure that this include is not referring the to Microsoft > header, > > > for example, on my machine: > > > > > > C:\Program Files (x86)\Windows > Kits\10\Include\10.0.17763.0\um\Windows.h > > > > > > ? > > > > > > Gary > > > > > > > compile with mingw and redefined macros that I think are mixing > > > > between Linux and windows headers. I won't be able to get to trying > > > > to fix and submit any PRs on these this week or next. But anyone who > > > > wants to try cross-compiling, here are the packages I installed to > get > > > > up and running minimally on Ubuntu: > > > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > > sudo apt-get install libssl-dev git > > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > > sudo apt-get install openjdk-8-jdk > > > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab the > > > > 3.6 tarball from apache. > > > > > > > > -Geoff > > > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily > > wrote: > > > > > > > > > > I'll see if I have any time this weekend, but this part is largely > > > > > unfamiliar to me, so not sure how far I'll get even if I have the > > time > > > > > to look at it. > > > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > > wrote: > > > > > > > > > > > > I think you're right Alex. I just happened to look at the > Makefile > > > > > > and saw this above the win64 target: > > > > > > > > > > > > # for cross-compilation on Ubuntu, install the > g++-mingw-w64-x86-64 > > > > package > > > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > > 16.04LTS > > > > > > box. Or even a 14.04 box if necessary. Anybody have the time to > > try? > > > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily < > alex.rem...@gmail.com > > > > > > > wrote: > > > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > > compile on > > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > > > : > > > > > > > > > > > > > > //#define inline __inline; > > > > > > > > > > > > > > I never did learn why it was there in the first place, but the > > broken > > > > > > > build was originally reported as > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > > > > > Now I'm wondering if it may have had something to do with > > > > > > > cross-compiling for the build. > > > > > > > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > > > > wrote: > > > > > > > > > > > > > > > > Is there anything needed to help move this release along? > > From the > > > > > > > > looks of the Makefile, Windows was using GCC. I don't think > > the > > > > > > > > compiler is going to have much of an impact since the JNI > > bindings > > > > are > > > > > > > > simply calling through to the OpenSSL library that is already > > > > > > > > precompiled for the environment. > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess < > > xenoam...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > > > > > I have a feeling about both mingw or cygwin build output > > will be > > > > slower > > > > > > > > > than microsoft-visual-studio build output... > > > > > > > > > Just a feeling, but no evidence. > > > > > > > > > > > > > > > > > > Alex
Re: [crypto] New Release
Thanks Geoffrey, Are you available at some point to do a webex to straighten out my local set up? Just email me directly so we can coordinate. Gary On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake wrote: > Hi Gary, > > windows.h/Windows.h/WINDOWS.H are all names for the same file, on > Windows I've found out, the FS is case-insensitive. This is not true > on a Linux box though. I submitted a new PR to fix this and get > Windows builds working again on a Linux box, as well as testing that > windows artifacts will still build via Travis. Hopefully this can > unstick the release as you can now cross-compile everything save the > OSX shared-lib on one box by pointing Maven to the proper targets. > > -Geoff > > On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory > wrote: > > > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake < > geoffrey.w.bl...@gmail.com> > > wrote: > > > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox > > > and vagrant, but it looks like the windows build is broken. There are > > > typos trying to include "Windows.h" which should be "windows.h" to > > > > > > > Are you sure that this include is not referring the to Microsoft header, > > for example, on my machine: > > > > C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\um\Windows.h > > > > ? > > > > Gary > > > > > compile with mingw and redefined macros that I think are mixing > > > between Linux and windows headers. I won't be able to get to trying > > > to fix and submit any PRs on these this week or next. But anyone who > > > wants to try cross-compiling, here are the packages I installed to get > > > up and running minimally on Ubuntu: > > > > > > sudo apt-get install build-essential g++-mingw-w64 > > > gcc-aarch64-linux-gnu libc6-dev-i386 > > > sudo apt-get install libssl-dev git > > > sudo add-apt-repository ppa:openjdk-r/ppa > > > sudo apt-get install openjdk-8-jdk > > > > > > Don't install the Ubuntu supplied maven, its too old. Just grab the > > > 3.6 tarball from apache. > > > > > > -Geoff > > > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily > wrote: > > > > > > > > I'll see if I have any time this weekend, but this part is largely > > > > unfamiliar to me, so not sure how far I'll get even if I have the > time > > > > to look at it. > > > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > > wrote: > > > > > > > > > > I think you're right Alex. I just happened to look at the Makefile > > > > > and saw this above the win64 target: > > > > > > > > > > # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 > > > package > > > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu > 16.04LTS > > > > > box. Or even a 14.04 box if necessary. Anybody have the time to > try? > > > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily > > > > wrote: > > > > > > > > > > > > Not sure if it's relevant or not, but to get the build to > compile on > > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > > : > > > > > > > > > > > > //#define inline __inline; > > > > > > > > > > > > I never did learn why it was there in the first place, but the > broken > > > > > > build was originally reported as > > > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > > > Now I'm wondering if it may have had something to do with > > > > > > cross-compiling for the build. > > > > > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > > > wrote: > > > > > > > > > > > > > > Is there anything needed to help move this release along? > From the > > > > > > > looks of the Makefile, Windows was using GCC. I don't think > the > > > > > > > compiler is going to have much of an impact since the JNI > bindings > > > are > > > > > > > simply calling through to the OpenSSL library that is already > > > > > > > precompiled for the environment. > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess < > xenoam...@gmail.com> > > > wrote: > > > > > > > > > > > > > > > > I have a feeling about both mingw or cygwin build output > will be > > > slower > > > > > > > > than microsoft-visual-studio build output... > > > > > > > > Just a feeling, but no evidence. > > > > > > > > > > > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > > > > > > > > > > > I used MinGW64. It does indeed ship with make. I can > provide > > > a link > > > > > > > > > to the distribution I used if there's interest. > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin < > > > van...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > Pretty sure I remember comments in the code about > building > > > with mingw > > > > > > > > > > on Windows (not cygwin). That should have a version of > make, > > > too, > > > > > > > > > > IIRC. > > > > > > > > > > >
Re: [crypto] New Release
Hi Gary, windows.h/Windows.h/WINDOWS.H are all names for the same file, on Windows I've found out, the FS is case-insensitive. This is not true on a Linux box though. I submitted a new PR to fix this and get Windows builds working again on a Linux box, as well as testing that windows artifacts will still build via Travis. Hopefully this can unstick the release as you can now cross-compile everything save the OSX shared-lib on one box by pointing Maven to the proper targets. -Geoff On Sat, Jul 18, 2020 at 11:25 AM Gary Gregory wrote: > > On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake > wrote: > > > I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox > > and vagrant, but it looks like the windows build is broken. There are > > typos trying to include "Windows.h" which should be "windows.h" to > > > > Are you sure that this include is not referring the to Microsoft header, > for example, on my machine: > > C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\um\Windows.h > > ? > > Gary > > > compile with mingw and redefined macros that I think are mixing > > between Linux and windows headers. I won't be able to get to trying > > to fix and submit any PRs on these this week or next. But anyone who > > wants to try cross-compiling, here are the packages I installed to get > > up and running minimally on Ubuntu: > > > > sudo apt-get install build-essential g++-mingw-w64 > > gcc-aarch64-linux-gnu libc6-dev-i386 > > sudo apt-get install libssl-dev git > > sudo add-apt-repository ppa:openjdk-r/ppa > > sudo apt-get install openjdk-8-jdk > > > > Don't install the Ubuntu supplied maven, its too old. Just grab the > > 3.6 tarball from apache. > > > > -Geoff > > > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily wrote: > > > > > > I'll see if I have any time this weekend, but this part is largely > > > unfamiliar to me, so not sure how far I'll get even if I have the time > > > to look at it. > > > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > > wrote: > > > > > > > > I think you're right Alex. I just happened to look at the Makefile > > > > and saw this above the win64 target: > > > > > > > > # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 > > package > > > > > > > > We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS > > > > box. Or even a 14.04 box if necessary. Anybody have the time to try? > > > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily > > wrote: > > > > > > > > > > Not sure if it's relevant or not, but to get the build to compile on > > > > > Windows with MinGW, I commented out line 137 of > > > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > > : > > > > > > > > > > //#define inline __inline; > > > > > > > > > > I never did learn why it was there in the first place, but the broken > > > > > build was originally reported as > > > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > > > Now I'm wondering if it may have had something to do with > > > > > cross-compiling for the build. > > > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > > wrote: > > > > > > > > > > > > Is there anything needed to help move this release along? From the > > > > > > looks of the Makefile, Windows was using GCC. I don't think the > > > > > > compiler is going to have much of an impact since the JNI bindings > > are > > > > > > simply calling through to the OpenSSL library that is already > > > > > > precompiled for the environment. > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess > > wrote: > > > > > > > > > > > > > > I have a feeling about both mingw or cygwin build output will be > > slower > > > > > > > than microsoft-visual-studio build output... > > > > > > > Just a feeling, but no evidence. > > > > > > > > > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > > > > > > > > > I used MinGW64. It does indeed ship with make. I can provide > > a link > > > > > > > > to the distribution I used if there's interest. > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin < > > van...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > Pretty sure I remember comments in the code about building > > with mingw > > > > > > > > > on Windows (not cygwin). That should have a version of make, > > too, > > > > > > > > > IIRC. > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory < > > garydgreg...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Except that you can't build on plain Windows because the > > build uses > > > > > > > > make > > > > > > > > > > and Microsoft version is called nmake. I might have to > > cobble up some > > > > > > > > > > cygwin thing... > > > > > > > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily < > >
Re: [crypto] New Release
On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake wrote: > I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox > and vagrant, but it looks like the windows build is broken. There are > typos trying to include "Windows.h" which should be "windows.h" to > Are you sure that this include is not referring the to Microsoft header, for example, on my machine: C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\um\Windows.h ? Gary > compile with mingw and redefined macros that I think are mixing > between Linux and windows headers. I won't be able to get to trying > to fix and submit any PRs on these this week or next. But anyone who > wants to try cross-compiling, here are the packages I installed to get > up and running minimally on Ubuntu: > > sudo apt-get install build-essential g++-mingw-w64 > gcc-aarch64-linux-gnu libc6-dev-i386 > sudo apt-get install libssl-dev git > sudo add-apt-repository ppa:openjdk-r/ppa > sudo apt-get install openjdk-8-jdk > > Don't install the Ubuntu supplied maven, its too old. Just grab the > 3.6 tarball from apache. > > -Geoff > > On Tue, Jun 30, 2020 at 8:24 PM Alex Remily wrote: > > > > I'll see if I have any time this weekend, but this part is largely > > unfamiliar to me, so not sure how far I'll get even if I have the time > > to look at it. > > > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > > wrote: > > > > > > I think you're right Alex. I just happened to look at the Makefile > > > and saw this above the win64 target: > > > > > > # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 > package > > > > > > We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS > > > box. Or even a 14.04 box if necessary. Anybody have the time to try? > > > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily > wrote: > > > > > > > > Not sure if it's relevant or not, but to get the build to compile on > > > > Windows with MinGW, I commented out line 137 of > > > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h > : > > > > > > > > //#define inline __inline; > > > > > > > > I never did learn why it was there in the first place, but the broken > > > > build was originally reported as > > > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > > > Now I'm wondering if it may have had something to do with > > > > cross-compiling for the build. > > > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > > wrote: > > > > > > > > > > Is there anything needed to help move this release along? From the > > > > > looks of the Makefile, Windows was using GCC. I don't think the > > > > > compiler is going to have much of an impact since the JNI bindings > are > > > > > simply calling through to the OpenSSL library that is already > > > > > precompiled for the environment. > > > > > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess > wrote: > > > > > > > > > > > > I have a feeling about both mingw or cygwin build output will be > slower > > > > > > than microsoft-visual-studio build output... > > > > > > Just a feeling, but no evidence. > > > > > > > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > > > > > > > I used MinGW64. It does indeed ship with make. I can provide > a link > > > > > > > to the distribution I used if there's interest. > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin < > van...@gmail.com> wrote: > > > > > > > > > > > > > > > > Pretty sure I remember comments in the code about building > with mingw > > > > > > > > on Windows (not cygwin). That should have a version of make, > too, > > > > > > > > IIRC. > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory < > garydgreg...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Except that you can't build on plain Windows because the > build uses > > > > > > > make > > > > > > > > > and Microsoft version is called nmake. I might have to > cobble up some > > > > > > > > > cygwin thing... > > > > > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily < > alex.rem...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > I can't speak to how the original developers did the > build, but all > > > > > > > > > > the Windows builds that I did were on a Windows > machine. I always > > > > > > > > > > assumed that the original developers just manually > packed the release > > > > > > > > > > jar with artifacts from each supported environment. I > never did any > > > > > > > > > > investigation into the process. Is cobbling together a > release in > > > > > > > > > > that manner really a non-starter here? > > > > > > > > > > > > > > > > > > > > Alex > > > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory < > garydgreg...@gmail.com > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >
Re: [crypto] New Release
I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox and vagrant, but it looks like the windows build is broken. There are typos trying to include "Windows.h" which should be "windows.h" to compile with mingw and redefined macros that I think are mixing between Linux and windows headers. I won't be able to get to trying to fix and submit any PRs on these this week or next. But anyone who wants to try cross-compiling, here are the packages I installed to get up and running minimally on Ubuntu: sudo apt-get install build-essential g++-mingw-w64 gcc-aarch64-linux-gnu libc6-dev-i386 sudo apt-get install libssl-dev git sudo add-apt-repository ppa:openjdk-r/ppa sudo apt-get install openjdk-8-jdk Don't install the Ubuntu supplied maven, its too old. Just grab the 3.6 tarball from apache. -Geoff On Tue, Jun 30, 2020 at 8:24 PM Alex Remily wrote: > > I'll see if I have any time this weekend, but this part is largely > unfamiliar to me, so not sure how far I'll get even if I have the time > to look at it. > > On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake > wrote: > > > > I think you're right Alex. I just happened to look at the Makefile > > and saw this above the win64 target: > > > > # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package > > > > We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS > > box. Or even a 14.04 box if necessary. Anybody have the time to try? > > > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily wrote: > > > > > > Not sure if it's relevant or not, but to get the build to compile on > > > Windows with MinGW, I commented out line 137 of > > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h: > > > > > > //#define inline __inline; > > > > > > I never did learn why it was there in the first place, but the broken > > > build was originally reported as > > > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > > > Now I'm wondering if it may have had something to do with > > > cross-compiling for the build. > > > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > > wrote: > > > > > > > > Is there anything needed to help move this release along? From the > > > > looks of the Makefile, Windows was using GCC. I don't think the > > > > compiler is going to have much of an impact since the JNI bindings are > > > > simply calling through to the OpenSSL library that is already > > > > precompiled for the environment. > > > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote: > > > > > > > > > > I have a feeling about both mingw or cygwin build output will be > > > > > slower > > > > > than microsoft-visual-studio build output... > > > > > Just a feeling, but no evidence. > > > > > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > > > > > I used MinGW64. It does indeed ship with make. I can provide a > > > > > > link > > > > > > to the distribution I used if there's interest. > > > > > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin > > > > > > wrote: > > > > > > > > > > > > > > Pretty sure I remember comments in the code about building with > > > > > > > mingw > > > > > > > on Windows (not cygwin). That should have a version of make, too, > > > > > > > IIRC. > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Except that you can't build on plain Windows because the build > > > > > > > > uses > > > > > > make > > > > > > > > and Microsoft version is called nmake. I might have to cobble > > > > > > > > up some > > > > > > > > cygwin thing... > > > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily > > > > > > > > wrote: > > > > > > > > > > > > > > > > > I can't speak to how the original developers did the build, > > > > > > > > > but all > > > > > > > > > the Windows builds that I did were on a Windows machine. I > > > > > > > > > always > > > > > > > > > assumed that the original developers just manually packed the > > > > > > > > > release > > > > > > > > > jar with artifacts from each supported environment. I never > > > > > > > > > did any > > > > > > > > > investigation into the process. Is cobbling together a > > > > > > > > > release in > > > > > > > > > that manner really a non-starter here? > > > > > > > > > > > > > > > > > > Alex > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hi Matt: > > > > > > > > > > > > > > > > > > > > > I have: > > > > > > > > > > > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > >
Re: [crypto] New Release
I'll see if I have any time this weekend, but this part is largely unfamiliar to me, so not sure how far I'll get even if I have the time to look at it. On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake wrote: > > I think you're right Alex. I just happened to look at the Makefile > and saw this above the win64 target: > > # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package > > We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS > box. Or even a 14.04 box if necessary. Anybody have the time to try? > > On Thu, Jun 25, 2020 at 4:12 PM Alex Remily wrote: > > > > Not sure if it's relevant or not, but to get the build to compile on > > Windows with MinGW, I commented out line 137 of > > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h: > > > > //#define inline __inline; > > > > I never did learn why it was there in the first place, but the broken > > build was originally reported as > > > > https://issues.apache.org/jira/browse/CRYPTO-137. > > > > Now I'm wondering if it may have had something to do with > > cross-compiling for the build. > > > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > > wrote: > > > > > > Is there anything needed to help move this release along? From the > > > looks of the Makefile, Windows was using GCC. I don't think the > > > compiler is going to have much of an impact since the JNI bindings are > > > simply calling through to the OpenSSL library that is already > > > precompiled for the environment. > > > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote: > > > > > > > > I have a feeling about both mingw or cygwin build output will be slower > > > > than microsoft-visual-studio build output... > > > > Just a feeling, but no evidence. > > > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > > > I used MinGW64. It does indeed ship with make. I can provide a link > > > > > to the distribution I used if there's interest. > > > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin > > > > > wrote: > > > > > > > > > > > > Pretty sure I remember comments in the code about building with > > > > > > mingw > > > > > > on Windows (not cygwin). That should have a version of make, too, > > > > > > IIRC. > > > > > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > > > > > > > > > > > wrote: > > > > > > > > > > > > > > Except that you can't build on plain Windows because the build > > > > > > > uses > > > > > make > > > > > > > and Microsoft version is called nmake. I might have to cobble up > > > > > > > some > > > > > > > cygwin thing... > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily > > > > > > > wrote: > > > > > > > > > > > > > > > I can't speak to how the original developers did the build, but > > > > > > > > all > > > > > > > > the Windows builds that I did were on a Windows machine. I > > > > > > > > always > > > > > > > > assumed that the original developers just manually packed the > > > > > > > > release > > > > > > > > jar with artifacts from each supported environment. I never > > > > > > > > did any > > > > > > > > investigation into the process. Is cobbling together a release > > > > > > > > in > > > > > > > > that manner really a non-starter here? > > > > > > > > > > > > > > > > Alex > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Matt: > > > > > > > > > > > > > > > > > > > I have: > > > > > > > > > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > > > > > > > > > > > Case matters here, so I wonder if the original others did > > > > > > > > > > not > > > > > cross > > > > > > > > > compile > > > > > > > > > > from Linux and instead built a little here, a little there, > > > > > > > > > > and > > > > > so on. > > > > > > > > > > > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure > > > > > > > > > > where > > > > > that is > > > > > > > > > > supposed to be... > > > > > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Are the Windows headers even available when using Ming32 or > > > > > Cygwin? > > > > > > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory < > > > > > garydgreg...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > The challenge is getting everything set up just right for > > > > > building > > > > > > > > the > > > > > > > > > > >
Re: [crypto] New Release
I think you're right Alex. I just happened to look at the Makefile and saw this above the win64 target: # for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS box. Or even a 14.04 box if necessary. Anybody have the time to try? On Thu, Jun 25, 2020 at 4:12 PM Alex Remily wrote: > > Not sure if it's relevant or not, but to get the build to compile on > Windows with MinGW, I commented out line 137 of > https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h: > > //#define inline __inline; > > I never did learn why it was there in the first place, but the broken > build was originally reported as > > https://issues.apache.org/jira/browse/CRYPTO-137. > > Now I'm wondering if it may have had something to do with > cross-compiling for the build. > > On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake > wrote: > > > > Is there anything needed to help move this release along? From the > > looks of the Makefile, Windows was using GCC. I don't think the > > compiler is going to have much of an impact since the JNI bindings are > > simply calling through to the OpenSSL library that is already > > precompiled for the environment. > > > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote: > > > > > > I have a feeling about both mingw or cygwin build output will be slower > > > than microsoft-visual-studio build output... > > > Just a feeling, but no evidence. > > > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > > > I used MinGW64. It does indeed ship with make. I can provide a link > > > > to the distribution I used if there's interest. > > > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote: > > > > > > > > > > Pretty sure I remember comments in the code about building with mingw > > > > > on Windows (not cygwin). That should have a version of make, too, > > > > > IIRC. > > > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > > > > wrote: > > > > > > > > > > > > Except that you can't build on plain Windows because the build uses > > > > make > > > > > > and Microsoft version is called nmake. I might have to cobble up > > > > > > some > > > > > > cygwin thing... > > > > > > > > > > > > Gary > > > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily > > > > > > wrote: > > > > > > > > > > > > > I can't speak to how the original developers did the build, but > > > > > > > all > > > > > > > the Windows builds that I did were on a Windows machine. I always > > > > > > > assumed that the original developers just manually packed the > > > > > > > release > > > > > > > jar with artifacts from each supported environment. I never did > > > > > > > any > > > > > > > investigation into the process. Is cobbling together a release in > > > > > > > that manner really a non-starter here? > > > > > > > > > > > > > > Alex > > > > > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi Matt: > > > > > > > > > > > > > > > > > I have: > > > > > > > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > > > > > > > > > Case matters here, so I wonder if the original others did not > > > > cross > > > > > > > > compile > > > > > > > > > from Linux and instead built a little here, a little there, > > > > > > > > > and > > > > so on. > > > > > > > > > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where > > > > that is > > > > > > > > > supposed to be... > > > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Are the Windows headers even available when using Ming32 or > > > > Cygwin? > > > > > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory < > > > > garydgreg...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > The challenge is getting everything set up just right for > > > > building > > > > > > > the > > > > > > > > > > various OS profiles. This component is quite different in > > > > > > > > > > this > > > > > > > regard, > > > > > > > > > > getting help from the original contributors would be > > > > > > > > > > helpful. > > > > > > > > > > > > > > > > > > > > After much fiddling to install the proper packages, this > > > > builds OK: > > > > > > > > > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > > > > > > > > > But these do not: > > > > > > > > > > mvn package -DskipTests -P win64 > > > > > >
Re: [crypto] New Release
Not sure if it's relevant or not, but to get the build to compile on Windows with MinGW, I commented out line 137 of https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h: //#define inline __inline; I never did learn why it was there in the first place, but the broken build was originally reported as https://issues.apache.org/jira/browse/CRYPTO-137. Now I'm wondering if it may have had something to do with cross-compiling for the build. On Thu, Jun 25, 2020 at 1:13 PM Geoffrey Blake wrote: > > Is there anything needed to help move this release along? From the > looks of the Makefile, Windows was using GCC. I don't think the > compiler is going to have much of an impact since the JNI bindings are > simply calling through to the OpenSSL library that is already > precompiled for the environment. > > On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote: > > > > I have a feeling about both mingw or cygwin build output will be slower > > than microsoft-visual-studio build output... > > Just a feeling, but no evidence. > > > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > > > I used MinGW64. It does indeed ship with make. I can provide a link > > > to the distribution I used if there's interest. > > > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote: > > > > > > > > Pretty sure I remember comments in the code about building with mingw > > > > on Windows (not cygwin). That should have a version of make, too, > > > > IIRC. > > > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > > > wrote: > > > > > > > > > > Except that you can't build on plain Windows because the build uses > > > make > > > > > and Microsoft version is called nmake. I might have to cobble up some > > > > > cygwin thing... > > > > > > > > > > Gary > > > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > > > > > > > > > I can't speak to how the original developers did the build, but all > > > > > > the Windows builds that I did were on a Windows machine. I always > > > > > > assumed that the original developers just manually packed the > > > > > > release > > > > > > jar with artifacts from each supported environment. I never did any > > > > > > investigation into the process. Is cobbling together a release in > > > > > > that manner really a non-starter here? > > > > > > > > > > > > Alex > > > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > > > > > wrote: > > > > > > > > > > > > > > Hi Matt: > > > > > > > > > > > > > > > I have: > > > > > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > > > > > > > Case matters here, so I wonder if the original others did not > > > cross > > > > > > > compile > > > > > > > > from Linux and instead built a little here, a little there, and > > > so on. > > > > > > > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where > > > that is > > > > > > > > supposed to be... > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > > > > > > > > > Are the Windows headers even available when using Ming32 or > > > Cygwin? > > > > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory < > > > garydgreg...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > The challenge is getting everything set up just right for > > > building > > > > > > the > > > > > > > > > various OS profiles. This component is quite different in this > > > > > > regard, > > > > > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > > > > > > > > > After much fiddling to install the proper packages, this > > > builds OK: > > > > > > > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > > > > > > > But these do not: > > > > > > > > > mvn package -DskipTests -P win64 > > > > > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > > > > > > > > > due to: > > > > > > > > > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto > > > --- > > > > > > > > > [INFO] Executing tasks > > > > > > > > > > > > > > > > > > make: > > > > > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > > > > > OS_NAME=Windows > > > > > > > > > OS_ARCH=x86_64 > > > > > > > > > [exec] make[1]: Entering directory > > > '/mnt/c/git/commons-crypto' > > > > > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > > > > >
Re: [crypto] New Release
Is there anything needed to help move this release along? From the looks of the Makefile, Windows was using GCC. I don't think the compiler is going to have much of an impact since the JNI bindings are simply calling through to the OpenSSL library that is already precompiled for the environment. On Sat, Jun 13, 2020 at 6:14 PM Xeno Amess wrote: > > I have a feeling about both mingw or cygwin build output will be slower > than microsoft-visual-studio build output... > Just a feeling, but no evidence. > > Alex Remily 于2020年6月14日周日 上午7:02写道: > > > I used MinGW64. It does indeed ship with make. I can provide a link > > to the distribution I used if there's interest. > > > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote: > > > > > > Pretty sure I remember comments in the code about building with mingw > > > on Windows (not cygwin). That should have a version of make, too, > > > IIRC. > > > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > > wrote: > > > > > > > > Except that you can't build on plain Windows because the build uses > > make > > > > and Microsoft version is called nmake. I might have to cobble up some > > > > cygwin thing... > > > > > > > > Gary > > > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > > > > > > > I can't speak to how the original developers did the build, but all > > > > > the Windows builds that I did were on a Windows machine. I always > > > > > assumed that the original developers just manually packed the release > > > > > jar with artifacts from each supported environment. I never did any > > > > > investigation into the process. Is cobbling together a release in > > > > > that manner really a non-starter here? > > > > > > > > > > Alex > > > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > > > wrote: > > > > > > > > > > > > Hi Matt: > > > > > > > > > > > > > I have: > > > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > > > > > Case matters here, so I wonder if the original others did not > > cross > > > > > > compile > > > > > > > from Linux and instead built a little here, a little there, and > > so on. > > > > > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where > > that is > > > > > > > supposed to be... > > > > > > > > > > > > Gary > > > > > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > > > > > > > Are the Windows headers even available when using Ming32 or > > Cygwin? > > > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory < > > garydgreg...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > The challenge is getting everything set up just right for > > building > > > > > the > > > > > > > > various OS profiles. This component is quite different in this > > > > > regard, > > > > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > > > > > > > After much fiddling to install the proper packages, this > > builds OK: > > > > > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > > > > > But these do not: > > > > > > > > mvn package -DskipTests -P win64 > > > > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > > > > > > > due to: > > > > > > > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto > > --- > > > > > > > > [INFO] Executing tasks > > > > > > > > > > > > > > > > make: > > > > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > > > > OS_NAME=Windows > > > > > > > > OS_ARCH=x86_64 > > > > > > > > [exec] make[1]: Entering directory > > '/mnt/c/git/commons-crypto' > > > > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > > > > > -o > > > > > > > > > > > > > > > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > > > > > [exec] Makefile:54: recipe for target > > > > > > > > > > > > > > > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > > > > > failed > > > > > > > > [exec] make[1]: Leaving directory > >
Re: [crypto] New Release
I have a feeling about both mingw or cygwin build output will be slower than microsoft-visual-studio build output... Just a feeling, but no evidence. Alex Remily 于2020年6月14日周日 上午7:02写道: > I used MinGW64. It does indeed ship with make. I can provide a link > to the distribution I used if there's interest. > > On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote: > > > > Pretty sure I remember comments in the code about building with mingw > > on Windows (not cygwin). That should have a version of make, too, > > IIRC. > > > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > wrote: > > > > > > Except that you can't build on plain Windows because the build uses > make > > > and Microsoft version is called nmake. I might have to cobble up some > > > cygwin thing... > > > > > > Gary > > > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > > > > > I can't speak to how the original developers did the build, but all > > > > the Windows builds that I did were on a Windows machine. I always > > > > assumed that the original developers just manually packed the release > > > > jar with artifacts from each supported environment. I never did any > > > > investigation into the process. Is cobbling together a release in > > > > that manner really a non-starter here? > > > > > > > > Alex > > > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > > > wrote: > > > > > > > > > > Hi Matt: > > > > > > > > > > > I have: > > > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > > /usr/share/mingw-w64/include/windows.h > > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > > > Case matters here, so I wonder if the original others did not > cross > > > > > compile > > > > > > from Linux and instead built a little here, a little there, and > so on. > > > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where > that is > > > > > > supposed to be... > > > > > > > > > > Gary > > > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > > > > > Are the Windows headers even available when using Ming32 or > Cygwin? > > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory < > garydgreg...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > The challenge is getting everything set up just right for > building > > > > the > > > > > > > various OS profiles. This component is quite different in this > > > > regard, > > > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > > > > > After much fiddling to install the proper packages, this > builds OK: > > > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > > > But these do not: > > > > > > > mvn package -DskipTests -P win64 > > > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > > > > > due to: > > > > > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto > --- > > > > > > > [INFO] Executing tasks > > > > > > > > > > > > > > make: > > > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > > > OS_NAME=Windows > > > > > > > OS_ARCH=x86_64 > > > > > > > [exec] make[1]: Entering directory > '/mnt/c/git/commons-crypto' > > > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > > > > -o > > > > > > > > > > > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > > > > [exec] Makefile:54: recipe for target > > > > > > > > > > > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > > > > failed > > > > > > > [exec] make[1]: Leaving directory > '/mnt/c/git/commons-crypto' > > > > > > > [exec] Makefile:82: recipe for target 'win64' failed > > > > > > > [exec] In file included from > > > > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > > > > > [exec] from > > > > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > > > > > [exec] > > > > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > > > > > fatal error: Windows.h: No
Re: [crypto] New Release
I used MinGW64. It does indeed ship with make. I can provide a link to the distribution I used if there's interest. On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote: > > Pretty sure I remember comments in the code about building with mingw > on Windows (not cygwin). That should have a version of make, too, > IIRC. > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory wrote: > > > > Except that you can't build on plain Windows because the build uses make > > and Microsoft version is called nmake. I might have to cobble up some > > cygwin thing... > > > > Gary > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > > > I can't speak to how the original developers did the build, but all > > > the Windows builds that I did were on a Windows machine. I always > > > assumed that the original developers just manually packed the release > > > jar with artifacts from each supported environment. I never did any > > > investigation into the process. Is cobbling together a release in > > > that manner really a non-starter here? > > > > > > Alex > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > wrote: > > > > > > > > Hi Matt: > > > > > > > > > I have: > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > /usr/share/mingw-w64/include/windows.h > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > Case matters here, so I wonder if the original others did not cross > > > > compile > > > > > from Linux and instead built a little here, a little there, and so on. > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > > > > supposed to be... > > > > > > > > Gary > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > > > Are the Windows headers even available when using Ming32 or Cygwin? > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory > > > wrote: > > > > > > > > > > > > The challenge is getting everything set up just right for building > > > the > > > > > > various OS profiles. This component is quite different in this > > > regard, > > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > > > After much fiddling to install the proper packages, this builds OK: > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > But these do not: > > > > > > mvn package -DskipTests -P win64 > > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > > > due to: > > > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > > > > > [INFO] Executing tasks > > > > > > > > > > > > make: > > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > > OS_NAME=Windows > > > > > > OS_ARCH=x86_64 > > > > > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > > > -o > > > > > > > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > > > [exec] Makefile:54: recipe for target > > > > > > > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > > > failed > > > > > > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > > > > > > [exec] Makefile:82: recipe for target 'win64' failed > > > > > > [exec] In file included from > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > > > > [exec] from > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > > > > [exec] > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > > > > fatal error: Windows.h: No such file or directory > > > > > > [exec] #include > > > > > > [exec] ^~~ > > > > > > [exec] compilation terminated. > > > > > > [exec] make[1]: *** > > > > > > > > > > > > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > > > > > Error 1 > > > > > > [exec] make: *** [win64] Error 2 > > > > > > [INFO] > > > > > > > > > > > > >
Re: [crypto] New Release
Use of cmake could be useful for cross platform builds, though I’ve only used some of the basic functionality so far and can’t comment on how big a task it is to convert to use. On Sat, Jun 13, 2020 at 17:26 Marcelo Vanzin wrote: > Pretty sure I remember comments in the code about building with mingw > on Windows (not cygwin). That should have a version of make, too, > IIRC. > > On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory > wrote: > > > > Except that you can't build on plain Windows because the build uses make > > and Microsoft version is called nmake. I might have to cobble up some > > cygwin thing... > > > > Gary > > > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > > > I can't speak to how the original developers did the build, but all > > > the Windows builds that I did were on a Windows machine. I always > > > assumed that the original developers just manually packed the release > > > jar with artifacts from each supported environment. I never did any > > > investigation into the process. Is cobbling together a release in > > > that manner really a non-starter here? > > > > > > Alex > > > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > > wrote: > > > > > > > > Hi Matt: > > > > > > > > > I have: > > > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > > /usr/i686-w64-mingw32/include/windows.h > > > > > /usr/share/mingw-w64/include/windows.h > > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > > > Case matters here, so I wonder if the original others did not cross > > > > compile > > > > > from Linux and instead built a little here, a little there, and so > on. > > > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where > that is > > > > > supposed to be... > > > > > > > > Gary > > > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > > > Are the Windows headers even available when using Ming32 or Cygwin? > > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory > > > > wrote: > > > > > > > > > > > > The challenge is getting everything set up just right for > building > > > the > > > > > > various OS profiles. This component is quite different in this > > > regard, > > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > > > After much fiddling to install the proper packages, this builds > OK: > > > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > > > But these do not: > > > > > > mvn package -DskipTests -P win64 > > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > > > due to: > > > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto > --- > > > > > > [INFO] Executing tasks > > > > > > > > > > > > make: > > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > > OS_NAME=Windows > > > > > > OS_ARCH=x86_64 > > > > > > [exec] make[1]: Entering directory > '/mnt/c/git/commons-crypto' > > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > > > -o > > > > > > > > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > > > [exec] Makefile:54: recipe for target > > > > > > > > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > > > failed > > > > > > [exec] make[1]: Leaving directory > '/mnt/c/git/commons-crypto' > > > > > > [exec] Makefile:82: recipe for target 'win64' failed > > > > > > [exec] In file included from > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > > > > [exec] from > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > > > > [exec] > > > > > > > > > > > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > > > > fatal error: Windows.h: No such file or directory > > > > > > [exec] #include > > > > > > [exec] ^~~ > > > > > > [exec] compilation terminated. > > > > > > [exec] make[1]: *** > > > > > > > > > > > > > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > > > > > Error 1 > > > > > > [exec] make: *** [win64] Error 2 > > > > > > [INFO] > > > > >
Re: [crypto] New Release
Pretty sure I remember comments in the code about building with mingw on Windows (not cygwin). That should have a version of make, too, IIRC. On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory wrote: > > Except that you can't build on plain Windows because the build uses make > and Microsoft version is called nmake. I might have to cobble up some > cygwin thing... > > Gary > > On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > > > I can't speak to how the original developers did the build, but all > > the Windows builds that I did were on a Windows machine. I always > > assumed that the original developers just manually packed the release > > jar with artifacts from each supported environment. I never did any > > investigation into the process. Is cobbling together a release in > > that manner really a non-starter here? > > > > Alex > > > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > > wrote: > > > > > > Hi Matt: > > > > > > > I have: > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > /usr/i686-w64-mingw32/include/windows.h > > > > /usr/share/mingw-w64/include/windows.h > > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > > > Case matters here, so I wonder if the original others did not cross > > > compile > > > > from Linux and instead built a little here, a little there, and so on. > > > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > > > supposed to be... > > > > > > Gary > > > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > > > Are the Windows headers even available when using Ming32 or Cygwin? > > > > That sounds more like a Visual Studio compiler thing. > > > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory > > wrote: > > > > > > > > > > The challenge is getting everything set up just right for building > > the > > > > > various OS profiles. This component is quite different in this > > regard, > > > > > getting help from the original contributors would be helpful. > > > > > > > > > > After much fiddling to install the proper packages, this builds OK: > > > > > > > > > > mvn package -DskipTests -P linux64 > > > > > mvn package -DskipTests -P linux32 > > > > > > > > > > But these do not: > > > > > mvn package -DskipTests -P win64 > > > > > mvn package -DskipTests -P win32 > > > > > > > > > > due to: > > > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > > > > [INFO] Executing tasks > > > > > > > > > > make: > > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > > OS_NAME=Windows > > > > > OS_ARCH=x86_64 > > > > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > > > > [exec] x86_64-w64-mingw32-gcc > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > > -o > > > > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > > [exec] Makefile:54: recipe for target > > > > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > > failed > > > > > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > > > > > [exec] Makefile:82: recipe for target 'win64' failed > > > > > [exec] In file included from > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > > > [exec] from > > > > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > > > [exec] > > > > > > > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > > > fatal error: Windows.h: No such file or directory > > > > > [exec] #include > > > > > [exec] ^~~ > > > > > [exec] compilation terminated. > > > > > [exec] make[1]: *** > > > > > > > > > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > > > > Error 1 > > > > > [exec] make: *** [win64] Error 2 > > > > > [INFO] > > > > > > > > > > > > [INFO] BUILD FAILURE > > > > > [INFO] > > > > > > > > > > > > [INFO] Total time: 10.107 s > > > > > [INFO] Finished at: 2020-06-13T13:58:50Z > > > > > [INFO] > > > > > > > > > > > > [ERROR] Failed to execute goal > > > > >
Re: [crypto] New Release
Except that you can't build on plain Windows because the build uses make and Microsoft version is called nmake. I might have to cobble up some cygwin thing... Gary On Sat, Jun 13, 2020, 18:02 Alex Remily wrote: > I can't speak to how the original developers did the build, but all > the Windows builds that I did were on a Windows machine. I always > assumed that the original developers just manually packed the release > jar with artifacts from each supported environment. I never did any > investigation into the process. Is cobbling together a release in > that manner really a non-starter here? > > Alex > > On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory > wrote: > > > > Hi Matt: > > > > > I have: > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > /usr/i686-w64-mingw32/include/windows.h > > > /usr/share/mingw-w64/include/windows.h > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > Case matters here, so I wonder if the original others did not cross > > compile > > > from Linux and instead built a little here, a little there, and so on. > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > > supposed to be... > > > > Gary > > > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > > > Are the Windows headers even available when using Ming32 or Cygwin? > > > That sounds more like a Visual Studio compiler thing. > > > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory > wrote: > > > > > > > > The challenge is getting everything set up just right for building > the > > > > various OS profiles. This component is quite different in this > regard, > > > > getting help from the original contributors would be helpful. > > > > > > > > After much fiddling to install the proper packages, this builds OK: > > > > > > > > mvn package -DskipTests -P linux64 > > > > mvn package -DskipTests -P linux32 > > > > > > > > But these do not: > > > > mvn package -DskipTests -P win64 > > > > mvn package -DskipTests -P win32 > > > > > > > > due to: > > > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > > > [INFO] Executing tasks > > > > > > > > make: > > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- > OS_NAME=Windows > > > > OS_ARCH=x86_64 > > > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > > > [exec] x86_64-w64-mingw32-gcc > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > > -I"src/main/native/org/apache/commons/crypto/" > > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > > -o > > > > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > > [exec] Makefile:54: recipe for target > > > > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > > failed > > > > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > > > > [exec] Makefile:82: recipe for target 'win64' failed > > > > [exec] In file included from > > > > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > > [exec] from > > > > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > > [exec] > > > > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > > fatal error: Windows.h: No such file or directory > > > > [exec] #include > > > > [exec] ^~~ > > > > [exec] compilation terminated. > > > > [exec] make[1]: *** > > > > > > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > > > Error 1 > > > > [exec] make: *** [win64] Error 2 > > > > [INFO] > > > > > > > > > [INFO] BUILD FAILURE > > > > [INFO] > > > > > > > > > [INFO] Total time: 10.107 s > > > > [INFO] Finished at: 2020-06-13T13:58:50Z > > > > [INFO] > > > > > > > > > [ERROR] Failed to execute goal > > > > org.apache.maven.plugins:maven-antrun-plugin:1.8:run (make) on > project > > > > commons-crypto: An Ant BuildException has occured: exec returned: 2 > > > > [ERROR] around Ant part ... > > > dir="/mnt/c/git/commons-crypto" executable="make">... @ 5:78 in > > > > /mnt/c/git/commons-crypto/target/antrun/build-make.xml > > > > > > > > I have: > > > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > > /usr/i686-w64-mingw32/include/windows.h > > > >
Re: [crypto] New Release
I can't speak to how the original developers did the build, but all the Windows builds that I did were on a Windows machine. I always assumed that the original developers just manually packed the release jar with artifacts from each supported environment. I never did any investigation into the process. Is cobbling together a release in that manner really a non-starter here? Alex On Sat, Jun 13, 2020 at 5:44 PM Gary Gregory wrote: > > Hi Matt: > > > I have: > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > /usr/i686-w64-mingw32/include/windows.h > > /usr/share/mingw-w64/include/windows.h > > /usr/x86_64-w64-mingw32/include/windows.h > > > > Case matters here, so I wonder if the original others did not cross > compile > > from Linux and instead built a little here, a little there, and so on. > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > supposed to be... > > Gary > > On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > > > Are the Windows headers even available when using Ming32 or Cygwin? > > That sounds more like a Visual Studio compiler thing. > > > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory wrote: > > > > > > The challenge is getting everything set up just right for building the > > > various OS profiles. This component is quite different in this regard, > > > getting help from the original contributors would be helpful. > > > > > > After much fiddling to install the proper packages, this builds OK: > > > > > > mvn package -DskipTests -P linux64 > > > mvn package -DskipTests -P linux32 > > > > > > But these do not: > > > mvn package -DskipTests -P win64 > > > mvn package -DskipTests -P win32 > > > > > > due to: > > > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > > [INFO] Executing tasks > > > > > > make: > > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- OS_NAME=Windows > > > OS_ARCH=x86_64 > > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > > [exec] x86_64-w64-mingw32-gcc > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > > -I"src/main/native/org/apache/commons/crypto/" > > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > > -o > > > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > > [exec] Makefile:54: recipe for target > > > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > > failed > > > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > > > [exec] Makefile:82: recipe for target 'win64' failed > > > [exec] In file included from > > > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > > [exec] from > > > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > > [exec] > > > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > > fatal error: Windows.h: No such file or directory > > > [exec] #include > > > [exec] ^~~ > > > [exec] compilation terminated. > > > [exec] make[1]: *** > > > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > > Error 1 > > > [exec] make: *** [win64] Error 2 > > > [INFO] > > > > > > [INFO] BUILD FAILURE > > > [INFO] > > > > > > [INFO] Total time: 10.107 s > > > [INFO] Finished at: 2020-06-13T13:58:50Z > > > [INFO] > > > > > > [ERROR] Failed to execute goal > > > org.apache.maven.plugins:maven-antrun-plugin:1.8:run (make) on project > > > commons-crypto: An Ant BuildException has occured: exec returned: 2 > > > [ERROR] around Ant part ... > > dir="/mnt/c/git/commons-crypto" executable="make">... @ 5:78 in > > > /mnt/c/git/commons-crypto/target/antrun/build-make.xml > > > > > > I have: > > > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > > /usr/i686-w64-mingw32/include/windows.h > > > /usr/share/mingw-w64/include/windows.h > > > /usr/x86_64-w64-mingw32/include/windows.h > > > > > > Case matters here, so I wonder if the original others did not cross > > compile > > > from Linux and instead built a little here, a little there, and so on. > > > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > > supposed to be... > > > > > > Building with mac64 profile is no better: > > > > > > mvn package -DskipTests -P mac64 > > > > > > [INFO] ---
Re: [crypto] New Release
Hi Matt: > I have: > > /mnt/c/git/commons-crypto# find /usr -name windows.h > /usr/i686-w64-mingw32/include/windows.h > /usr/share/mingw-w64/include/windows.h > /usr/x86_64-w64-mingw32/include/windows.h > > Case matters here, so I wonder if the original others did not cross compile > from Linux and instead built a little here, a little there, and so on. > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > supposed to be... Gary On Sat, Jun 13, 2020, 15:41 Matt Sicker wrote: > Are the Windows headers even available when using Ming32 or Cygwin? > That sounds more like a Visual Studio compiler thing. > > On Sat, 13 Jun 2020 at 09:29, Gary Gregory wrote: > > > > The challenge is getting everything set up just right for building the > > various OS profiles. This component is quite different in this regard, > > getting help from the original contributors would be helpful. > > > > After much fiddling to install the proper packages, this builds OK: > > > > mvn package -DskipTests -P linux64 > > mvn package -DskipTests -P linux32 > > > > But these do not: > > mvn package -DskipTests -P win64 > > mvn package -DskipTests -P win32 > > > > due to: > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > [INFO] Executing tasks > > > > make: > > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- OS_NAME=Windows > > OS_ARCH=x86_64 > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > [exec] x86_64-w64-mingw32-gcc > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > > -I"src/main/native/org/apache/commons/crypto/" > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > > -I"target/jni-classes/org/apache/commons/crypto/random" -c > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > > -o > > > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > > [exec] Makefile:54: recipe for target > > > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > > failed > > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > > [exec] Makefile:82: recipe for target 'win64' failed > > [exec] In file included from > > > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > > [exec] from > > > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > > [exec] > > > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > > fatal error: Windows.h: No such file or directory > > [exec] #include > > [exec] ^~~ > > [exec] compilation terminated. > > [exec] make[1]: *** > > > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > > Error 1 > > [exec] make: *** [win64] Error 2 > > [INFO] > > > > [INFO] BUILD FAILURE > > [INFO] > > > > [INFO] Total time: 10.107 s > > [INFO] Finished at: 2020-06-13T13:58:50Z > > [INFO] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-antrun-plugin:1.8:run (make) on project > > commons-crypto: An Ant BuildException has occured: exec returned: 2 > > [ERROR] around Ant part ... > dir="/mnt/c/git/commons-crypto" executable="make">... @ 5:78 in > > /mnt/c/git/commons-crypto/target/antrun/build-make.xml > > > > I have: > > > > /mnt/c/git/commons-crypto# find /usr -name windows.h > > /usr/i686-w64-mingw32/include/windows.h > > /usr/share/mingw-w64/include/windows.h > > /usr/x86_64-w64-mingw32/include/windows.h > > > > Case matters here, so I wonder if the original others did not cross > compile > > from Linux and instead built a little here, a little there, and so on. > > > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > > supposed to be... > > > > Building with mac64 profile is no better: > > > > mvn package -DskipTests -P mac64 > > > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > > [INFO] Executing tasks > > > > make: > > [exec] make native OS_NAME=Mac OS_ARCH=x86_64 > > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > > [exec] gcc -arch x86_64 -Ilib/inc_mac > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -O2 -fPIC > > -mmacosx-version-min=10.7 -fvisibility=hidden -I/usr/local/include > > -I/usr/local/opt/openssl/include -Ilib/include -I/usr/include > > -I"src/main/native/org/apache/commons/crypto/" > > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > > -I"target/jni-classes/org/apache/commons/crypto/cipher" > >
Re: [crypto] New Release
Are the Windows headers even available when using Ming32 or Cygwin? That sounds more like a Visual Studio compiler thing. On Sat, 13 Jun 2020 at 09:29, Gary Gregory wrote: > > The challenge is getting everything set up just right for building the > various OS profiles. This component is quite different in this regard, > getting help from the original contributors would be helpful. > > After much fiddling to install the proper packages, this builds OK: > > mvn package -DskipTests -P linux64 > mvn package -DskipTests -P linux32 > > But these do not: > mvn package -DskipTests -P win64 > mvn package -DskipTests -P win32 > > due to: > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > [INFO] Executing tasks > > make: > [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- OS_NAME=Windows > OS_ARCH=x86_64 > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > [exec] x86_64-w64-mingw32-gcc > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" > -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include > -I"src/main/native/org/apache/commons/crypto/" > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > -I"target/jni-classes/org/apache/commons/crypto/cipher" > -I"target/jni-classes/org/apache/commons/crypto/random" -c > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > -o > target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o > [exec] Makefile:54: recipe for target > 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' > failed > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > [exec] Makefile:82: recipe for target 'win64' failed > [exec] In file included from > src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, > [exec] from > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: > [exec] > src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: > fatal error: Windows.h: No such file or directory > [exec] #include > [exec] ^~~ > [exec] compilation terminated. > [exec] make[1]: *** > [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] > Error 1 > [exec] make: *** [win64] Error 2 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 10.107 s > [INFO] Finished at: 2020-06-13T13:58:50Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.8:run (make) on project > commons-crypto: An Ant BuildException has occured: exec returned: 2 > [ERROR] around Ant part ... dir="/mnt/c/git/commons-crypto" executable="make">... @ 5:78 in > /mnt/c/git/commons-crypto/target/antrun/build-make.xml > > I have: > > /mnt/c/git/commons-crypto# find /usr -name windows.h > /usr/i686-w64-mingw32/include/windows.h > /usr/share/mingw-w64/include/windows.h > /usr/x86_64-w64-mingw32/include/windows.h > > Case matters here, so I wonder if the original others did not cross compile > from Linux and instead built a little here, a little there, and so on. > > I can see "-Ilib/inc_win" in the build but I am not sure where that is > supposed to be... > > Building with mac64 profile is no better: > > mvn package -DskipTests -P mac64 > > [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- > [INFO] Executing tasks > > make: > [exec] make native OS_NAME=Mac OS_ARCH=x86_64 > [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' > [exec] gcc -arch x86_64 -Ilib/inc_mac > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -O2 -fPIC > -mmacosx-version-min=10.7 -fvisibility=hidden -I/usr/local/include > -I/usr/local/opt/openssl/include -Ilib/include -I/usr/include > -I"src/main/native/org/apache/commons/crypto/" > -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" > -I"target/jni-classes/org/apache/commons/crypto/cipher" > -I"target/jni-classes/org/apache/commons/crypto/random" -c > src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c > -o > target/commons-crypto-1.1.0-SNAPSHOT-Mac-x86_64/OpenSslCryptoRandomNative.o > [exec] Makefile:54: recipe for target > 'target/commons-crypto-1.1.0-SNAPSHOT-Mac-x86_64/OpenSslCryptoRandomNative.o' > failed > [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' > [exec] Makefile:88: recipe for target 'mac64' failed > [exec] gcc: error: x86_64: No such file or directory > [exec] gcc: error: unrecognized command line option ‘-arch’; did you > mean ‘-march=’? > [exec] gcc: error: unrecognized command line option > ‘-mmacosx-version-min=10.7’ > [exec] make[1]: *** >
Re: [crypto] New Release
The challenge is getting everything set up just right for building the various OS profiles. This component is quite different in this regard, getting help from the original contributors would be helpful. After much fiddling to install the proper packages, this builds OK: mvn package -DskipTests -P linux64 mvn package -DskipTests -P linux32 But these do not: mvn package -DskipTests -P win64 mvn package -DskipTests -P win32 due to: [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- [INFO] Executing tasks make: [exec] make native CROSS_PREFIX=x86_64-w64-mingw32- OS_NAME=Windows OS_ARCH=x86_64 [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' [exec] x86_64-w64-mingw32-gcc -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -I"/include" -Ilib/inc_win -O2 -fno-inline -Ilib/include -I/usr/include -I"src/main/native/org/apache/commons/crypto/" -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" -I"target/jni-classes/org/apache/commons/crypto/cipher" -I"target/jni-classes/org/apache/commons/crypto/random" -c src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c -o target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o [exec] Makefile:54: recipe for target 'target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o' failed [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' [exec] Makefile:82: recipe for target 'win64' failed [exec] In file included from src/main/native/org/apache/commons/crypto/random/org_apache_commons_crypto_random.h:22:0, [exec] from src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c:19: [exec] src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:151:10: fatal error: Windows.h: No such file or directory [exec] #include [exec] ^~~ [exec] compilation terminated. [exec] make[1]: *** [target/commons-crypto-1.1.0-SNAPSHOT-Windows-x86_64/OpenSslCryptoRandomNative.o] Error 1 [exec] make: *** [win64] Error 2 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10.107 s [INFO] Finished at: 2020-06-13T13:58:50Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (make) on project commons-crypto: An Ant BuildException has occured: exec returned: 2 [ERROR] around Ant part .. @ 5:78 in /mnt/c/git/commons-crypto/target/antrun/build-make.xml I have: /mnt/c/git/commons-crypto# find /usr -name windows.h /usr/i686-w64-mingw32/include/windows.h /usr/share/mingw-w64/include/windows.h /usr/x86_64-w64-mingw32/include/windows.h Case matters here, so I wonder if the original others did not cross compile from Linux and instead built a little here, a little there, and so on. I can see "-Ilib/inc_win" in the build but I am not sure where that is supposed to be... Building with mac64 profile is no better: mvn package -DskipTests -P mac64 [INFO] --- maven-antrun-plugin:1.8:run (make) @ commons-crypto --- [INFO] Executing tasks make: [exec] make native OS_NAME=Mac OS_ARCH=x86_64 [exec] make[1]: Entering directory '/mnt/c/git/commons-crypto' [exec] gcc -arch x86_64 -Ilib/inc_mac -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include" -O2 -fPIC -mmacosx-version-min=10.7 -fvisibility=hidden -I/usr/local/include -I/usr/local/opt/openssl/include -Ilib/include -I/usr/include -I"src/main/native/org/apache/commons/crypto/" -I"/usr/lib/jvm/java-1.8.0-openjdk-amd64/include/linux" -I"target/jni-classes/org/apache/commons/crypto/cipher" -I"target/jni-classes/org/apache/commons/crypto/random" -c src/main/native/org/apache/commons/crypto/random/OpenSslCryptoRandomNative.c -o target/commons-crypto-1.1.0-SNAPSHOT-Mac-x86_64/OpenSslCryptoRandomNative.o [exec] Makefile:54: recipe for target 'target/commons-crypto-1.1.0-SNAPSHOT-Mac-x86_64/OpenSslCryptoRandomNative.o' failed [exec] make[1]: Leaving directory '/mnt/c/git/commons-crypto' [exec] Makefile:88: recipe for target 'mac64' failed [exec] gcc: error: x86_64: No such file or directory [exec] gcc: error: unrecognized command line option ‘-arch’; did you mean ‘-march=’? [exec] gcc: error: unrecognized command line option ‘-mmacosx-version-min=10.7’ [exec] make[1]: *** [target/commons-crypto-1.1.0-SNAPSHOT-Mac-x86_64/OpenSslCryptoRandomNative.o] Error 1 [exec] make: *** [mac64] Error 2 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12.513 s [INFO] Finished at: 2020-06-13T14:08:40Z [INFO]