all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: branch core-updates updated (49c2a46 -> 568004c)
Date: Wed, 15 Mar 2017 01:00:24 -0400	[thread overview]
Message-ID: <20170315050024.GA27201@jasmine> (raw)
In-Reply-To: <20170314184900.3080.43694@vcs0.savannah.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]

On Tue, Mar 14, 2017 at 02:49:00PM -0400, Efraim Flashner wrote:
> efraim pushed a change to branch core-updates
> in repository guix.
> 
>       from  49c2a46   gnu: python@2.7: Update to 2.7.13
>        new  c5e9101   gnu: mesa: Use llvm backend for Intel hardware only.
>        new  2a8b89c   gnu: mesa: Customize build flags based on architecture.
>        new  044006f   gnu: mesa: Enable gallium tests.
>        new  568004c   gnu: nss: Build for aarch64-linux with 64-bit support.

Some in this push broke mesa for me on x86_64.

It fails in the configure phase like this:

checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for PTHREADSTUBS... yes
checking for LIBDRM... yes
checking for SHA1Init... no
checking for CC_SHA1_Init... no
checking for wincrypt.h... no
checking for SHA1Init in -lmd... no
checking for LIBSHA1... no
checking for nettle_sha1_init in -lnettle... no
checking for gcry_md_open in -lgcrypt... no
checking for SHA1_Init in -lcrypto... no
checking for OPENSSL... no
checking for SHA1 implementation...
checking for GLPROTO... yes
checking for DRI2PROTO... yes
checking for DRI3PROTO... yes
checking for PRESENTPROTO... yes 
checking for XCB_DRI3... yes
checking for XF86VIDMODE... yes
checking for DRIGL... yes
checking for EXPAT... yes
configure: error: classic DRI driver '915' does not exist
phase `configure' failed after 12.6 seconds

Please tell me what other information or debugging I can provide.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2017-03-15  5:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170314184900.3080.43694@vcs0.savannah.gnu.org>
2017-03-15  5:00 ` Leo Famulari [this message]
2017-03-16 21:21   ` branch core-updates updated (49c2a46 -> 568004c) Efraim Flashner

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=20170315050024.GA27201@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    /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.