On 2020/03/09 11:34, Janne Johansson wrote: > Den fre 6 mars 2020 kl 12:29 skrev Thomas de Grivel <billi...@gmail.com>: > > > Hello, > > > > I was using base gcc but switching to base clang fixes the warnings on > > -current at least. > > Is base gcc not supported anymore ? > > > > I think you are supposed to use whatever gets used when you call "cc" on > the OpenBSD platform you are on, and if need be, get gcc from ports for an > uptodate version of it.
Some arches (aarch64) only ever had clang. Some arches (i386, armv7) moved to clang and have removed gcc. Some arches (amd64, mips64 [sgi,octeon]) have moved to clang but still have /usr/bin/gcc present, mostly so that people making changes to the base OS have some easy way to check if their changes don't negatively impact gcc 4.2.1 arches. (However this does make it harder to pick up on things in ports which hardcode "gcc" and fail if not present!). For these arches, clang is the supported compiler. Some arches still use gcc. gcc 3 for m88k. gcc 4.2.1 for alpha hppa mips64el powerpc sh sparc64. Of these, mips64el powerpc sparc64 *also* have clang built, but have not switched to it as the main system compiler. For all of these arches, gcc is the supported compiler. > Since arches are moving from gcc into clang (at various speeds), its not > unthinkable for some of them to have both over the transition, but the > "supported" one is always the binary that gets run if you use "cc" for > compiler and nothing else. yep.
