Mesa compiler specification

[Kevin Oberman]

Thanks! A much better solution.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Mon, Jan 21, 2019 at 3:18 PM Jan Beich <jbeich at freebsd.org> wrote:

> Kevin Oberman <rkoberman at gmail.com> writes:
>
> > On Mon, Jan 21, 2019 at 12:33 PM Tobias Kortkamp <tobik at freebsd.org>
> wrote:
> >
> >> On Mon, Jan 21, 2019, at 21:20, Kevin Oberman wrote:
> >> > I am happy to see mesa-18.3.2 has made it to ports. Thanks, Jan.
> >> >
> >> > I do have one question/request... Can the mesa ports be updated to
> allow
> >> > compilation with either llvm60 or llvm70? I have been compiling with
> >> llvm70
> >> > fora few weeks with no problems. It both compiles and runs fine. It
> was
> >> the
> >> > only remaining port on my system requiring llvm60 and I suspect that
> I am
> >> > not alone in this.
> >>
> >> You can do this by simply setting MESA_LLVM_VER=70 in make.conf.
> >>
> >
> > Thanks but it is not really the proper way to solve the problem. This is
> > something that should "just work" and not require figuring out what needs
> > to be added to make.conf. At least a note in a pkg-message would help.
>
> DEFAULT_VERSIONS+=llvm=70 (already default) syntax would apply to mesa-dri
> after v2 in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230789
> lands.
>
> Once devel/llvm80 appears it'd be time to prepare for LLVM_DEFAULT bump,
> patching consumers and asking port maintainers for feedback until actual
> release happens. Based on results consumers not ready would be temporarily
> kicked out from LLVM_DEFAULT train, or maybe someone provides a better
> idea.
> llvm80 stabilization is partially dependent on how much help
> clang800-import
> effort receives.
>
> Note, LLVM_DEFAULT is defined in Mk/bsd.default-versions.mk
>