devkitPro

devkitARM release 56 is now available via pacman. Use sudo (dkp-)pacman -Syu to update or sudo (dkp-)pacman -S devkitARM to install.

devkitARM release 56

• update binutils to 2.36.1
• update gcc to 11.1.0
• update newlib to 4.1.0
• Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience.

Full details of gcc 11 changes can be found at https://gcc.gnu.org/gcc-11/

Of particular note is the stringop-overflow/stringop-overread/array-bounds warnings that come from writing directly to literal connstants cast as pointers. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 for example. These warnings are harmless and can be safely ignored. Upstream gcc hopes to address this issue in the near future.

----

This month, we have the following Patrons to whom we would like to give our most sincere thanks! (If you are a Patron and do not wish to be publicly listed, please let us know through any contact platform)

Michael Theall
TuxSH
Lily Foster
Kaeru Team
Ray Haleblian
Jeremy S Postelnek, Trevor Rudolph
mGBA
Mack Eugene, Tiago Nascimento, Extrems, Rajveer Aujla, Ben Morris, TheoUnderStars, Brandon, Miras Absar, rsn8887
Hamcha, Jon Bell
JerRy, Craig Richardson, Andrey Legchilin, Anders Persson, Toby Hutton, Thomas Finch, Kim Rosenbohm, Gustavo Valiente, Daniel 'dbeef' Zalega, Admiral H. Curtiss, M4xw, Lollie

devkitARM-gdb is now updated with the latest gdb 10.2 and the windows binaries are now no longer dependent on DLLs outside stock windows DLLs. As above use sudo (dkp-)pacman -Syu to update or sudo (dkp-)pacman -S devkitARM-gdb to install.

$ sudo dkp-pacman -Syu
:: Synchronizing package databases...
dkp-libs is up to date
error: failed retrieving file 'dkp-linux.db' from downloads.devkitpro.org : The requested URL returned error: 404
error: failed to update dkp-linux (unexpected error)
error: failed to synchronize all databases

This is a recent thing, as I must have updated just a week or so ago. Happens on more than one system, so it can't be a local problem.

The location of the linux repositories was rearranged last year when I brought up aarch64 binaries and the old files were removed recently with some server housekeeping. If you're using dkp-pacman then update with the latest pacman binaries from https://github.com/devkitPro/pacman/releases/latest. If you modified an existing pacman then use the updated URLs from wiki/devkitPro_pacman#Customising_Exist ... an_Install