Roman Valls Guimera

@briansmith Thanks for the assistance and patience, I finally managed to sort this out in https://github.com/aws/aws-sam-build-images/pull/26#issuecomment-938311869

Reopening since this is not fully solved. @nmoutschen got one step forward using `cross` in https://github.com/aws-samples/serverless-rust-demo/issues/2#issuecomment-949423936: ``` % CC_aarch64_unknown_linux_gnu=clang cross build --target aarch64-unknown-linux-gnu (...) error: failed to run custom build...

Similar issue noted on https://github.com/briansmith/ring/issues/1374, this issue tracks non-MUSL cross-compiling of `ring` though.

Sans `cross`, with just `cargo`, there seems to be the same symptom (/cc @nmoutschen), which can make debugging potentially easier... ``` % RUSTFLAGS='-C target-cpu=apple-a14' CC_aarch64_unknown_linux_gnu=clang cargo build --target aarch64-unknown-linux-gnu Compiling...

Scratch the previous observations, passing the ("right"?) `TARGET_CFLAGS` [so that `ring` can find the system's `assert.h`](https://stackoverflow.com/questions/38948058/homebrew-installed-clang-fails-to-find-headers-on-mac-os-x): `RUST_BACKTRACE=1 RUSTFLAGS='-C target-cpu=neoverse-n1' TARGET_CFLAGS="-I /Library/Developer/CommandLineTools/SDKs/MacOSX11.3.sdk/usr/include" CC_aarch64_unknown_linux_gnu=clang cargo build --target aarch64-unknown-linux-gnu` We run into a...

And then running with the latest stable Rust 1.56 **without** setting `CC_aarch64_unknown_linux_gnu=clang` (defaulting to GCC?): ``` % RUSTFLAGS='-C target-cpu=neoverse-n1' cargo build --release --target aarch64-unknown-linux-gnu Compiling libc v0.2.105 Compiling cc v1.0.71...

Hi @jcgomes90, could you share a bit more of this parquet column-level write code? I'm about to write some code that does a "migration" from a parquet file towards another...

Oh, nevermind, I think I'll use `parquet_derive` (https://github.com/ccakes/parquet_derive) for now while https://github.com/apache/arrow/pull/4140 gets merged/worked on by @xrl, @sunchao et al 👍

@fabbarix @Leo-PL Count me in as well for that binary please, I've been following this with attention and I do have a couple of those devices coming in my mail...

I've just tried to load it in Ghidra with [this extension](https://github.com/hank/ghidra-esp8266), but there seems to be an assumption with the loader https://github.com/hank/ghidra-esp8266/issues/3 that all ESP8266 firmwares must have: ```java public...