Summary: | librep 0.16.1 ebuild causes various bugs in sawfish | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matt Tucker <tuck> |
Component: | New packages | Assignee: | foser (RETIRED) <foser> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matt Tucker
2003-02-17 19:18:30 UTC
well hmm.. dunno, it seems this is the only way some ppl can get sawfish to work. I'm confused. Disabling gmp is the only way some people can get sawfish to work? What kind of bugs are they seeing when it's enabled? And what about the thing with readline? I use sawfish-client; having readline enabled is nice. If people don't want it, isn't that what USE flags are for? bugs long ago.. forgot what it was exactly about. You checked in a change nine days ago to fix bugs from long ago that you can't even remember? Does that sound weird to you? is this nine days ago ? then its a mistake.. ill have a look. I just started from scratch with 1.4_rc2 a couple of days ago and ran into librep and sawfish weirdness. I tried to emerge sawfish, which wanted librep-0.16.1 and rep-gtk-0.17 (but not gmp). When rep-gtk tries to build, it compiles a couple of files and then gets into a deadlock waiting for some files to be removed. I get the following lines repeated infinitely: Waiting for rep-types.o.lock to be removed Waiting for rep-gtk.o.lock to be removed Man, this is frustrating. Now, I can't reproduce the deadlock. Anyway, even if I do get sawfish to compile, which I have a couple of times, it doesn't work. It just complains like this: Bad argument: #<closure make-lut>, , 3 Bad argument: #<closure make-lut>, , 3 Bad argument: #<closure make-lut>, , 3 The original link I meant to include was <http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/dev-libs/librep/librep-0.16.1.ebuild.diff?r1=1.7&r2=1.8>, which shows the changes I'm talking about. Jonathan, have you tried reversing these changes in the ebuild and rebuilding librep to see if it solves your problems? i think the current stable version in portage 0.16.1-r1 should fix this screwup, can you guys confirm so i can close ? Sorry for the mess. Works for me. Thanks. ok closing, again sorry for the mess up |