Alexander Huszagh

Fix the above environment variables, update the README to mention the new target, and this is ready for merging. Nice work, thank you.

Do you mind if I make some changes directly to this PR? I can fix up some of the stuff with the template file, so it uses the correct placeholders...

> Apologies for the late response, please make any changes you see fit! I'll be updating based on your earlier comment right now No worries, you're doing us a favor....

> What changes are you making to the configuration file? I already encountered an issue with my own use-case; the embedded device I'm developing for is running `libuClibc-0.9.33.2.so`, however in...

The other is allowing you to change the uclibc, gcc, and other versions when configuring using placeholders. That needs the above PR to merge the though before uclibc configuration works....

[#1087](https://github.com/cross-rs/cross/pull/1087) is getting merged now, so I'll post the diff for my config file and yours (and show you how to configure it for an older uclibc version): ```bash cargo...

We might also need to provide a config for the mirrors, actually, since `uclibc-ng` only supports [1.0+](https://uclibc.org/news.html), and the original `uclibc` is [pre-1.0](https://uclibc.org/downloads/). I can do this by auto-detecting the...

I'm running into a bug when pushing to this repository. If you apply the following patch then squash the commit history, this is ready for merging. Since the upstream configuration...

For the pre-1.0 uclibc, I think it's fine as-is (that is, it can be configured to work but only post-1.0 is tested), since the original uclibc has been hard-forked and...

Any update on this? If no, I can merge the changes myself and then squash the commit history, give you the co-author, and merge. Is that fine?