Harden_all_packages_with_position-independent_code + guile modules

Tom Hughes tom at compton.nu
Thu Mar 12 17:26:43 UTC 2015

On 12/03/15 17:14, Till Maas wrote:
> On Thu, Mar 12, 2015 at 02:49:03PM +0000, Tom Hughes wrote:
>> On top of which there seems, despite a number of questions posted here since
>> the change went live, very little assistance from the proposal owners with
>> fixing packages that have been broken by it.
> I do not see much value in repeating responses if others have already
> figured something out. So to workaround build failures because of it for
> individual packages is to disable the flags for the respective package.
> This allows to build a package for now so the actual problem can be
> analysed without disturbing updates for the package.

Well I haven't figured out how to fix libdwarf (see message this 
morning) nor do I have any idea what I should do next to try and figure 
it out.

So unless I ignore the "rawhide first" rule it seems I can't update that 
for F22 until the mass rebuild which might apparently fix it in rawhide.

Alternatively I can disable hardened builds, but I assumed that needed 
permission from somebody...


Tom Hughes (tom at compton.nu)

More information about the devel mailing list