Am 08.11.2017 00:29 schrieb "Jeffrey Walton" :
The 32-bit prompt looks off to me. It says MINGW32 as expected, but the
compiler is building for (targeting) 64-bit executable:
test@asus-windows MINGW32 ~/cryptopp
$ uname -a
MINGW32_NT-6.3 asus-windows8
On Tue, Nov 7, 2017 at 1:53 PM, wrote:
> Here are three more experiments building three different CryptoPP versions
> with the latest 64-bit/64-bit MingW compiler.
>
> Since I already have a solution, this should have no sense of urgency. Let
> me know if there is something
Here are three more experiments building three different CryptoPP versions
with the latest 64-bit/64-bit MingW compiler.
Since I already have a solution, this should have no sense of urgency. Let
me know if there is something specific I can do to help.
*I fixed my compiler version. Now it is
Hi Jeff,
Am 06.11.2017 20:20 schrieb "Jeffrey Walton" :
How does this fancy you:
$ git diff
diff --git a/socketft.cpp b/socketft.cpp
index 454eaa5..20cda22 100644
--- a/socketft.cpp
+++ b/socketft.cpp
@@ -30,6 +30,14 @@
# include
#endif
+// From
On Monday, November 6, 2017 at 1:36:36 PM UTC-5, Marcel Raad wrote:
>
> Hi Jeff,
>
> Am 06.11.2017 19:29 schrieb "Jeffrey Walton" :
>
> Should we remove that header or comment it out? I don't know anyone
> developing on Windows 2000 anymore. Windows XP and Windows 2003 are
>
Hi Jeff,
Am 06.11.2017 19:29 schrieb "Jeffrey Walton" :
Should we remove that header or comment it out? I don't know anyone
developing on Windows 2000 anymore. Windows XP and Windows 2003 are
the floors for the development shops I work with.
unfortunately that wouldn't help
On Mon, Nov 6, 2017 at 1:20 PM, Marcel Raad wrote:
>
> Am 06.11.2017 18:55 schrieb :
>
> g++ -DNDEBUG -g2 -O3 -pthread -pipe -c socketft.cpp
> socketft.cpp:36:23: fatal error: wspiapi.h: No such file or directory
> # include
>^
>
Hi Gene,
Am 06.11.2017 18:55 schrieb :
g++ -DNDEBUG -g2 -O3 -pthread -pipe -c socketft.cpp
socketft.cpp:36:23: fatal error: wspiapi.h: No such file or directory
# include
^
compilation terminated.
make: *** [socketft.o] Error 1
you can define
Thanks for checking my Win32/Win64 hybrid. I had no idea I was doing that.
I did try your latest version, and got pretty far with my setup:
g++ -DNDEBUG -g2 -O3 -pthread -pipe -c rsa.cpp
In file included from filters.h:22:0,
from pubkey.h:48,
from rsa.h:12,
On Mon, Nov 6, 2017 at 9:28 AM, wrote:
> Here are the details on the two MingW compilers I used, with 630 first:
>
> C:\data\code>g++ -v
> Using built-in specs.
> COLLECT_GCC=g++
> COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/6.3.0/lto-wrapper.exe
> Target: mingw32
Hi Jeff,
Here are the details on the two MingW compilers I used, with 630 first:
C:\data\code>g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/6.3.0/lto-wrapper.exe
Target: mingw32
Configured with: ../src/gcc-6.3.0/configure
On Saturday, November 4, 2017 at 3:45:32 PM UTC-4, usbg...@gmail.com wrote:
>
> I got it fixed... kind of.
>
> On a hunch, I switched back to MinGW4.72, and CryptoPP565 still failed to
> build. After trying all permutations of my setups, here is what I found:
>
> MinGW CryptoPP
> 630
On Sunday, November 5, 2017 at 5:08:08 PM UTC-5, Marcel Raad wrote:
>
> On Saturday, November 4, 2017 at 10:36:30 PM UTC+1, Jeffrey Walton wrote:
> > I tired to setup a MinGW testing environment several times but it either
> (1) never worked or (2) broke immediately. On the rare occasions I
On Monday, November 6, 2017 at 7:23:41 AM UTC-5, Jeffrey Walton wrote:
>
>
>
> On Sunday, November 5, 2017 at 5:08:08 PM UTC-5, Marcel Raad wrote:
>>
>> On Saturday, November 4, 2017 at 10:36:30 PM UTC+1, Jeffrey Walton wrote:
>> > I tired to setup a MinGW testing environment several times but
On Sunday, November 5, 2017 at 5:08:08 PM UTC-5, Marcel Raad wrote:
>
> On Saturday, November 4, 2017 at 10:36:30 PM UTC+1, Jeffrey Walton wrote:
> > I tired to setup a MinGW testing environment several times but it either
> (1) never worked or (2) broke immediately. On the rare occasions I
On Saturday, November 4, 2017 at 10:36:30 PM UTC+1, Jeffrey Walton wrote:
> I tired to setup a MinGW testing environment several times but it either (1)
> never worked or (2) broke immediately. On the rare occasions I could compile
> and link I was able to file some MinGW bug reports but they
On Saturday, November 4, 2017 at 3:45:32 PM UTC-4, usbg...@gmail.com wrote:
>
> I got it fixed... kind of.
>
> On a hunch, I switched back to MinGW4.72, and CryptoPP565 still failed to
> build. After trying all permutations of my setups, here is what I found:
>
> MinGW CryptoPP
> 630
I got it fixed... kind of.
On a hunch, I switched back to MinGW4.72, and CryptoPP565 still failed to
build. After trying all permutations of my setups, here is what I found:
MinGW CryptoPP
630 565fail
630 562fail
472
Hi Jeff,
thanks for your reply. I have never used git, so it took some time to
decipher the patch format. I applied it manually to my config.h file, but
got more errors, not less.
Could you post a complete config.h file? I hope that is enough to fix this.
Thanks,
Gene
On Friday, November
On Friday, November 3, 2017 at 6:09:20 PM UTC-4, usbg...@gmail.com wrote:
>
> I am building CryptoPP 5.65 with MingW 6.3.0.
>
> make gives an error:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *c:\devdir\>makeg++ -DNDEBUG -g2 -O2 -march=native -pipe -c cryptlib.cppIn
> file included from
20 matches
Mail list logo