Yes, you were right. I was mixing the header files. I removed all junk 
files and installed cryptopp again from repo. Works fine now. Thank you. :)

Dne středa 17. ledna 2018 21:56:16 UTC+1 Jeffrey Walton napsal(a):
>
> On Wed, Jan 17, 2018 at 2:43 PM,  <[email protected] <javascript:>> 
> wrote: 
> > Still the same. I tried to uninstall cryptopp and cryptopp-devel 
> packages, 
> > then do dnf clean all, then install the packages back and still the same 
> > error. The problem is somewhere in this line: 
> > CryptoPP::FileSource createFileFingerprint(filePath.c_str(), true, new 
> > CryptoPP::HashFilter(sha256Hasher, new CryptoPP::HexEncoder(new 
> > CryptoPP::StringSink(fileFingerprint)))); 
>
> When you make, pipe your output through c++filt: 
>
>     g++ main.cpp -o main -lcryptopp 2>&1 | c++filt 
>
> Then post the error message. 
>
> I've got a feeling you are mixing and matching header files. Maybe the 
> you are using upcoming Crypto++ 6.0 header files and a Crypto++ 5.6.3 
> library from Fedora. That's because of: 
>
>      undefined reference to 
> CryptoPP::BufferedTransformation::Skip(unsigned long) 
>
> The 'unsigned long'  is _now_ the word64 type, but that change 
> occurred at Crypto++ 5.6.5. At 5.6.4 and below a word64 was 'unsigned 
> long long'. At Crypto++ 5.6.5 it was changed to a 'unsigned long' 
> under LP64 data models. 
>
> You should not be missing a "BufferedTransformation::Skip(unsigned 
> long)". If you are missing anything, it should be 
> "BufferedTransformation::Skip(unsigned long long)". 
>
> The change is detailed under "Notes for Distros" at 
> https://www.cryptopp.com/release565.html . 
>
> Jeff 
>

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to