hiya.
the new compat32 sets rearrangement has broken the GCC 12 build, due to dropping "gcc=10" tag in some places. that's a minor issue, and i'll fix that soon (though having looked closer at the first "grep -r" output below, i see most of these are affected. i'll just initially be fixing arm64 and amd64.) however, while looking at this i noticed that there's been a major explosion in sets that shouldn't happen. compare matches for "libasan.so.5.0" betweeen new/old: yesterday-when-i-was-mad distrib/sets/lists> grep -r asan.so.5.0 . ./base/shl.mi:./usr/lib/libasan.so.5.0 base-sys-shlib cxx,gcc=10 ./debug/shl.mi:./usr/libdata/debug/usr/lib/libasan.so.5.0.debug comp-sys-debug debug,cxx,gcc=10 ./base32/ad.aarch64:./usr/lib/eabi/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.aarch64:./usr/lib/eabihf/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mips64eb:./usr/lib/64/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mips64eb:./usr/lib/o32/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mips64el:./usr/lib/64/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mips64el:./usr/lib/o32/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mipsn64eb:./usr/lib/64/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mipsn64eb:./usr/lib/o32/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mipsn64el:./usr/lib/64/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.mipsn64el:./usr/lib/o32/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.powerpc64:./usr/lib/powerpc/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/ad.riscv64:./usr/lib/rv32/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/md.amd64:./usr/lib/i386/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./base32/md.sparc64:./usr/lib/sparc/libasan.so.5.0 base-compat-shlib compat,gcc,cxx ./debug32/ad.aarch64:./usr/libdata/debug/usr/lib/eabi/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.aarch64:./usr/libdata/debug/usr/lib/eabihf/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mips64eb:./usr/libdata/debug/usr/lib/64/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mips64eb:./usr/libdata/debug/usr/lib/o32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mips64el:./usr/libdata/debug/usr/lib/64/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mips64el:./usr/libdata/debug/usr/lib/o32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mipsn64eb:./usr/libdata/debug/usr/lib/n32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mipsn64eb:./usr/libdata/debug/usr/lib/o32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mipsn64el:./usr/libdata/debug/usr/lib/n32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.mipsn64el:./usr/libdata/debug/usr/lib/o32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.powerpc64:./usr/libdata/debug/usr/lib/powerpc/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/ad.riscv64:./usr/libdata/debug/usr/lib/rv32/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/md.amd64:./usr/libdata/debug/usr/lib/i386/libasan.so.5.0.debug comp-sys-debug debug,compat ./debug32/md.sparc64:./usr/libdata/debug/usr/lib/sparc/libasan.so.5.0.debug comp-sys-debug debug,compat vs in an older tree: yesterday-when-i-was-mad distrib/sets/lists> grep -r asan.so.5.0 . ./base/shl.mi:./usr/lib/libasan.so.5.0 base-sys-shlib compatfile,cxx,gcc=10 ./debug/shl.mi:./usr/libdata/debug/usr/lib/libasan.so.5.0.debug comp-sys-debug debug,compatfile,cxx,gcc=10 ie, there are just *two* entries for this file (the real file, and the debug file), and the rest is all derived from the "comaptfile" and "debug" tags. the new ones has 30 copies, spread across a number of files, all that will need editing as future GCCs appear. this is compounded across dozens of other files so there are now hundreds or perhaps thousands of unnecessary duplicated lines, in a couple of dozen of files. can someone please fix this? (nia is out for now, so maybe some other enterprising person can help :) thanks. .mrg.
