Brendan O'Dea writes: > On Sun, Jul 16, 2006 at 05:20:07AM +0200, Matthias Klose wrote: > >The g++-4.1 workaround introduced in 5.8.8-6 can be removed; fixed in > >4.1.1-7 and up. > > Thanks Matthias. > > Currently perl has a build-depend on a specific version of "gcc", do I > need to change that to "gcc (>= 4:4.1.1-7) | gcc-4.1 (>= 4.1.1-7)" or > does gcc-defaults require a version bump? > > An additional issue which occurs to me is that if I revert the change so > that perl.h distributed in the perl package again contains the register > declaration, this may cause problems with building binary modules or > programs which embed perl unless those packages also declare a similar > build-dependency.
right, but that should not be the problem of the perl package. > Drats. Pity build-dependencies aren't transitive. you could add conflicts (as the build-conflicts below). but maybe more ugly. > Do you think that it's safe to at least assume that the build daemons > will have the newer g++ installed? not sure, but the easiest thing would be do build-conflict with gcc-4.1 (= 4.1.1-7), gcc-4.1 (= 4.1.1-6), gcc-4.1 (= 4.1.1-5), ... I'm unsure, which version was the first version to have that bug. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
