There's a merged pull request on the void-packages repository

gcc: fix dynamic linker paths and default os library paths
https://github.com/void-linux/void-packages/pull/27269

Description:
Void used to mess with the dynamic linker paths, which is very wrong, so it's time to change that. The reason this was done was
because the lib32/64 symlinks were not available in unconfigured chroots (since base-files used to create them during configuration) and this has not been the case for a while, so there is nothing blocking this.

While at it, change the library paths to lib64 for 64-bit systems and lib32 for 32-bit systems. This merely changes the toolchain
and usually does not have much of an effect; dynamic libraries do not contain the paths (the search paths are controlled by
the dynamic linker). The lib32/64 symlinks are contained in base-files, so there is no harm in having this be consistent.

(no revbump: there is no harm in just preparing this before merging gcc10)

[ci skip]

@leahneukirchen 
@void-linux/pkg-committers