Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I failed getting flash player for 64 Bit Linux . Can neone tell me where can I get 64 Bit Flash Player . I searched it in Google and saw people saying there is no 64 Flash Player Until now ,,, is it so . If it is so ,, is there any way I use the 32 Bit Flash Player ??.
Thanx in Anticipation.
You have to do a manual install. Find the "flashplayer.xpt" and "libflashplayer.so" files from the "install_flash_player_7_linux" directory where you extracted the tarball. Copy these 2 files into your browser's /plugins/ directory and you'll be good to go!
this is just a fact of the install script only works on 32bit platforms, the plugin works fine.
I am having the same troubles. I have untarred the gplash-4.0.13.tar.bz2
than I try to ./config I get a whole lot of "no help" from it. the what I get is...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
can you make any sense out of this. I am hoping you have been through the same here. or hopefully someone has.
1) Download the Plugin and the Viewer from http://www.gibix.net/dokuwiki/en:raz...spluginwrapper
2) Install Alien, if not already installed.
3) Convert the downloaded rpm's to deb's (sudo alien -d *.deb)
4) Install the newly created debs (Install in this order: sudo dpkg -i nspluginwrapper-i386_0.9.90-2_amd64.deb, sudo dpkg -i nspluginwrapper_0.9.90-2_amd64.deb) -- If I got the order wrong, you'll know because it won't install.
5) Download the plugin you want to install, and extract the .so file. For example, to install flash, grab the tar.gz file from Macromedia's website, and extract libflashplayer.so.
6) Move the plugin (example, libflashplayer.so) to /usr/lib/mozilla/plugins. This is where nspluginwrapper stores the main plugin, so it's probably a nice folder to keep them.
7) Now we need nsplugwrapper to make the new plugin, so call: /usr/lib/nspluginwrapper/x86_64/npconfig -i /usr/lib/mozilla/plugins/libflashplayer.so (if wanting the flash plugin, of course). Depending on whether or not you run that command with sudo, it will either end up in /usr/lib/mozilla/plugins, or ~/.mozilla/plugins. If you ran it as sudo, you'll need to link it to either your profile's plugins or the main plugins (/usr/lib/mozilla-firefox/plugins). Or copy, doesn't matter. The old plugin must not move, as it's path seems to become hard coded in the new plugin created (which has "npwrapper-" prepended to the old name).