Version: 1.4beta3, 1.3.9, probably earlier too (using KDE KDE 3.5.2) Installed from: Compiled From Sources Compiler: GCC 4.1.0 built from source OS: Linux it's very strange but amaroK 1.4beta3/1.3.9 copiled by GCC 4.1.0 doesn't work properly; building collection doesn't work while the same source on the same os compiled by GCC 4.0.2 works correctly.
Created attachment 15677 [details] 1.4beta3
Seems to be an sqlite problem. Does it work with MySQL/PostgreSQL?
as i mentioned it depends on compiler, sqlite is always 3.1.2; looks like gcc 4.1.0 miscompile amarok.
More likely: Your TagLib was built with a different GCC version. So rebuild it.
unfortunately it didn't help.
OK, so I'm reopening it. I still don't believe that GCC 4.1 miscompiles amaroK, though.
it may be strange and probably You won't believe until You compile it using 4.1.
Test this with MySQL or PostgreSQL, as requested.
Created attachment 15708 [details] 1.4beta3 --enable-postgresql doesn't work too.
Created attachment 15831 [details] current svn still doesn't work.
Alright, we've tested it: 15:21 < leinir> That's balls 15:22 < leinir> i am using GCC 4.1, and it works here
there is one rule - if u want claim that software works good it must work for everybody, if it doesn't work at least for one person it is buggy and its your problem you cannot reproduce that bug on your own and fix it.
Well, since nobody here (as far as I know) wrote gcc, it's not anyone here's job to fix your installation of it. Go off and ask the gcc devs why their product can't compile amaroK for you when it does for other people if you believe someone owes you a fix.
man i can build amarok using gcc 4.1.0, i cannot build collection datebase, is it so hard to uderstand that?
Is it so hard to understand that the assumption from our side is that gcc 4.1.0 has bugs which lead to amarok not working as it was programmed?
gcc bug is unlikely reason for mentioned malfunction; frequently old source code doesn't work with new compiler (for instance older kernels won't compile or won't work correctly with newest gcc), so it would be a good idea to look for a bug in amarok not in gcc.
That is true, but the bug was closed because other people reported it to work. Therefore either the people who reported it working are lying, or you have some local problem with your installation that we can't help you with. Sorry.