Fix enable LLVM for JIT compilation in CMake

[kitaisreal]

Changelog category (leave one):

• Bug Fix (user-visible misbehaviour in official stable or prestable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Enable build with JIT compilation by default.

[kitaisreal]

CMAKE_CROSSCOMPILING can be true even without cross compilation

This variable will be set to true by CMake if the [CMAKE_SYSTEM_NAME]
(https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_NAME.html#variable:CMAKE_SYSTEM_NAME) 
variable has been set manually (i.e. in a toolchain file or as a cache entry from the [cmake]

https://cmake.org/cmake/help/latest/variable/CMAKE_CROSSCOMPILING.html

[kitaisreal]

One of latest builds on master:
https://s3.amazonaws.com/clickhouse-builds/22.4/2db8d354c6f1b46968619acd0ae8f7f80cfbdb53/package_release/build_log.log

Mar 28 13:25:31 -- Adding contrib module msgpack-c (configuring with msgpack-c-cmake)
Mar 28 13:25:31 -- Adding contrib module cityhash102 (configuring with cityhash102)
Mar 28 13:25:31 -- Adding contrib module libfarmhash (configuring with libfarmhash)
Mar 28 13:25:31 -- Adding contrib module icu (configuring with icu-cmake)
Mar 28 13:25:31 -- Adding contrib module h3 (configuring with h3-cmake)
Mar 28 13:25:31 -- Adding contrib module mariadb-connector-c (configuring with mariadb-connector-c-cmake)
Mar 28 13:25:31 -- Adding contrib module llvm (configuring with llvm-cmake)
Mar 28 13:25:31 -- Not using LLVM
Mar 28 13:25:31 -- Adding contrib module libxml2 (configuring with libxml2-cmake)

[kitaisreal]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[kitaisreal]

@Felixoid our previous wrong fix affects only v22.3.2.2-lts v22.3.1.1262-prestable.
I will backport it to 22.3, will you please make release ?

[Felixoid]

Yep, we can release a new version

[kitaisreal]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[tavplubix]

@kitaisreal you forgot to take a look at failed tests before merging again:
Stateless tests (release, DatabaseReplicated, actions) - 02152_http_external_tables_memory_tracking
Stateless tests (release, actions) - 02152_http_external_tables_memory_tracking
Stateless tests (release, s3 storage, actions) - 02152_http_external_tables_memory_tracking
Stateless tests (release, wide parts enabled, actions) - 02152_http_external_tables_memory_tracking

This test was not flaky for last 3 weeks: http://a137ed393136a448a8a0b796e91304c4-2000240599.us-east-1.elb.amazonaws.com:8123/play?user=default#c2VsZWN0IAp0b1N0YXJ0T2ZEYXkoY2hlY2tfc3RhcnRfdGltZSkgYXMgZCwKY291bnQoKSwgZ3JvdXBVbmlxQXJyYXkocHVsbF9yZXF1ZXN0X251bWJlcikKZnJvbSBgZ2gtZGF0YWAuY2hlY2tzIHdoZXJlICcyMDIyLTAxLTAxJyA8PSBjaGVja19zdGFydF90aW1lIGFuZCB0ZXN0X25hbWU9JzAyMTUyX2h0dHBfZXh0ZXJuYWxfdGFibGVzX21lbW9yeV90cmFja2luZycgYW5kIHRlc3Rfc3RhdHVzIGluICgnRkFJTCcsICdGTEFLWScpIGdyb3VwIGJ5IGQgb3JkZXIgYnkgZA==

So seems like it was broken here somehow. I will try to revert.

[kitaisreal]

@tavplubix I take a look this change just revert other pull request that breaks LLVM compilation, everything must work as before.

[azat]

Stateless tests (release, actions) - 02152_http_external_tables_memory_tracking

The problem was in settings randomization, in particular max_block_size=67990 for 02152_http_external_tables_memory_tracking, fixed in #35745