[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

binutils requirements for gcc 3.2 rebuild



Matthias,
    Ben Collins suggest this should be passed off to you as a
Build-Depends and Depends for gcc-3.2. On ppc (and perhaps all
arches) we should have the minimal binutils set to 2.13.90.0.6
or greater once Chris Chimelis solves his hardware problems
and can get new debian binutils packages ready. 
    On ppc, a fix was introduced at binutils 2.13.90.0.5 which 
changed how *r_offset is set so it is no longer a non-zero value.
This is critical to prelink being able to unprelink a prelinked
binary back to an identical copy of the unprelinked original.
The binutils behavior pre-2.13.90.0.5 was such that unpredictable
non-zero values were placed in *r_offset making it impossible
to predict the original value again. This is solved in 2.13.90.0.5
by adopting a zero value for *r_offset like all the other arches
do.
   The need for binutils 2.13.90.0.6 arises from a glitch I ran
across where binutils would produces shared libraries that were
not properly -zcombreloc. HJ Lu and Alan Modra added two fixes...
the correct ppc-specific one and a general safety net fix to
prevent any arch from having this bug in the future. So while
the problem has only been demonstrated on ppc, it may impact
other arches as well. 
    Thanks in advance for dealing with this.
                               Jack



Reply to: