Hi,
> I've an interesting problem: bug #675125. > Its a grave bug against slang2, as it breaks jed, (and other things). > slang2-2.2.14-12+ (in sid) breaks jed for certain locales (C is broken, > *.UTF-8 look fine); > but slang2_2.2.14-10 (in testing) looks fine. > > The trouble is, while downgrading to -10 fixes issues, _rebuilding_ -10 > in sid results in a > broken libslang2 ; i.e. the problem is not the slang2 package, but the > build environment. > So far i've tested with ncurses, locale from testing but haven't found > the cause yet. > > While i'm still investigating, _something_ in the sid environment is the > real culprit and > I can't assign a bug to it yet until I pin it down. Has anyone seen a > similar issue elsewhere, > or got a hint as to how to handle it? I want to make sure we don't just > freeze on the current slang but ship the > broken environment. Try gcc/g++ 4.6 instead of 4.7. Maybe check if "S-Lang load path" (wherever that is stored) is initialized in a sane way. I had a similar issue where an integer was 0 all the time - although not being initialized with something useful - which changed with gcc 4.7, then it was just a random value :) -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fe0e915.1090...@bzed.de
