Most stand alone compilers for bootstrapping a new system are missing from recent releases:

ftp://ftp.freepascal.org/pub/fpc/dist/3.0.4/bootstrap/ [has 7 bootstrap compilers]
ftp://ftp.freepascal.org/pub/fpc/dist/3.2.0/bootstrap/ [has 2 bootstrap compilers]
ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/bootstrap/ [emply]

I have a feature request. Instead of having a
"...dist/[fpc_version]/bootstrap" directory, use the cpu-os directory and automatically create a bootstrap compiler archive during the build process. Like this:

ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/aarch64-linux/fpc-3.2.2.aarch64-linux_bootstrap.gz ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/arm-android/fpc-3.2.2.arm-android_bootstrap.gz ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/x86_64-linux/fpc-3.2.2.x86_64-linux_bootstrap.gz ...

Or maybe use the same archive name for each:
ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/aarch64-linux/bootstrap_compiler.gz ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/arm-android/bootstrap_compiler.gz ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/x86_64-linux/bootstrap_compiler.gz ...

Having a consistent location and naming convention would make it easier to create automated build systems that download and bootstrap a new fpc and lazarus build directly from git on a new system. The alternative is to download a large archive (e.g. ~83 MB for fpc-3.2.2.x86_64-linux.tar) and extract a bootstrap compiler (e.g. ppcx64 is only ~4 MB) from deep inside (three levels deep of archives).