Martin Husemann writes: > On Thu, Feb 27, 2014 at 10:07:36AM +0100, J. Hannken-Illjes wrote: > > ./usr/include/g++/bits/sparc > > ./usr/include/g++/bits/sparc64 > > I asked Jörg to try (his MKCOMPAT=no clang build) with > > ./usr/include/g++/bits/sparc gcc,compat > ./usr/include/g++/bits/sparc64 gcc > > (the old state was obviosly incorrect, but so is the current one). > This is still incorrect for gcc 4.1, but I bet noone will notice.
as i said elsewhere -- the right solution here is to put those files into new mtree files in src/etc/mtree, and avoid creating them for the builds that "don't want them". (personally, i'd just always create them and have them be empty and ignored for any sort of build that doesn't put files in there. putting any marker (like gcc, or compat) on these subdirs means that they'll always be removed on some build types, ie, that means that the obsolete phase will *always* do something for a fresh build. .mrg.
