Arch Linux

lithium

Member

Registered: 2007-09-18

Posts: 76

Acroread x64

I installed bin32-acroread today as well all the necessary lib32* libraries and the mozilla plugin using nspluginwrapper. It works fine both standalone and in firefox. However, if I start firefox from a terminal, I notice this output:

LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/nppdf.so [/usr/lib/mozilla/plugins/nppdf.so: wrong ELF class: ELFCLASS32]

Did I install something incorrectly? Indeed, that file is a 32-bit library but I thought that all the lib32's were kept separately?

Thanks.

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Acroread x64

lib32 libraries aren't exactly separate. What happens is that Linux will try all libraries of the same name until one of them works or all of them fail. I don't know that answer to your problem though. My gut tells me that nspluginwrapper isn't working properly.

lithium

Member

Registered: 2007-09-18

Posts: 76

Re: Acroread x64

Well, keep in mind that everything works fine. I can use acroread from firefox just fine. Only I think that file shouldn't be where it is...

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Acroread x64

Well, keep in mind that everything works fine. I can use acroread from firefox just fine. Only I think that file shouldn't be where it is...

Whoops. I understand now and I fully agree. It should be in /opt/lib32/.

lithium

Member

Registered: 2007-09-18

Posts: 76

Re: Acroread x64

Bingo. Now, could I have done something to mess this up (I simply followed the instructions from pacman's output) or is this something wrong with the package in AUR?

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Acroread x64

Bingo. Now, could I have done something to mess this up (I simply followed the instructions from pacman's output) or is this something wrong with the package in AUR?

It's how the package was designed. And now that I think about it, it's probably the cleanest choice. Either the plug-in had to be put into the correct directory (this case) or symlinked from somewhere else. Firefox and others are looking in specific places for it's plug-ins and not elsewhere in the PATH.