all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Tim Gesthuizen <tim.gesthuizen@yahoo.de>, 32458@debbugs.gnu.org
Cc: Rutger Helling <rhelling@mykolab.com>
Subject: bug#32458: Acknowledgement (SDL SEGFAULTs on foreign distro)
Date: Mon, 22 Oct 2018 22:50:17 +0200	[thread overview]
Message-ID: <8736sx4sfq.fsf@fastmail.com> (raw)
In-Reply-To: <be8e39b8-bb70-42f3-c0cf-34aa91f19930@yahoo.de>

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

Hello Tim!

Tim Gesthuizen <tim.gesthuizen@yahoo.de> writes:

> Hi,
> I did another bisect to find the second cause of failure.
> I used the input rewriting technique but with the fixed libepoxy definition:
>
>>> (use-modules (gnu packages)
>>>              (gnu packages games)
>>>              (gnu packages gl)
>>>              (guix packages)
>>>              (guix profiles))
>>>
>>> (define libepoxy-legacy
>>>   (package
>>>     (inherit libepoxy)
>>>     (version "1.4.0")))
>> 
>> This package is missing a (source ...) field.  So this only pretends to
>> be 1.4.0, but is actually the same as the inherited one.
>> 
>> (Also, should it not be 1.5.0?)
>
> Yes it should be. Something made me think the expression evaluating to
> the origin object in the original libepoxy definition would be
> reevaluated. And it also should be 1.5.0.
>
> I started using the small guile script using guile-sdl2 again, simply
> because I do not need to close the window manually if a commit is good
> and the program starts. Otherwise the bisect would still need human
> input. You can find the scripts that I used attached as a tar archive.
> It has some hardcoded paths though. Execute the check.sh script to check
> the current commit.
> After a really long bisect and tons of package rebuilding git found
> commit faccae1c3769c90694c2b7eee0e4e9ab53049a8f to be guilty. The commit
> updates mesa so it seems quite possible.

Woohoo, congrats!  Really great to finally nail this down.

One thing that might be worth a try before bisecting Mesa itself is
building against LLVM 3.9.1 again.  I don't know the relevance of the
"exactly 3.9.1 for swrast" comment from that commit.

We should also check whether this problem is fixed in 18.2 (available in
the 'staging' branch).

Out of curiosity, which graphics driver are you using?

> I don't have that much time right now but I will try to revert the two
> commits found so far and see whether this gets OpenGL running again on
> the master branch.

Great, thank you!

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

  reply	other threads:[~2018-10-22 20:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 17:25 bug#32458: SDL SEGFAULTs on foreign distro Tim Gesthuizen
     [not found] ` <handler.32458.B.153444037626013.ack@debbugs.gnu.org>
2018-08-20 16:12   ` bug#32458: Acknowledgement (SDL SEGFAULTs on foreign distro) Tim Gesthuizen
2018-08-20 20:35     ` Marius Bakke
2018-08-20 20:59     ` Marius Bakke
2018-08-22 19:18       ` Tim Gesthuizen
2018-10-07 16:22         ` Tim Gesthuizen
2018-10-07 20:06           ` Marius Bakke
2018-10-08 18:07             ` Tim Gesthuizen
2018-10-08 18:28               ` Marius Bakke
2018-10-10 15:35                 ` Tim Gesthuizen
2018-10-15 19:19                   ` Marius Bakke
2018-10-15 19:31                     ` Marius Bakke
2018-10-16 18:20                       ` Tim Gesthuizen
2018-10-17 15:13                         ` Marius Bakke
2018-10-22 17:23                           ` Tim Gesthuizen
2018-10-22 20:50                             ` Marius Bakke [this message]
2018-10-29 18:43                               ` Tim Gesthuizen
2018-11-14 19:49                                 ` Marius Bakke
     [not found] ` <87zhs0hbre.fsf@fastmail.com>
2019-01-18 20:14   ` Tim Gesthuizen
2019-01-23 17:32   ` Tim Gesthuizen

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=8736sx4sfq.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=32458@debbugs.gnu.org \
    --cc=rhelling@mykolab.com \
    --cc=tim.gesthuizen@yahoo.de \
    /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.