On Sun, January 25, 2009 19:21, Tom wrote:
> Hi List!
>
> After following the thread about the icedtea build on amd64 I found
> myself wondering if it would make sense for me to change to
> a non-multilib setup.
>
> So how is the status of that specific profile, how stable, and more
> importantly how feature rich can it be?
>
> Java seems to be getting close to a non issue, but what about flash for
> instance? I know there's now a native 64version of adobe's plugin (I'm
> using it right now) but I don't know about its dependencies.
>
> Other things spring to mind, certain codec-packs, multimedia in
> general.
> And of course wine, virtualization etc.
>
> So can anybody provide some insight into how things are generally
> going in non-multilib-land?!
The only difference is that no 32 bits code is pushed into your system.
Which in turn means you won't be able to run nor compile 32 bits stuff at
all. Wine will plainly not work.
mplayer will play about everything. I haven't used win32codecs for years.
However I stay away from closed formats, but the few realplayer and window
media files that I needed to play could be opened without problems by
mplayer without the help of external codecs.
The flash alpha plugin for 64 bits works well.
You should really check what 32 bits stuff you use. If you need wine you
need multilib. Really, there's no advantage into going no-multilib. You
only lose versatility and reduce the range of software that you can use.
You could get a rough idea about the 32 bits you have installed by using
file like this:
file {,/usr}/bin/*|grep 32
--
Jesús Guerrero
