Libtool problems installing mysql workbench.
 

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.

MySql Workbench Slackbuilds - cannot find -lpython2.7.1
 

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?

Please don't
 

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

Have you installed all the deps? Missing some of them would make your workbench unable to connect to your mysql

Yup, all of 'em in the sequence specified at SlackBuilds.org (all built from SlackBuilds and installed one-by-one as listed in the "this requires xxx."

Too, my user account (and the root MySQL user) has Attila the Hun permissions on the data bases to both localhost and the server.

[edit]
Forgot to mention, in /etc/rc.d/rc.mysqld:
As suggested by some instruction in the documentation. It's also commented out in /etc/mysqld/my.cnf.

Shouldn't have anything to do with anything but, also in /etc/mysql/my.cnf,
so commits will happen on loads at the default 1 second intervals (loads things a lot faster that way).
[/edit]

Well, I'm not the expert here ... so ignoring my personal prejudices against ubuntu ( :) ) ...

Start workbench from a console (mysql-workbench) and see what it outputs to the console. Workbench expects to find mysql libraries in the "usual" place, and if it doesn't find them, it won't start, and it won't tell you why it won't start except for some message to the console. These messages can be rather cryptic, but they are a good place to start.

If you are using a SlackBuild script on Ubuntu, all bets are off - one of the ./configure options are --build=$ARCH-slackware-linux and I don't know what that would do under Ubuntu. The other settings AFAICT should work, maybe someone here that knows more about Slack versus Ubuntu can comment.

On Ubuntu, there is no /etc/rc.d directory, you probably want to use either /etc/rc[0-3].d or /etc/init.d.

Other then that, I'm not sure ... I like MySql-Workbench, but it is a serious pain in the freakin' arse to get working, it almost isn't worth the trouble. There are a lot of people out there having the tunnel manager error, caused by not having pycrypto installed, and there is nothing obvious that says that is where the problem is. I wasted too many hours trying to get it to work, only to get weird things like grey screen on startup, tunnel manager problems, weird python related build problems, etc. before I finally got it working.

Having said all that, what exactly do you mean "sorta-kinda" works? Exactly what doesn't work, and what to you do to get it to manifest?

I might comment that some of the dependencies have other dependencies, but missing certain dependencies (like pycrypto) will NOT stop it from building and installing, nor will there be any indication given that a dependency is missing until you run it. Then, missing dependencies can manifest by run-time errors.

Yeah, know that (and you walk the SlackBuilds tree taking note of every single "this is required" dependency for every single step along the way -- did that (actually, always do that).

By the way, I do not use Ubuntu (anything); notice the "Distribution?" Somehow or other that particular drop-down figures out where to find the MySQL stuff it needs to. I dunno, but I think there's a symbolic link lurking around somewhere other.

Anyway, onward and... downward? Nah, it'll work someday.

Well, that was an interesting exercise:
Of course ifconfig isn't found: it's in /sbin and ordinary folk aren't supposed to mess with it! (And, no, I don't think I want to symbolic link it to /bin or /usr/bin.)

Hmm. The bind is getting cheesy.

here's what i got when running MySQL Workbench from console and everything works well :

That's what I got running as root (which, of course, can find ifconfig). I'm going to keep digging and see what I come up, thanks.

I spent some time yesterday reclaiming my laptop from the Evil Empire. Had to reinstall Win7 on it early this year so I could run Turbotax (which would not run in Win7 in Virtualbox); gotta do them taxes. This year's Turbotax arrived a few days ago -- it does run in Win7 in VirtualBox! Oh, happy day, no more useless Windows boat anchor sitting there needing critical updates every blessed week.

Slackware 14 64-bit went on to a fully-wiped-clean disk, set it up, copied stuff from my main server, installed a couple of utilities and viola, pita the laptop lives!

I think I heard a sigh of relief.

So back to MySQL Workbench and see if I can get that going.

Thanks for you help and advice.

For those of you interested and/or following this thread: Oracle has released a new version of MySqlWorkBench that ... drum roll please ... supports data migration (!!). Workbench 5.2.45 is now available!

Unfortunately, it throws a bunch of compile errors related to lua. Upgrading to the current version of lua did not help. At this point I'm not sure if there is some weird dependency problem, or if their code is just buggy. So, alas, I'm stuck on the previous version for now, which compiles just fine.

grtpp_module_lua.cpp:75:16: error: 'LUA_GCSTOP' was not declared in this scope
grtpp_module_lua.cpp:75:29: error: 'lua_gc' was not declared in this scope
grtpp_module_lua.cpp:76:21: error: 'luaL_openlibs' was not declared in this scope
grtpp_module_lua.cpp:77:16: error: 'LUA_GCRESTART' was not declared in this scope
grtpp_module_lua.cpp: In function 'int call_traceback(lua_State*)':
grtpp_module_lua.cpp:253:46: error: 'lua_getfield' was not declared in this scope
grtpp_module_lua.cpp:258:25: error: 'lua_pushinteger' was not declared in this scope
make[4]: *** [grtpp_module_lua.lo] Error 1

Anyone have any suggestions as to the cause and resolution for these errors?

Moderate Please delete this post if you can, it is a duplicate post - got error when trying to post previous post, so I did it again and then they both showed up. Sorry!

Use Lua 5.1.x and it should work
I have built 5.2.45 and it's working fine on my machine :)

Willy, did you succed on the multilib system? I'm stuck at libtool searching for liblzma in /usr/lib instead of /usr/lib64.

I'm using 32 bit machine, sorry
I have no multilib machine here

I have Lua 5.1.5, same errors. I'm using 64 bit slack, I think I'll slap the 32 bit version into a VM and see it builds there - maybe it is a multilib related issue?

It could be, but i'm not really sure since i don't have a multilib machine to proof that