FS#7487 - audacious-player plalylist contain ?xspf
Attached to Project:
Arch Linux
Opened by Peter Avramucz (muczyjoe) - Thursday, 21 June 2007, 11:43 GMT
Last edited by Travis Willard (Cerebral) - Tuesday, 03 July 2007, 13:01 GMT
Opened by Peter Avramucz (muczyjoe) - Thursday, 21 June 2007, 11:43 GMT
Last edited by Travis Willard (Cerebral) - Tuesday, 03 July 2007, 13:01 GMT
|
Details
If i start, and add some files, it's ok, but after restart
tha items contain ?xspf at the end. An audacious dev said, i
should compile it by and it worked. He said, it's because
the cflags, but i've compiled with the PKGBUILD, and it
works.
So the solution might be so simple, as repackaging the audacious-player. |
This task depends upon
Closed by Travis Willard (Cerebral)
Tuesday, 03 July 2007, 13:01 GMT
Reason for closing: Fixed
Additional comments about closing: AHA! I've finally figured out what the problem is, for reals. I'm uploading fresh -player and -plugins packages that hopefully should put an end to this confusing and annoying bug.
Basically, the player and plugins pkgs must always be built with the same compile-time flags (and probably the same minor version of GCC too) - if they're not, then oddness happens with the playlist. What happened in this case is that we were using a version of the player released a while ago. Then, GCC was updated and -mtune=generic was made default. Then, without releasing a new player, audacious released a new version of the plugins. So, the plugins were built with the new GCC and new flags, while the player was still built with the old flags. That's why removing -mtune=generic from the plugins seemed to help.
Anyway, I've rebuilt both player and plugins with proper cflags. Versions are audacious-plugins 1.3.5-5, audacious-player 1.3.2-4.
Tuesday, 03 July 2007, 13:01 GMT
Reason for closing: Fixed
Additional comments about closing: AHA! I've finally figured out what the problem is, for reals. I'm uploading fresh -player and -plugins packages that hopefully should put an end to this confusing and annoying bug.
Basically, the player and plugins pkgs must always be built with the same compile-time flags (and probably the same minor version of GCC too) - if they're not, then oddness happens with the playlist. What happened in this case is that we were using a version of the player released a while ago. Then, GCC was updated and -mtune=generic was made default. Then, without releasing a new player, audacious released a new version of the plugins. So, the plugins were built with the new GCC and new flags, while the player was still built with the old flags. That's why removing -mtune=generic from the plugins seemed to help.
Anyway, I've rebuilt both player and plugins with proper cflags. Versions are audacious-plugins 1.3.5-5, audacious-player 1.3.2-4.
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/6a9bfc9c5ade7d0c/99ec4e414a3fd5fa
Happens on debian too.
I'm stumped - no matter how I rebuild it, it keeps coming up..
Ooo! Nevermind - I just tried after removing ALL cflags and it seems to be working for me now. I'll test it for the next couple of days to make sure it's not another red herring, then I'll re-upload.
makepkg
pacman -U audacious-plugins-1.3.5-3-i686.pkg.tar.gz
This works for me. However the package from arch mirrors, doesn't... :-/
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe"
local/gcc 4.2.0-2
Everything default.