Slackware 14 64 bit.

I'm trying to install MySql workbench. If I use the slackbuilds version, when it runs a get a grey windows and nothing happens. No idea why, nothing gets echoed to the console, it just gives a grey window and sits there.

So I am compiling from source. When I try I get X--tag=CC: command not found followed by several similar lines. A bit of looking around shows that this is a problem related to libtool, and has been happening to many packages over the course of several tools.

I found a website that says to do this:

libtoolize --force --copy
aclocal
autoconf
automake

When I do that, I am then able to compile workbench with no errors.

So - why? Is there a problem with libtool shipped with Slack 14? Why does the above fix the problem?

Edit: not only does it compile and install, but it runs just fine - no grey screen. The slackbuilds version is 5.2.43, the current version is 5.2.44. Not sure if the version differences are significant or not...

No it means there is a problem with libtool that has been shipped with the sources.

Normally you only need to run those commands on source code that you get via git/cvs, usually when they package a release it gets done by the package release person/team.

You should send an email to the maintainer listed in the SlackBuild about the issue so they can confirm the problem and modify the SlackBuild to work around the problem.

EDIT Just read the last line, you've used the next version number than that tested by the maintainer, most likely they botched the release. You can still give the SlackBuild maintainer a heads up in case they want to update it anyway.

The slackbuilds version is tested on clean slackware 14.0 machine and it's working just fine
The 3 commands that you mentioned are all listed in the slackbuilds for slackware 14.0. I'm thinking that you might be using the old slackbuilds designed for slackwaare 13.37?

Have you checked all the dependencies and you have a proper libtool in your systems?
I tested the latest version and it still worked, so nothing is wrong with the script

This is a clean Slack 14 system, but maybe I did grab the 13.37 slackbuilds package? Huh....I'll look into this....

tyvm everyone for your input

So my MySql workbench woes continue. Decided to give it another shot today. Using the slackbuilds script and 5.2.43 from slackbuilds page:

/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: cannot find -lpython2.7.a

Searching for this reveals next to nothing. I have python 2.7.3 that comes with Slackware 14. I'm not sure what it is trying to tell me, let alone how to fix it.

So my MySql workbench woes continue. Decided to give it another shot today. Using the slackbuilds script and 5.2.43 from slackbuilds page I get:

/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: cannot find -lpython2.7.a

Searching for this issue on internet reveals next to nothing. I have python 2.7.3 that comes with Slackware 14. I'm not sure what it is trying to tell me, let alone how to fix it.

Slackware 14 64 bit, fairly clean install.

I don't use the program you're talking about, but perhaps the wxPython package has what you're looking for? It seems to be a dependency for your said program according to slackbuilds.org.

Be sure to install all dependencies before compiling MySql workbench, there are quite a lot of them. All dependencies are specified here:

http://slackbuilds.org/repository/14...-workbench-gpl

I managed to compile MySql workbench before, but I don't remember on which Slackware version, though I had some problems with MultiLib packages, I described it here:

http://www.linuxquestions.org/questi...ackages-850734

I didn't try to do this on Slackware 14 yet, so maybe there is no MultiLib problem anymore.

1st question, did you modify the slackbuild script in any way?

That is not a valid reason for creating a new thread, so please don't.
Your same topic threads have been merged.

So I wiped my system and did a clean install of Slackware 14 64 bit. I attempted to build MySql Workbench with a clean download of the slackbuilds package into a clean install of Slackware 14. As I did so, it would identify missing dependencies as expected, so I installed them. Some of these packages also had missing dependencies, so as I came across those I would install them also. Note that I took the lazy way out and used SBOPKG to install all of these packages (SBOPKG is great, btw :-D ). This is the list of what I installed, and the order in which I installed them:

sigc++
glibmm
cairomm
pangomm
atkmm
gtkmm
lua
ctemplate

paramiko (it will build without this, but will give run-time errors in the console if you don't have this installed)

pexpect (it builds and runs without this, idk what this actually does)

pycrypto (this is the part that will really bite your butt! This one caused me hours of grief. There is nothing anywhere that I could find that says you need it, but you will get the infamous "Cannot start SSH tunnel manager" error without it, and you will get "No module named Crypto" errors in the console. If you don't happen to see this console message, you will have a difficult time resolving this one. "Cannot start SSH tunnel manager" message did not make it obvious to me that I simply needed to install pycrypto, problem solved. A romp through the Internet via Google on the SSH tunnel manager problem turns up a lot of frustrated people with this problem but no solutions. So be sure to install pycrypto!)

Note that if you are missing glibmm, it may complain about giomm-2.4, but this is part of glibmm, so installing glibmm-2.4 also installs giomm-2.4 or otherwise satisfies the dependency.

Once I installed all of these, the build proceeded without error. Idk what the python error was about, but doing a clean install of Slackware got rid of it.

Upon running it, it started up and runs just fine.

Conclusions:

1) Use slackbuilds. Don't try to build this on your own. If you look long enough you will figure out how to make it work but slackbuilds can save you from hours of frustration. Plus the slackbuilds script installs a patch for you, though idk offhand what it does.
2) Don't break your python install (I wish I knew how I did that).
3) Install pycrypto, even though it's not listed anywhere as a dependency

ps: I emailed the package maintainer and asked him to mention the pycrypto on the slackbuilds page as a dependency.

It was pointed out to me that pycrypto is a requirement for paramiko. It is worth mentioning that paramiko will build and install just fine without pycrypto, and if you use SBOPKG to install paramiko for example, or get it from some other source and don't notice this dependency for whatever reason, you may never know that you need pycrypto.

If you don't mind, try using my SlackBuild on my SlackHacks which is updated more often than in SBo
it basically list all your requirements

Your buildscript worked fine, and I notice it uses the current version of workbench. I modified your script to install workbench under /opt, and that worked good also. So far so good, thanks

May I ask for a little help and advice?

I used @willysr's SlackBuild to build mysql-workbench-gpl-5.2.44-x86_64-1wsr and it sorta-kinda works. I wonder if you could share what options you selected when initializing it; I'm pretty sure I had to use the first Ubuntu choice so MySQL Workbench could find /etc/rc.d/rc.mysql (the other choices are looking in /etc/rc[0-3].d and /etc/init.d and I didn't want to fool around with those).

MySQL is started on my systems at boot and, when I start MySQL Workbench, it looks as though mysql@localhost is working but then I can't seem to do anything (such as startup / shutdown).

I've probably missed something and have been through the documentation and done as much step-by-step troubleshooting I can think of.

Maybe a push in the right direction might help and I'd appreciate any hints you may have.

Thanks