xxhash | native implementation of the excellent XXHash hashing

Check the header file for all of the functions available. This one looks like the one you need. You will need to cast your buffers as (void *).

fast-lzma2.h

In case somebody comes along a similar issue. These was a library in my included libraries that was using the static linkage (mpirxx.lib). A good way to debug this is to put /VERBOSE:LIB in your linker options. Then build and go to your Output windows where you can see which is the first library to trigger this error chain.

Thanks to Alan Birtles for the help.

I've checked MySQL source code and built-in functions and I could not find any way to run XXHash in MySQL routines. It seems XXHash is used by MySQL internally and it is not user-visible.

In order to run XXHash in MySQL routines, I have developed a plugin in case anyone needs to use XXHash algorithm in MySQL server.

This plug in can be found here: Github repository for xxhash_mysql_plugin.

After installing plug in you can run the xxhash function in your select statements as below:

A likely reason is that your project is missing xxhash.c in its list of source files to compile. Each *.c file becomes an object file, which is linked during the last stage. So without it, no symbol defined in xxhash.c is ever created.

Another way to solve this issue is to #define XXH_INLINE_ALL just before #include "xxhash.h". This will inline the code, as if it was present in the local source file, and as a consequence, it will not need to link to another object file. Inlining is also good for performance on small data, but increases binary size.

The LoadBalancerSettings.ConsistentHashLB flag is for an Envoy configuration, and there's more detail in Envoy's Load Balancing Docs:

The ring/modulo hash load balancer implements consistent hashing to upstream hosts. The algorithm is based on mapping all hosts onto a circle such that the addition or removal of a host from the host set changes only affect 1/N requests. This technique is also commonly known as “ketama” hashing.

It's an hash algorithm that decreases the impact of servers being added and removed from Envoy's balancing pool (e.g. the servers behind a VirtualService).

Without such an algorithm, adding a single server to the pool causes hashes to map to different servers:

We wrote ketama to replace how our memcached clients mapped keys to servers...whenever we added or removed servers from the pool, everything hashed to different servers, which effectively wiped the entire cache.

Back to Istio - Envoy's docs again note:

A consistent hashing load balancer is only effective when protocol routing is used that specifies a value to hash on.

which means - specify a header to generate the hash from. From Istio docs:

httpHeader | string | REQUIRED. The name of the HTTP request header that will be used to obtain the hash key. If the request header is not present, the load balancer will use a random number as the hash, effectively making the load balancing policy random.

I am adding this as the answer regarding Gabriel's suggestion that it might help other people in the future too.

I cleaned the Nuget cache, repaired my ".NET Core SDK 2.0.2" installation, did a "Solution and Project Cleanup" and rebuilt my project, and the Encoding.RegisterProvider(CodePagesEncodingProvider.Instance) code started to work fine.

Now I can access the extra code pages using the Encoding.GetEncoding() method, however I still get the same list of encodings from Encoding.GetEncodings() method after adding the extra encodings.

From my perspective the Encoding.GetEncodings() method should return all the encodings available after more of them have been added.

Please follow this method to install from compiled binary. Download the OpenLiteSpeed binary from the Download page or use the wget command to download it from the console, here we use v1.6.4 as example:

Looking at the log file you can see:

Many thanks to the user dugan on linuxquestions.org! He solved my problem here.

I just had to install Qt from a different source (I used the Qt installer, as mentioned in the question), to have a different version of it in another location. The reason for that is that many programs on Debian rely on an earlier version of Qt, so just updating it would break a lot, that's also why Synaptic&Co. don't update it.
Then I had to add the binary to the PATH variable, like so: