I need to install Tcldot library and
I installed
graphviz
tcl-dev
in ubuntu 20.
but there is not tcldot library..
How can I install it in ubuntu?
I've never used tcldot, but this documentation (https://graphviz.org/pdf/tcldot.3tcl.pdf) says:
#!/usr/local/bin/tclsh
package require Tcldot
Related
According to the documentation, when I install the CUDA 7.5 Toolkit on my Mac (OSX 10.11) I should get the nvrtc files with it. I do not. Where do I pick up the nvrtc header files and libraries? Were they supposed to be in the bundle and left out? Were the deprecated or replaced with something else?
So the trick is:
1) Install XCode (from the App Store) FIRST. After the App Store is done installing it, you have to go into your Application menu and actually run it and accept the license.
2) Use the Homebrew version:
$ brew install Caskroom/cask/cuda
3) Lastly, you can update your PATH and LD_LIBRARY_PATH to find the new code:
$ export PATH=/usr/local/cuda/bin:${PATH}
$ export LD_LIBRARY_PATH=/usr/local/cuda/lib:${LD_LIBRARY_PATH}
For some reason, simply downloading the package from NVidia and installing it does not get you a complete installation.
I have tried installing MYSQL gem on fedora using rubinius but it keeps throwing failed to build gem's native extension and that I should install development tools first.
I am on Fedora 22 and I already have mysql-devel library installed. What should I do?
You probably don’t have gcc et al installed yet. The “development tools” being referred to is likely the yum/dnf group. You can install a slew of build tools by following these instructions. But now that we’re on Fedora 22, use dnf instead of yum.
So, in short:
sudo dnf groupinstall 'Development Tools' 'Development Libraries'
Unable to install pyaudio from the package python3-pyaudio_0.2.8-1_amd64.deb
with the following error message:
Dependency is not satisfiable: python3(<3.3)
I am on Ubuntu 14.04 where the default Python3 version is Python 3.4.
Is there a way to get this to work with Python 3.4 version or my only bet is to downgrade to Python 3.3 ?
If i did understand your question well, i recommend you check the following repository in github.
pyAudioAnalysis Installation
Use pip install pipwin on CMD after that use pipwin install pyaudio on ur program
I have installed MySQL 5.5.32 via apt-get install into Ubuntu 13.04.I want to use it in a Java project.For this i must have MySql connector jar.I can not find it.I tried locate *mysql*.jar but it did not find anything.I looked into /etc/mysql but there is no jar in it.I don't want to download it from internet because i believe that it somehow exists in an MySQL folder.Does anybody have any idea where the connector jar went into Ubuntu 13.04?
If you're using a version of Ubuntu prior to 19.04, you'll need to install libmysql-java, the MySQL JDBC driver, because the connector is not in the Ubuntu-packaged MySQL package that you've already installed. Versions after that do not publish that package.
Once it's installed, you'll have the file /usr/share/java/mysql.jar, which is an indirect symlink to the actual jar file.
Alternatively, install the mysql-apt-config package, update, and you'll be able to install all currently supported MySQL software with apt.
First, apt-get install libmysql-java
Then mysql.jar is located in /usr/share/java/mysql.jar.
Third, in Eclipse, do this as: Project -> Properties -> Java Build Path -> Libraries -> Add External JARs -> select /usr/share/java/mysql.jar
In ubuntu 19.10 the following works:
apt-get install libmariadb-java
Does OSX need an install of libmysqlclient15-dev? I'm trying to compile a gem that is failing and a lot of sources says to install "libmysqlclient15-dev" but I only see this for Linux, not OSX. Am I missing something here?
brew install mysql
fixed this for me
I know this is old, but google got me here. So let's say the solution in 2018 for python3 on OSX.
brew install mysql-client
echo 'export PATH="/usr/local/opt/mysql-client/bin:$PATH"' >> ~/.bash_profile
source ~/.bash_profile
pip install mysqlclient
I just had the same problem and only got a partial working solution.
Here are the steps I made to make it work:
brew install mysql-client
brew install mysql-connector-c
IF YOU HAVE ZSH:
echo 'export PATH="/usr/local/opt/mysql-client/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc
ELSE:
echo 'export PATH="/usr/local/opt/mysql-client/bin:$PATH"' >> ~/.bash_profile
source ~/.bash_profile
Now for the installation itself:
LDFLAGS=-L< your openssl lib folder location > pip install mysqlclient==< version >
for example:
LDFLAGS=-L/usr/local/opt/openssl/lib pip install mysqlclient==1.3.12
If you are using the mysql dmg file to install mysql you will need to edit your ~/.bash_profile and include this:
export DYLD_LIBRARY_PATH=/usr/local/mysql/lib:$DYLD_LIBRARY_PATH
brew install mysql
then
arch -x86_64 gem install mysql2 -v 0.5.3 -- --srcdir=/usr/local/mysql/include
Afterwards I was able to run bundle install.
Copied from Bragadeesh Jegannathan's blog post
Yes you will need to install this. For example if you are trying to install the mysql gem you will need the headers for the mysql library. This is because some gems need to compile native extensions, so they need the header files for any 3rd party libraries that the extensions uses.
On Mac OS X I recommend using MacPorts to manage the installation of these libraries/headers.
Those instructions are for Debian type Linuxes. The closest thing to Debian for OS X is Fink. After getting that installed and set up, you can say fink install mysql-unified-dev to get essentially the same thing as asking for libmysqlclient15-dev on a Debian or Ubuntu type system.
Beware that Fink installs its packages in /sw, and not all build scripts know to look there for libraries and headers. You might have to give custom build options to get it to figure this out.
A path that may be more successful is to simply download the MySQL 5.0 package for Mac OS X. That should include the same development files as libmysqlclient15-dev, and as a bonus will put them in places more likely to be found by your gem.
(Why 5.0, by the way? Because that's what corresponds to ABI version 15, which your package apparently requires. Maybe it will in fact work with 5.1, or 5.4, or 6.0, but that would be a risk you'd have to decide to take on your own.)