Missing source archives about buildscripts HOT 4 CLOSED

Same issue as #51

Since you will likely ask what I'm trying to achieve.
I tried building Swiss from source to be met by a missing symbol in libogc, which lead me to attempt to build a random libogc fork with the latest devkitppc installed:

$ pacman -Q
devkit-env 1.0.1-2
devkitPPC r38-1
devkitPPC-gdb 9.2-1
devkitppc-rules 1.1.0-1
devkitpro-keyring 20180316-1
gamecube-examples 20200609-1
gamecube-pkg-config 0.28-5
gamecube-tools 1.0.2-1
general-tools 1.2.0-2
libfat-ogc 1.1.5-2
libogc 2.1.0-1
ppc-pkg-config 0.28-5

But I'm getting a compilation error on libogc/system.c

system.c
/home/bitscher/outsrc/libogc/libogc/system.c: In function '__init_syscall_array':
/home/bitscher/outsrc/libogc/libogc/system.c:296:2: error: '__syscalls' undeclared (first use in this function); did you mean '__syscall_exit'?
  296 |  __syscalls.sbrk_r = __libogc_sbrk_r;
      |  ^~~~~~~~~~
      |  __syscall_exit

Turns out that __syscalls is not defined in /opt/devkitpro/devkitPPC/powerpc-eabi/include/sys/iosupport.h so I was probing a little.

from buildscripts.

Please do not use either old versions of the tools or build random libogc forks in order to "fix" code that should build with stock components. You should report an issue with Swiss and ask that code is upstreamed rather than having incompatible forks.

from buildscripts.

The reported issue was not about a fork of libogc not building, it was about the build scripts of devkitpro failing because of missing source archives.

from buildscripts.

We discourage end users from building the tools and prefer that everything is managed via devkitPro pacman. This would help to ensure that people can actually build each other's projects if certain people didn't insist on not upstreaming code. We cannot guarantee that tools you build yourself will function properly and provide no support for self built tools or building from source.

We especially don't provide support for incompatible forks of our code.

from buildscripts.