BUG: Easytag-devel not work when compiled with GCC 4.0

[berteun@…]

After compiling and installing easytag-devel with GCC 4.0 it does not start-up, mentioning that the accelerator for SortTagMenu cannot be parsed, including a description of the accelerator. This looks like some binary garbage, probably indicating a GCC 4 bug. (Not sure though.)

Anyhow, it does not work with GCC 4.0, but it does work when compiled with GCC 3.3. So I guess that should somehow be the default.

[matt@…]

What are you trying to say? It does or it doesn't works using gcc-4.x (the summary and your comment are somewhat confusing...)

Actually it does works ok with gcc-4.x but there's a bug in id3lib implementation of easytag-devel. It's author is aware of that problem and will address a fix in an upcoming release. Otherwise, aac/flac/vorbis files are correctly handled by easytag-devel.

[berteun@…]

My summary is confusing indeed. If I compile it with GCC-4.0 I get, when I start it from the command-line (note the binary stuff that shouldn't be in the accelerator):

~ berteun$ easytag Starting EasyTAG 1.99.9 (PId: 10875) ... Currently using id3lib version 3.8.3 ...

(easytag:10875): Gtk-WARNING : Unable to parse accelerator '|\x9d#x\u007f\xe8\u0002\xa6\x90\u0001' for action 'SortTagMenu' EasyTAG 1.99.9: Abnormal exit! (PId: 10875). Received signal SIGBUS (10) You have probably found a bug in EasyTAG. Please, send a bug report with a gdb backtrace ('gdb easytag core' then 'bt' and 'l') and informations to reproduce it to <easytag@…> Bus error

First performing: "gcc_select 3.3" and then compiling results in an easytag_devel that runs fine. I tagged around a thousand files today without problems.

[mww@…]

adding a

platform darwin 8 { configure.env-append CC=/usr/bin/gcc-3.3 CPP=/usr/bin/cpp-3.3 CXX=/usr/bin/g++-3.3 }

should do the same, just w/o user interaction. Problem is, that - at least here - the build fails..

[matt@…]

(In reply to comment #2)

My summary is confusing indeed. If I compile it with GCC-4.0 I get, when I start it from the command-line (note the binary stuff that shouldn't be in the accelerator):

~ berteun$ easytag Starting EasyTAG 1.99.9 (PId: 10875) ... Currently using id3lib version 3.8.3 ...

(easytag:10875): Gtk-WARNING : Unable to parse accelerator '|\x9d#x\u007f\xe8\u0002\xa6\x90\u0001' for action 'SortTagMenu' EasyTAG 1.99.9: Abnormal exit! (PId: 10875). Received signal SIGBUS (10) You have probably found a bug in EasyTAG. Please, send a bug report with a gdb backtrace ('gdb easytag core' then 'bt' and 'l') and informations to reproduce it to <easytag@…> Bus error

First performing: "gcc_select 3.3" and then compiling results in an easytag_devel that runs fine. I tagged around a thousand files today without problems.

I repeat to avoid any confusions, easytag-devel version 1.99.9 and 1.99.11 are working fine when compiling with at least Xcode 2.2.x So please upgrade to the lastest Xcode version which is at that time, 2.2.1

For users that don't want to update to Xcode 2.2.1, i can add a variant that uses gcc-3.x Let me know if after upgrading to Xcode 2.2.1, you still have these problems.

[matt@…]

(In reply to comment #3)

adding a

platform darwin 8 { configure.env-append CC=/usr/bin/gcc-3.3 CPP=/usr/bin/cpp-3.3 CXX=/usr/bin/g++-3.3 }

should do the same, just w/o user interaction. Problem is, that - at least here

• the build fails..

Markus, here with Xcode 2.2.1 which has gcc version 4.0.1 (Apple Computer, Inc. build 5250), the easytag-devel 1.99.9 and 1.99.11 is working fine (with Xcode =< 2.2, it doesn't), so i won't provide a "fix" for something that works here. I can at least provide a gcc3 variant for users that don't want to upgrade to Xcode 2.2.1