Edgar Fuß <ef%math.uni-bonn.de@localhost> writes: >> C) Have something like the within-family compiler choice, but extend it >> to across families, so that even if configured to build with clang a >> package marked as not working with clang would get built with gcc. > I guess the tricky part is libtool. You either need a matching libtool > for each compiler (family) and install the correct one before building > or you need to add --tag arguments to libtool invocations calling a > compiler. Hmm. It seems that pkgsrc doesn't enforce this at all. I've been switching to/from clang and not noticing any libtools issues. But I'm not recommending my option C - I think if the user sets a compiler family it should be honored.
Attachment:
pgpQKvXuLIMad.pgp
Description: PGP signature