I am trying to run rMATS on a Linux (CentOS) cluster. On this system I do not have root access. I installed several of the rMATS dependency packages using the anaconda conda install package manager.
rMATS is unable to access a shared library libblas.so.3 on the system and throws an error rMATSexe: error while loading shared libraries: libblas.so.3: cannot open shared object file: No such file or directory
Although I have located the libblas.so.3 library on my system /Users/paul/anaconda3/pkgs/lapack-3.6.1-1/lib/libblas.so.3 I am unsure how to make it accessible to the rMATS software as a "shared library".
I have tried export LD_LIBRARY_PATH=/Users/ranum/anaconda3/pkgs/lapack-3.6.1-1/lib/libblas.so.3 but this did not work.
Where can i put this libblas.so.3 library so that it can be found by the system?
LD_LIBRARY_PATH is a directory path not a file path. You want to set it like this:
LD_LIBRARY_PATH=/Users/ranum/anaconda3/pkgs/lapack-3.6.1-1/lib
Related
I have some trouble when I want to add a database.
_dataBase = QSqlDatabase::addDatabase("QPSQL");
After calling this method I have an error:
QSqlDatabase: QPSQL driver not loaded
QSqlDatabase: available drivers: QSQLITE QMYSQL QMYSQL3 QODBC QODBC3 QPSQL QPSQL7
I include to PATH variable paths to:
PostgreSQL\9.3\bin
PostgreSQL\9.3\lib
PostgreSQL\9.3\include
Also I copy folder sqldrivers to Debug folder. Also tried to copy dlls drom this folder to Debug. Doesn't work either.
I came here googling because I had the same problem in Windows.
In my case to solve the issue I had to install PostgreSQL for Windows 32 bits since my Qt target was MinGW 32 bits.
Additionally, I had to add the PATH to the PostgreSQL bin and lib directories so Qt could find the right .dlls.
#SET PATH=C:\Program Files (x86)\PostgreSQL\9.6\bin\;C:\Program Files (x86)\PostgreSQL\9.6\lib\;%PATH%
The PATH can be set before launching Qt Creator or using the Qt Creator itself via the Build Environment in the Projects pane.
Add the system variable QT_DEBUG_PLUGINS=1 if you want to get full information of why the QPSQL driver has not been loaded.
Probably you will discover that Qt is not able to find it. Copy and paste the output here to know what exactly happens.
Use depends.exe on qsqlpsql.dll and found that this dll need libpq.dll from PostgreSQL\9.3\libfolder. Add libpq.dll to Debug folder and it works:)
Try pip install PyQt5 event if you already installed it using conda or installer. It helped me.
I got same problem with deploying Qt application (windeployqt didn't help). I had to copy more .dlls (libcrypto-1_1-x64.dll, libiconv-2.dll, libintl-8.dll, libpq.dll, libssl-1_1-x64.dll, libwinpthread-1.dll) from postgreSQL bin path (c:\Program Files\PostgreSQL\12\bin) next to .exe file (according to dependency walker).
I need to run a perl program on Windows. I install Strawberry Perl.
I am not able to install Device::USB module.
Here is the revelant error in log :
-> OK
Successfully installed Inline-0.80
Installing C:\Dwimperl\perl\site\lib\MSWin32-x86-multi-thread\.meta\Inline-0.80\install.json
Installing C:\Dwimperl\perl\site\lib\MSWin32-x86-multi-thread\.meta\Inline-0.80\MYMETA.json
Configuring Device-USB-0.36
Running Makefile.PL
ERROR: Missing required environment variables to compile under Windows.
LIBUSB_LIBDIR should contain the path to the libusb libraries
LIBUSB_INCDIR should contain the path to the libusb include files
-> N/A
-> FAIL Configure failed f
As the error msg states, you should define the two environment variables LIBUSB_LIBDIR and LIBUSB_INCDIR.
Under windows on the command line you can add env vars (temporarily, for the currend cmd process) via SET name=value, e.g.: SET LIBUSB_LIBDIR=C:\your\path\to\the\libs.
Also, libusb has to be installed on your machine - maybe this also will set the lib&include path env vars permanently. (thx for comment! :)
First, you need to install the libusb library on your system.
Device-USB
This module provides a relatively complete Perl wrapper on the libusb
library. Using this module provides an object-oriented interface to any
installed USB devices.
Obviously, the module requires a copy of the libusb library compiled for the
target system. The module also requires a C compiler compatible with the
Perl installation, because it uses the Inline::C module to create the
interface to libusb.
Then, you need to tell Device::USB where to locate the library by setting env var LIBUSB_LIBDIR to the directory that contains the libusb DLL, and by setting env var LIBUSB_INCDIR to the directory that contains the libusb .h files.
You can set those env vars by right-clicking "My Computer", clicking "Properties", clicking "Advanced system settings", clicking "Environment Variables".
I'm trying to get Eclipse to work on my CentOS 7 VM via X11 forwarding. The X11 forwarding seems to be working, as I am able to run and see "xclock". However, whenever I run Eclipse, it crashes with a message similar to this:
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/home/centos/eclipse/configuration/org.eclipse.osgi/375/0/.cp/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
no swt-pi-gtk in java.library.path
/home/centos/.swt/lib/linux/x86_64/libswt-pi-gtk-4527.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
Can't load library: /home/centos/.swt/lib/linux/x86_64/libswt-pi-gtk.so
This issue is all over the web, and a lot of it is solved my soft linking files in /usr/lib/jni/ to ~/.swt/lib/linux/x86/ but, I do not have a a /usr/lib/jni directory. So, I tried to find the libraries that create this folder upon installation and I found these in another Stack Overflow post: libswt-gtk-3-jni, libswt-gtk-3-java
And I can't seem to find anything on CentOS that provides these. I then found this guide on the CentOS client portal for installing Eclipse and it doesn't work for me. It talks about getting access to devtoolset-3 via RedHat Subscription Manager or RHN Classic, both of which are unavailable to me on the machine that I am working with.
At this point I have JDK installed, and Eclipse untarred and attempting to launch and I'm getting this error. Any ideas?
I'm trying to create my first application with Lazarus Pascal and PostgreSQL.
The pg database is on my Ubuntu Linux host. Lazarus is on XP, running through VirtualBox.
When trying to make a connection to the PG database, I get an error that libpq.dll is missing.
What should I do? Pretty new to this platform.
From the docs here http://wiki.lazarus.freepascal.org/postgres
Error: "Can not load PostgreSQL client library "libpq.dll""
The program cannot find your PostgreSQL driver files. Copy all required PostgreSQL .dll/.manifest files either
to your project directory and your executable output directory,
or to a directory in your search path (e.g. c:\windows\system32)
A good example that demonstrates how to include drive DLL files when connecting Lazarus with PostgreSQL under Windows is easyDB.
On Linux/Unix/OSX: make sure the PostgreSQL libraries are in your library search path, e.g.:
On linux add the path to the libpq.so file to the libraries section in your /etc/fpc.cfg file. For example : -Fl/usr/local/pgsql/lib
It may be necessary to create a symbolic link from a specific library version to a general library name:
ln -s /usr/lib/pqsql.so.5 /usr/lib/pqsql.so
. Alternatively, install the postgresql client -dev package using your distribution's package manager
I'm trying to install ADT plug-in in Eclipse 3.5.2 which I got from PowerPC Ubuntu repositories. ADT 16.0.0 or above requires Eclipse 3.6 or higher so I tried 15.0.1 and 9.0.0.
ADT 15.0.1 installation completed 100%, I clicked "Apply Now" and got a bunch of errors. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Problems occurred when invoking code from plug-in: "org.eclipse.ui.intro".
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
ADT 9.0.0 Installation went the same. From Error Log:
Invalid preference page path: com.android.ide.eclipse.preferences.main
Undefined context while filtering dialog/window contexts
Unable to access file "plugins/org.eclipse.emf.ecore_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.environment_1.0.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.ui_1.1.2.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.equinox.concurrent_1.0.1.R35x_v20100209.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.project.facet.core_1.4.1.v200911141735.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.resolver_1.2.0.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.jem.util_2.0.201.v201001252130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.common_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.ui_1.1.102.v200910200227.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.uriresolver_1.1.301.v200805140415.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.edit_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emfworkbench.integration_1.1.301.v200908101600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xerces_2.9.0.v200909240008.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.emf_1.1.301.v200908181930.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/javax.xml_1.3.4.v200902170245.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.change_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.gef_3.5.1.v20090910-2020.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.xml.core_1.1.402.v201001222130.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.frameworks_1.1.300.v200904160730.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.emf.ecore.xmi_2.5.0.v200906151043.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.apache.xml.serializer_2.7.1.v200902170519.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.ui_1.1.402.v200901262305.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.validation_1.2.104.v200911120201.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.sse.core_1.1.402.v201001251516.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.wst.common.core_1.1.201.v200806010600.jar!META-INF/MANIFEST.MF".
Unable to access file "plugins/org.eclipse.draw2d_3.5.2.v20091126-1908.jar!META-INF/MANIFEST.MF".
Invalid preference page path: DDMS
Invalid preference page path: LogCat
Android tab did not appear in Window > Preferences.
Also, both installations took 2 hours.
So, is it possible to install ADT plug-in to Eclipse on PowerPC Ubuntu? Is there any way to install Eclipse 3.6 or 3.7 on my system? My computer is PowerPC G4, Emac (ATI Graphics), Ubuntu 10.04.
First, never install Eclipse from a Linux package manager or repository; always download from www.eclipse.org
The PowerPC linux builds are only available for the Eclipse SDK, not the packages listed on the main Eclipse Downloads page. Here's the link for the latest release of Eclipse (3.7.2/Indigo): http://download.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/index.php
The other thing to make sure of is that you have the Oracle JDK and have configured Eclipse to use it, as described here. Most Linux distros have gcj on the system path and it doesn't play nice with Eclipse.
From there you should be able to install the ADT according to the instructions.
I will throw in here just in case someone runs across my problem
Mint 32 bit, all updates and upgrades applied
sudo apt-get updates
sudo apt-get upgrades)
Eclipsed Indigo Classic - sudo apt-get eclipse
java - sudo apt-get install sun-java6-jdk
Trying to install the Android Eclipse Plugin r18 continually failed with the org.eclipse.wst.sse.core missing error that seems common and random at the same time. Note, this did not happen using 64 bit mint/eclipse etc. go figure. and never on windows.
Here is what I did after trying a lot of different patterns found here on Stack and experimenting using snaps on a virtual box to find the right recipe for me.
Fresh eclipse classic indigo install 3.7.0 (sudo apt-get eclipse) as mentioned above
Start eclipse from the command (sudo eclipse)
Add the repository http://download.eclipse.org/releases/indigo in the Help/Install New Software section
Install Linux tools from the list of options from step 3
After restart try to install the android tools again from the http://dl-ssl.google.com/android/eclipse/ repository ( Success !!! )
After restart CLOSE eclipse (don't let it install the sdk etc)
Start Eclipse normally and let the tools install the SDK for you, or click on the "Window" menu if it doesnt do this immediately on restart to install the base sdk package
Go to the Android SDK manager under the window menu and download any other api's etc you need
This worked for me, many similar things did not, not sure what the differences where etc. and also note I had ZERO issues using 64 bit mint (which is a bit counter intuitive considering the problems the ADB has with 64 bit)
Not THE answer, but certainly an answer for someone having same issues I was (Hopefully)