Allegro game development library developers are preparing the next stable release 4.2.0. It would be a good idea to test the remaining prereleases to ensure that they work properly on all platforms. This is a slightly edited ebuild from version 4.1.18, I have tried it on amd64 and x86 and it seems to work for me. It fixes at least one minor problem with alpha transparency on amd64 which exists in current allegro 4.1.14 when used to build the latest development version of ufo2000. Reproducible: Always Steps to Reproduce:
Created attachment 56933 [details] allegro-4.2.0_beta2.ebuild
beta2 sets CFLAGS from configure. That's evil. Probably configure.in needs to be patched and the fix sent upstream.
Beta 3 was released, ebuild can be renamed to 'allegro-4.2.0_beta3.ebuild' By the way, I have added '--disable-asm' configure option because of several reasons: 1. It did not build (beta2) without this option on amd64 2. It is impossible to valgrind allegro-based programs compiled without this configure option 3. Looks like assembly optimized code (optimized for i386 long time ago?) does not work so good on modern cpu, and C code compiled by modern compilers with proper optimizations settings even beats it (see http://www.allegro.cc/forums/view_thread.php?_id=474843) Maybe it is worth to add local USE flag for selecting whether we want assembly optimized code or not?
And I have sent a message to allegro developers mailing list with a link to this bugzilla page and information about CFLAGS issue.
I would just like to add a question on this bit (also said on the AD mailinglist): > 1. It did not build (beta2) without this option on amd64 Allegro's configure script should automatically configure for AMD64 if it runs on it. I'm running Gentoo on an AMD64 system myself and it works for me. That said, I'm not an autoconf expert and it's possible I goofed up the detection system somehow. > Maybe it is worth to add local USE flag for selecting whether we want assembly > optimized code or not? That sounds like a better idea to me than to always disable it, at least for the time being. Evert
Created attachment 59796 [details] allegro-4.2.0_beta3.ebuild Just checked it, it's weird, '--disable-asm' option is really not needed on amd64. I really did have a compilation failure, but that probably was with one of the early versions, nevermind. And as assembly optimized and nonoptimized builds have different ABI (explained in allegro-dev mailing list, thanks), seems that there is no point in adding this option anyway. It is good that allegro develpers are using gentoo linux too, now I can just step aside and let you cooperate with gentoo devs in order to provide good allegro packages for gentoo in the future :-) The same ebuild with --disable-asm option removed is attached for lazy people like myself. It is not intended for inclusion in the portage tree, but it might be useful for some people looking for fresh ebuilds in the bugzilla :-)
> It is good that allegro develpers are using gentoo linux too, now I can just > step aside and let you cooperate with gentoo devs in order to provide good > allegro packages for gentoo in the future :-) Actually, Allegro developers are quite busy as it is and don't really have much time to make good gentoo packages, much as they'd like to. So if you can help out by keeping an eye on this that would be greatly appreciated. :) Evert
reopen when 4.2 is out. Thanks.
clean up bug list after bugzilla update
