MMC is my mortal enemy :neocat_gun:
*(Need to figure out issue with clocks so I can dual-boot this nugget)*
elly
elly
npub19wj8...g8gs
Computer-touching nerd, infodumping about Linux and firmware development.
Opinions are my own and blah blah.
Pronouns: she/her | they/them
LANG: en, pl, ja (prov)
GitHub: https://github.com/ellyq
Sh**post containment zone: https://1.6.0.0.8.0.0.b.e.d.0.a.2.ip6.arpa/@ellyqw
Greetings, humans. We come in peace.
If we refer to multi-core systems as "Multi-Processor", does it mean systems with multiple, multi-core processors should be referred to as "Multi-Multi-Processor?"
Conversation with friend that knows rust:
M: How do you expect people to learn rust? It's so freakin' broken.
F: What do you mean "broken"? Why?
M: Half of the time I'm trying to even build the bloody thing I run into stupid issues.
F: Well, you must be doing something wrong, show me an example.
M: Here you go:
```
error: failed to run custom build command for `libfdt-sys v0.0.2`
Caused by:
process didn't exit successfully: `/mnt/Optane/toolchain/fdtviz/target/debug/build/libfdt-sys-3031182c5b22e2c2/build-script-build` (exit status: 101)
[...]
cargo:rerun-if-changed=libfdt/libfdt/libfdt.h
--- stderr
libfdt/libfdt/libfdt_env.h:10:10: fatal error: 'stdbool.h' file not found
thread 'main' (3832) panicked at /home/elly/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libfdt-sys-0.0.2/build.rs:45:10:
Unable to generate bindings: ClangDiagnostic("libfdt/libfdt/libfdt_env.h:10:10: fatal error: 'stdbool.h' file not found\n")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
/mnt/Optane/toolchain/fdtviz main find /usr/lib/* -name 'stdbool.h' 101 ✘
/usr/lib/clang/21/include/stdbool.h
/usr/lib/gcc/aarch64-linux-gnu/15/include/stdbool.h
/usr/lib/gcc/x86_64-redhat-linux/15/include/stdbool.h
```
F: What the fuck :neocat_floof_explode:
M: Yeah, you know what... I think I'm just gonna stick with C for now :akko_giggle:
