Version: 1.2 (using KDE KDE 3.3.1) Installed from: RedHat RPMs Compiler: gcc-3.4.2 OS: Linux In the configure script, the include flags for mysql are found by running mysql_config --include. This switch is only available for mysql > 4.0. There is an equivalent switch which works for all versions: --cflags. There are still a few distributions which ship mysql 3.x.x due to the change in licensing (resolved recently). I'll attach a patch to make it work with an old mysql
Created attachment 9623 [details] patch to configure to detect mysql < 4.0
sorry, we depend on mysql >=4.x. dont remember the exact reason, but there were some problems with temporary tables, iirc. regards, muesli
I have amarok 1.2.1 working fine with mysql 3.23.58, as far as I can tell - I think the only problem with temporary tables is that the GRANT sql command for writing to them doesn't exist <4, so the wiki page for mysql throws an error. You just need to leave out the grant on temporary tables - I'm told anyone can create them in v3, and it seems to work fine. Course, something might break. But I see no sign yet.
Due to last comment, I reopened the bug. Any other known problem with mysql 3.X?
Changing the summary to reflect the new purpose.
Why hasn't this been incorporated? Amarok works fine with MySQL version 3, and it just needs a check for this in configure, with the patch above. I have to make this change in the tarball everytime I compile a new version. Can it be implemented please? To repeat, all that MySQL version 3 needs is to change "mysql_config --include" to "mysql_config --cflags". A quick check in configure will do this.
*** Bug 106576 has been marked as a duplicate of this bug. ***
Confirmed against 1.3.5 too.
Created attachment 13151 [details] allow of of mysql3 too mysql_config --cflags only if it works mysql_config --include only if it works
Is this fixed now?
Not fixed yet, not until someone applies patch (at least the configure.in.in bits) from comment #9. I could do it, provided it's approved by an amarok developer.
I'm guessing a dev hasn't applied it cause none of us are using mysql 3 anymore and don't want to downgrade :-)
Sorry, we won't support 3.x any more. We simply can't maintain it. It's two major versions outdated by now.