Summary: | x11-wm/afterstep-2.2.9 stable request (x11-wm/afterstep-2.2.4 does not provide /usr/bin/afterstep binary on IA64) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom Noonan <tom> |
Component: | Current packages | Assignee: | Gentoo Afterstep Maintainers (OBSOLETE) <afterstep+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | STABLEREQ |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | IA64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 308649 | ||
Bug Blocks: | |||
Attachments: |
Biuld log of Afterstep-2.2.4 on IA64 2/20/10
Afterstep-2.2.9 failure on 64bit host. |
Description
Tom Noonan
2010-02-20 20:00:40 UTC
Attach build log. Created attachment 220541 [details]
Biuld log of Afterstep-2.2.4 on IA64 2/20/10
Upon closer inspection I see multiple compile errors. So the build fails, but the emerge doesn't.
The fault seems to be tied into jpeg support. It builds properly without the jpeg use flag. It may be related to new jpeg-7/8 (jpeg-8 is stable now, so that's probably what you have) Does afterstep-2.2.9 fail the same way? I plan to ask stable for it soon I am using jpeg-7, current stable on ia64. I upgraded to 2.2.9 and the ebuild builds correctly with the following use flags: gif jpeg png -alsa -dbus -debug -gtk (-mmx_ -nls -svg -tiff -xinerama It seems to work ok, marking as closed. Thanks for testing it, as jpeg-8 is stable on most arches now, it's time to stable a new afterstep version (2.2.4 is 3 years old and current ebuild also has a few fixes on stripped files and bundled libungif) Arches, please test and mark stable =x11-wm/afterstep-2.2.9, thanks! One thing to note is the 2.2.9 ebuild fails "due to poor programming practices" with the gtk use flag enabled on ia64. I noticed that while testing but didn't post it as it is a separate issue from my original bug. I don't have a build log handy, I'll have to create one when I get to work. The ebuild complains but does not fail on my x86 box. Created attachment 223727 [details]
Afterstep-2.2.9 failure on 64bit host.
Oh, I manually toggled the gtk use flag on at the command line for that build. (Since I knew it wouldn't work.) I forgot to note that when I put the emerge --info and emerge -vqp afterstep outputs at the beginning. That is why it shows the gtk use flag being disabled and then fails to build. (In reply to comment #7) > The ebuild complains but does not fail on my x86 box. I can confirm this! It complains but compiles fine and works. stable x86, thanks Andreas ppc stable I get the QA Notice: Package has poor programming practices which may compile * but will almost certainly crash on 64bit architectures. * message on 64bit ppc64 too. Add us back when bug 308649 is solved Thanks Same for alpha/ia64/sparc Stable for HPPA. Try it now, bug 308649 should be fixed. The package is still a QA mess, forcing -O3 optimization and ignoring LDFLAGS but at least it builds, unlike the current stable. amd64 stable (In reply to comment #17) > Try it now, bug 308649 should be fixed. > The package is still a QA mess, forcing -O3 optimization and ignoring LDFLAGS > but at least it builds, unlike the current stable. > just for the record, -O3 issue fixed now, and LDFLAGS issue is bug 325309 alpha/ia64/sparc stable ppc64 stable (fails to build with asneeded on my ppc64 chroot, btw, I hate this package) |