From: Rutger Helling <rhelling@mykolab.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 33716-done@debbugs.gnu.org
Subject: [bug#33716] [PATCH staging] gnu: mesa: Update to 18.3.1.
Date: Thu, 13 Dec 2018 11:51:34 +0100 [thread overview]
Message-ID: <20181213115134.754b3bc1@mykolab.com> (raw)
In-Reply-To: <87k1kebgr7.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Thanks for pushing! Unfortunately I couldn't get Clang to upgrade to
7.0.0. I've added a llvm@7.0.0 variant to master along with comments
about Mesa and Clang.
On Wed, 12 Dec 2018 22:02:36 +0100
Marius Bakke <mbakke@fastmail.com> wrote:
> Rutger Helling <rhelling@mykolab.com> writes:
>
> > Hey Guix,
> >
> > Here's a Mesa update for the just released 18.3.1 version. Not sure
> > whether or not I'm too late for the staging branch. If I am this can
> > wait until the next staging branch.
>
> Thanks! I've pushed this patch on your behalf and started the
> 'staging' jobset on Hydra, with a small change...
>
> > Two things to note:
> > * While Mesa 18.3.x still builds with LLVM 6 the upcoming 19.0.x
> > series doesn't anymore. For that and performance reasons I decided
> > to add a llvm@7.0.0 package for Mesa. I don't know enough about the
> > LLVM stack to upgrade it entirely, so this is kind of a
> > workaround.
>
> LLVM 7 is a heavy dependency, so I opted to drop it since it is not
> required. Feel free to add the LLVM@7 variant on 'master' in the mean
> time -- it would be good to make it the default in the next staging
> cycle. Did you try upgrading Clang as well?
>
> > * Since Mesa 18.3 works with Python 3 I've replaced the Python 2
> > dependencies with Python 3 ones.
>
> Great, thanks for keeping up with Mesa development!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-12-13 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 10:31 [bug#33716] [PATCH staging] gnu: mesa: Update to 18.3.1 Rutger Helling
2018-12-12 21:02 ` bug#33716: " Marius Bakke
2018-12-13 10:51 ` Rutger Helling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181213115134.754b3bc1@mykolab.com \
--to=rhelling@mykolab.com \
--cc=33716-done@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.