Re: Having trouble compiling cryptopp with vs 2013 for x86_64

2017-11-29 Thread MalleeswaraReddy s 
On linux  and mac , crypto cpp library with Qt worked correctlry.

On windows msvc 2015 64 bit + Qt 5.9 getting error.

--

"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe" -f 
Makefile.Release

link /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /DLL /SUBSYSTEM:WINDOWS 
/OUT:..\plugins\win\cryptoplugin.dll 
@C:\Users\ernds\AppData\Local\Temp\nmD403.tmp

Creating library ..\plugins\win\cryptoplugin.lib and object 
..\plugins\win\cryptoplugin.exp

cryptopp.lib(rijndael.obj) : error LNK2019: unresolved external symbol 
Rijndael_Enc_AdvancedProcessBlocks referenced in function "public: virtual 
unsigned __int64 __cdecl 
CryptoPP::Rijndael::Enc::AdvancedProcessBlocks(unsigned char const 
*,unsigned char const *,unsigned char *,unsigned __int64,unsigned int)const 
" (?AdvancedProcessBlocks@Enc@Rijndael@CryptoPP@@UEBA_KPEBE0PEAE_KI@Z)

cryptopp.lib(integer.obj) : error LNK2019: unresolved external symbol 
Baseline_Add referenced in function "public: virtual class 
CryptoPP::Integer & __cdecl CryptoPP::ModularArithmetic::Accumulate(class 
CryptoPP::Integer &,class CryptoPP::Integer const &)const " 
(?Accumulate@ModularArithmetic@CryptoPP@@UEBAAEAVInteger@2@AEAV32@AEBV32@@Z)

cryptopp.lib(integer.obj) : error LNK2019: unresolved external symbol 
Baseline_Sub referenced in function "public: virtual class 
CryptoPP::Integer & __cdecl CryptoPP::ModularArithmetic::Accumulate(class 
CryptoPP::Integer &,class CryptoPP::Integer const &)const " 
(?Accumulate@ModularArithmetic@CryptoPP@@UEBAAEAVInteger@2@AEAV32@AEBV32@@Z)

cryptopp.lib(sha.obj) : error LNK2019: unresolved external symbol 
X86_SHA256_HashBlocks referenced in function "public: virtual unsigned 
__int64 __cdecl CryptoPP::SHA224::HashMultipleBlocks(unsigned int const 
*,unsigned __int64)" (?HashMultipleBlocks@SHA224@CryptoPP@@UEAA_KPEBI_K@Z)

..\plugins\win\cryptoplugin.dll : fatal error LNK1120: 4 unresolved 
externals

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\BIN\x86_amd64\link.EXE"' : return code '0x460'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\BIN\nmake.exe"' : return code '0x2'

Stop.

NMAKE : fatal error U1077: 'cd' : return code '0x2'

Stop.

01:55:20: The process "C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\BIN\nmake.exe" exited with code 2.

Error while building/deploying project cryptoplugin (kit: Qt 5.9.2 
(msvc2015_64))

The kit Qt 5.9.2 (msvc2015_64) has configuration issues which might be the 
root cause for this problem.

When executing step "Make"


If any body have idea, please let me know


thanks in advance.

--

On Wednesday, April 6, 2016 at 10:26:13 PM UTC+5:30, Freddy Martinez wrote:
>
> Hi guys... I have the cryptopp code inside my Qt Project and before I try 
> to compile it with vs 2013, I always compile it with mingw and everything 
> was fine. Now, I had download the Qt 5.5.1 version for vs 2013 and I'm 
> getting this linker error:
>
> gcm.obj : error LNK2019: unresolved external symbol 
> GCM_AuthenticateBlocks_2K referenced in function "protected: virtual 
> unsigned __int64 __cdecl CryptoPP::GCM_Base::AuthenticateBlocks(unsigned 
> char const *,unsigned __int64)" 
> (?AuthenticateBlocks@GCM_Base@CryptoPP@@MEAA_KPEBE_K@Z)
>
> gcm.obj : error LNK2019: unresolved external symbol 
> GCM_AuthenticateBlocks_64K referenced in function "protected: virtual 
> unsigned __int64 __cdecl CryptoPP::GCM_Base::AuthenticateBlocks(unsigned 
> char const *,unsigned __int64)" 
> (?AuthenticateBlocks@GCM_Base@CryptoPP@@MEAA_KPEBE_K@Z)
>
> integer.obj : error LNK2019: unresolved external symbol Baseline_Add 
> referenced in function "int __cdecl CryptoPP::Add(unsigned __int64 
> *,unsigned __int64 const *,unsigned __int64 const *,unsigned __int64)" 
> (?Add@CryptoPP@@YAHPEA_KPEB_K1_K@Z)
>
> integer.obj : error LNK2019: unresolved external symbol Baseline_Sub 
> referenced in function "int __cdecl CryptoPP::Subtract(unsigned __int64 
> *,unsigned __int64 const *,unsigned __int64 const *,unsigned __int64)" 
> (?Subtract@CryptoPP@@YAHPEA_KPEB_K1_K@Z)
>
> panama.obj : error LNK2019: unresolved external symbol Panama_SSE2_Pull 
> referenced in function "protected: virtual void __cdecl 
> CryptoPP::PanamaCipherPolicy CryptoPP::ByteOrder,1> >::CipherResynchronize(unsigned char *,unsigned char 
> const *,unsigned __int64)" 
> (?CipherResynchronize@?$PanamaCipherPolicy@U?$EnumToType@W4ByteOrder@CryptoPP@@$00@CryptoPP@@@CryptoPP@@MEAAXPEAEPEBE_K@Z)
>
> rdrand.obj : error LNK2019: unresolved external symbol 
> MASM_RRA_GenerateBlock referenced in function "public: virtual void __cdecl 
> CryptoPP::RDRAND::GenerateBlock(unsigned char *,unsigned __int64)" 
> (?GenerateBlock@RDRAND@CryptoPP@@UEAAXPEAE_K@Z)
>
> rdrand.obj : error LNK2019: unresolved external symbol 
>

Re: Crypto++ 5.6.5 and Valgrind

2017-11-29 Thread Ingo Naumann 
Hi,

>> You might be able to work around it by removing the `-march=native`
>> from CXXFLAGS. Open GNUmakefile and delete the line that adds it.
>> However, you will loose a fair amount of performance because the
>> source files depend on some of the options included in
>> `-march=native`.
Wo-ho! This one saves my day! Valgrind's smiling at me again. :)

I.

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Change Doxygen comment stle from //! to ///

2017-11-29 Thread Jeffrey Walton 
Hi Everyone,

I'd like to change the Doxygen comment style from //! to ///.

It will be a massive change, but it should help some tools.

Visual Studio appears to be a lost cause. I know it does not work with //! 
style. It appears Microsoft will only provide Intellisense with C# style 
comments, where a /// is followed by an XML tag. Also see 
https://developercommunity.visualstudio.com/content/problem/71324/intellisense-not-working-with-doxygen-comment-styl.html

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Crypto++ 5.6.5 and Valgrind

2017-11-29 Thread Jeffrey Walton 
On Wed, Nov 29, 2017 at 9:34 AM, Jeffrey Walton  wrote:
> On Wed, Nov 29, 2017 at 9:16 AM, Ingo Naumann  wrote:
>> ...
>> ...
>> So now I've upgraded to valgrind-3.14.0.GIT (cloned ten minutes ago) but it
>> yields the same result. I'm hitting illegal instructions in both
>> "cryptest.exe" as well as my own software (during ECDSA key generation).
>>
>> But if nobody else can confirm this I'll probably either re-install and
>> start from a scratch and/or perform a memory check with another tool and see
>> what comes up.
>
> I'm fairly certain a reinstall is going to be a waste of your time,
> but I could be wrong. You might try searching for the opcodes that are
> causing the problem. They have probably already been reported (I
> reported about a half dozen or so myself). Also see
> https://bugs.kde.org/buglist.cgi?bug_status=__all__=illegal%20instruction

My bad... Here's a better query. It returns results just for Valgrind.
https://bugs.kde.org/buglist.cgi?bug_status=__all__=illegal%20instruction_redirect=1=valgrind

If you start running searches on your own, be sure to select All
issues (open + closed). The team sometimes closes a report for missing
opcodes as "won't fix".

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Crypto++ 5.6.5 and Valgrind

2017-11-29 Thread Jeffrey Walton 
On Wed, Nov 29, 2017 at 9:16 AM, Ingo Naumann  wrote:
> ...
> We work around it by building Valgrind from sources. Its fairly easy once
> you install the packages "automake autoconf libtool". Also see
> http://valgrind.org/downloads/repository.html.
>
> Hmmm. I had built valgrind from the "current" source, ie version 3.13
> from June 2017.
>
> So now I've upgraded to valgrind-3.14.0.GIT (cloned ten minutes ago) but it
> yields the same result. I'm hitting illegal instructions in both
> "cryptest.exe" as well as my own software (during ECDSA key generation).
>
> But if nobody else can confirm this I'll probably either re-install and
> start from a scratch and/or perform a memory check with another tool and see
> what comes up.

I'm fairly certain a reinstall is going to be a waste of your time,
but I could be wrong. You might try searching for the opcodes that are
causing the problem. They have probably already been reported (I
reported about a half dozen or so myself). Also see
https://bugs.kde.org/buglist.cgi?bug_status=__all__=illegal%20instruction

You might be able to work around it by removing the `-march=native`
from CXXFLAGS. Open GNUmakefile and delete the line that adds it.
However, you will loose a fair amount of performance because the
source files depend on some of the options included in
`-march=native`.

You best bet at this point is probably work from Master. After 5.6.5
we changed the model to Base+SIMD. Base C++ files are fine without an
ISA, and SIMD files get an ISA added when needed. As far as I know,
lack of `-march=native` no longer has a material affect on
performance. Base+SIMD also had the effect of side-stepping most the
missing VEX codecs. I don't recall experiencing the problem since we
switched to Base+SIMD.

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Crypto++ 5.6.5 and Valgrind

2017-11-29 Thread Ingo Naumann 
Hi,

Thanks a lot for your answer.

> I've just upgraded from an older version to Crypto++ 5.6.5 and my
> Valgrind is seriously unhappy about it. Even the "cryptest.exe v"
> command crashes with "Illegal instruction" (details on request) when
> calling it with
>
>
> []
> We work around it by building Valgrind from sources. Its fairly easy
> once you install the packages "automake autoconf libtool". Also see
> http://valgrind.org/downloads/repository.html.

Hmmm. I had built valgrind from the "current" source, ie version
3.13 from June 2017.

So now I've upgraded to valgrind-3.14.0.GIT (cloned ten minutes ago) but
it yields the same result. I'm hitting illegal instructions in both
"cryptest.exe" as well as my own software (during ECDSA key generation).

But if nobody else can confirm this I'll probably either re-install and
start from a scratch and/or perform a memory check with another tool and
see what comes up.

Ingo

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.