Brian May

Is it possible that with the latest libraries my code has grown too big for the esp32? Good: ``` esptool.py v4.1 Creating esp32 image... Merged 25 ELF sections Successfully created...

I think my dev mode was already using `z`. Tried release mode which uses `s`, and that fixes the problem. Wondering what I can do to reduce my image size....

What does LTO stand for? I know of LTO tape, somehow I don't think that is it. Sounds like a good optimisation to have. Hmmm. I think ESP32 chips come...

I tried: ``` # ESP-IDF Partition Table # Name, Type, SubType, Offset, Size, Flags nvs, data, nvs, 0x9000, 0x6000, phy_init, data, phy, 0xf000, 0x1000, factory, app, factory, 0x10000, 3M, ```...

Also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017244 which has a different list of missing symbols.

This is my proposed solution to add the symbol back in but use the symbol from the OS (If I got it correct). ```diff From: Brian May Date: Fri, 26...

Note that in the process of upgrading the Debian package, there are two distinct steps. 1. Upgrade libroken package. 2. Upgrade the Heimdal applications that use libroken package. As far...

Oh, I completely forgot another point. Any library that depends on libkrb5 implicitly depends on libroken because libkrb5 depends on libroken. So even though application X may not directly depend...

@erayaslan Not sure who you are asking. If you are asking me, yes, I could do that, but then I would be forever out of sync with upstream. As in...

Good point. A serious complication in this case is that the set of symbols built depends on what version of libc is used to build the library. And upstream Heimdal...