Re: Running 32bit OpenGL program with amd64
Alberto Luaces <aluaces@udc.es> writes:
>> I've been using a 32bit application which stopped working when the
>> NVIDIA drivers were updated last time.
>
> Correct. The same happened to me.
Yeah and it's impossible to get it working again :((((
>> The reasons why it stopped working are unknown,
>
> Not quite. The *nvidia-glx-ia32 packages where emptied/obsoleted. See
> for example http://packages.debian.org/wheezy/libgl1-nvidia-glx-ia32 .
That doesn't mean that's the reason why it stopped working.
>> and apparently I would have to switch to brokenarch before having a
>> chance to get it working again. There's no way to tell which i386
>> packages would need to be installed, and since it doesn't work anyway,
>> there's no point in trying to find out.
>>
>
> Yes it is. If you have installed the typical 64-bit .deb package that
> is actually a 32-bit binary with the ia32-libs package dependency, you
> can just quickly install the real 32-bit .deb. Then apt-get or aptitude
> will pull the :i386 dependencies for that :i386 package. This can be
> done for example, for skype or the Humble Bundle games.
There is no Debian package for this 32bit application.
> If your package is not installed as a .deb file, you would be on your
> own as well recollecting the appropriate libraries in 32 bit.
> Nevertheless, you can track which ones are required with the command
> 'ldd' and the Debian packages page
> (http://www.debian.org/distrib/packages) This is not a specific
> multiarch advice, anyway.
What would that help me without knowing why the application doesn't work
anymore? It seems reasonable to assume that it has something to do with
the NVIDIA drivers --- if I could, I'd just go back to the previous
version.
>>> However, I had to use the nvidia drivers from experimental in order to
>>> have working 32-bit OpenGL libraries.
>>
>> I have tried that at least three times now. It doesn't work, causes
>> dependency problems and is difficult to fix once it's messed up.
>
> The only tricky part at the time of this writing is to select the right
> nvidia drivers if you are using them. But as I said, now there is
> available at the experimental repository a new version that fixes the
> multiarch problem for OpenGL. Just take care of installing the exact
> same version of drivers and libraries among the multiple solutions
> offered to you by the conflict resolution tool in apt-get/aptitude.
The package management doesn't know anything about unstable or
experimental anymore because that lead to problems, so it doesn't
present any solutions. If I download and install packages manually, it
causes dependency problems, and I might have to do so indefinitely once
I started doing it.
>> 32bit support is totally broken, brokenarch totally sucks, and I'm
>> majorly pissed and don't trust Debian anymore. It seems unlikely that
>> the problem will be fixed before the next release is out, and I find it
>> amazing that they will leave the users of stable with this problem and
>> have them find out that their 32bit software doesn't work anymore after
>> the upgrade. If it wasn't such a pita to do it, I'd already have
>> switched to something else.
>
> I think the opposite. I see all mature enough, and I expect that tiny
> details like the one I described will be ironed out before the release.
It's not a tiny detail when an important feature suddenly disappears
without any warning and without any way to get it back. It's also not a
tiny detail when you're suddenly supposed to give up amd64 and switch to
brokenarch. It would be easier to re-install and use i386 instead of
amd64, but I don't like the idea of turning my system back about a
decade because Debian is totally messed up now --- and it's about as
much work as switching.
> The concept is simple: activate multiarch → install 32-bit software by
> means of 32-bit .debs. The wine package for wheezy in amd64 has a nice
> documentation on how to activate multiarch.
I don't have any use for wine and the two or three times I tried it over
the years, wine didn't work anyway. Last time it couldn't even run
notepad.
Anyway, the concept sucks and is anything but simple. So what do I need
to install --- packages from testing only, of course --- to get things
working again? Why isn't that documented somewhere?
--
Debian testing iad96 brokenarch
Reply to: