Rob Tillotson wrote: > > I just tried rebuilding pilot-link, after making the changes in > debian/rules suggested in the BTS entry (changing all "egcc" to > "gcc"), and could not reproduce the bug.
The bug is really for potato and is Alpha-based (again). I'll look into this one now as well. It *should* build fine, if past pilot-link experience is worth anything. Then again, new upstream versions frequently break things. As a start, though, let's incorporate the patches submitted in #27941 (I'll do this here) and try again. Also, fyi, when egcs is built, despite the fact that it's a primary compiler on the Alphas (hence is 'gcc'), a link named 'egcc' is installed pointing to gcc. > I've never dealt with a bug in someone else's package before; does > this mean that I should do an NMU and close the bug, or...??? > > (I really don't want to see pilot-link drop out, as it will take two > of my packages, ones I am the "upstream" author of no less, with it.) Agreed. This is a useful package (granted, I don't have a Palm-series machine, but still...).... At any rate, it should be ok to ignore this bug relating to release criteria since it applies to the potato version of the package. C
