On Wed, Dec 05, 2012 at 03:13:16PM +0100, Salvatore Bonaccorso wrote: > Control: reassign 675895 icu 4.8.1.1-7 > Control: fixed 675895 4.8.1.1-8 > Control: affects 675895 + parrot > > Hi Alessandro and Jay > > On Tue, Jun 05, 2012 at 02:22:07PM -0400, Jay Berkenbilt wrote: > > Alessandro Ghedini <[email protected]> wrote: > > > > > Apparently it's "icu-config --ldlfags" (called by Parrot's build system) > > > who > > > brings in the PIE options (along with all the other hardening build > > > flags). > > > Using --ldflags-libsonly should do (I'm working on it). > > > > > > The fact that icu-config passes all those build flags doesn't sound quite > > > right > > > though and may cause other packages to FTBFS. Jay, what do you think? > > > > Yes, this is a bug in ICU. I'll switch it back to using > > hardening-wrapper. This came in when I changed from that to > > dpkg-buildoptions. There are odd things with icu's build system.... > > I was going trough the list in [1], so the bugs 'affecting wheezy, but not > sid'. With the above I tried to reassign and marking correct version > so that this should not show up.
Thanks.
> I have builded the current version in wheezy (4.0.0-3) both in wheezy
> and unstable (which both have icu 4.8.1.1-10.
Yeah, I had marked it as fixed in icu/4.8.1.1-8 without reassigning, but it
seems that it doesn't work like that.
> But it looks there is another FTBFS on ia64[2].
Yup, that's #689177, which is sid-only.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
