Sorry about the vagueness . I am referring to the following repos:
Teletype repo - main teletype code. Describes both libavr32 build approach and docker approach, providing documentation on both.
Libavr32 repo - main libavr32 code. If you choose the libavr32 build approach, you will come here. Before you build libavr32, you need to build the toolchain first. In the windows section of readme, it points to…
Your fork of the avr32 toolchain - this and other forks of avr32 toolchain all have the same problem. Their config.mks refer to atmel patch url that doesn’t exist anymore and instead need to be replaced with a new url or have the file manually added to the folder so that the build can pass.
Hope that helps explain what I have seen so far.