[Mesa-dev] [Bug 100073] Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=100073

--- Comment #13 from oiaohm at gmail.com ---
(In reply to Ilia Mirkin from comment #10)
> There are lots of words, with lots of mentions of how Debian is awesome, but
> still no usage scenario. Let me help you. A usage scenario looks like:
> 
> """
> Step 1: run X
> Step 2: run Y
> Step 3: run Z
> 
> Note how when you run Z, things don't work or otherwise suck.
> """
> 
> Everything you're talking about is generic hypotheticals with various
> assumptions built in.. I want an actual use-case.

This is a set of assumptions.  Why do I have to 100 percent wait for real world
error.

1) you set your distribution to multiarch.
2) you install programs from different 32 and 64 bit archs as I have now.
This can result in like mesa-utils that contains glxgears being installed for
arm64 and having blender installed for amd64


apt-get install mesa-utils:x32  kicad:i386 blender:amd64  gltron:arm64

Yes you can install from different arch using a single command line.

Now you try to run glgears, kicad, blender and gltron. 

You have 4 versions of mesa on the system.   So the first fix handle the kicad
to blender that works now.   But gltron:arm64 or anything else I have built for
arm64 is going to have trouble.   So I can build binary on x86 PC that is fast
test it on x86 PC without needing extra vm stuff.

Yes building binary normally still involves a container/chroot linking
container/chroot to x11 is a pain and pointless when you are on debian.

The kicad one installed as i386 can be at times that amd64 does not work
correctly when using particular extensions.  gltron would be to test that arm64
it work. 

I don't know what architectures I will have set multi in the future it will be
linked to what boards I am dealing with.

The stuff I have in x32 is mostly internal that you don't have permission to
have access to. 

Ilia Mirkin the reality what you have been calling hypothetical will break my
work-flows.  This is why I opened the bug. 

All I can guess is you are not interested in solving problem for my workflow so
I should not bother opening bugs in future.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170309/2ce14656/attachment.html>