Re: __gmon_start__ issues between 2.1.x and 2.2.x on sparc(?)

[Ben Collins <bcollins at debian dot org>]

On Mon, Feb 19, 2001 at 07:39:09PM +0100, Franz Sirl wrote:
> At 19:22 19.02.2001, Ben Collins wrote:
> >On Mon, Feb 19, 2001 at 10:14:58AM -0800, Ulrich Drepper wrote:
> > > Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
> > >
> > > > We had the same problem on PPC, AFAIR it was solved by this change in
> > > > binutils/bfd:
> > >
> > > Yep, it's  definitely a binutils bug.
> >
> >Ok, this makes sense then, and seems to be fixed in the latest binutils.
> >Big question is, is there anything I can do to make these "broken"
> >libraries and binaries work under glibc 2.2.x? It's impossible for me to
> >retroactively build an already released Debian sparc distribution, and
> >upgrading needs to be as painless as possible.
> 
> Just recompile glibc-2.2 (well, and all other shared libs you already built 
> against glibc-2.2, but that isn't important for a pure glibc upgrade) with 
> the new binutils and force users to upgrade binutils too if they upgrade to 
> glibc-2.2. For my PPC rpm I just added a "Requires: binutils > 2.10.0.33" 
> to the glibc spec, I think apt supports similar stuff.

Ok, I think I've narrowed down the possible recompiles I need for our
upgrade, and yes, dpkg/apt supports that sort of versioned relationship.

Now to get binutils fixed for elf32-sparc, and I guess elf64-sparc while
I'm at it.

Thanks,
  Ben

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'