Hi! On Fri, Mar 07, 2008 at 04:50:34PM -0800, Jeff W wrote: > Any update with this bug?
Yeah. While I may not be the fastest bug-fixer myself, I've been trying to get a sponsored upload which should fix this one for quite some time... > I am now suddenly and without explanation running into this problem > when I was able to use tcc perfectly fine before. Could you please test the version at: (source) dget http://angband.pl/debian/pool/main/t/tcng/tcng_10b-1.kb8.dsc (i386 binary) http://angband.pl/debian/pool/main/t/tcng/tcng_10b-1.kb8_i386.deb I could not reproduce the bug, yet there is only one route by which the build path is used by the package. In the version still in Debian archive, it is then covered by the following hack: #!/bin/sh TCNG_TOPDIR=/usr/lib/tcng exec /usr/lib/tcng/bin/tcc "$@" Apparently, under some scenarios the env var doesn't get through. Whatever the reason is, my pending version stores that path at configure time instead. And if that's not enough, please tell me. Just per chance you're a DD or have one next room... the "official" version for sponsoring is at mentors.debian.net, with s/10b-1.kb8/10b-2/. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
