This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: __gmon_start__ issues between 2.1.x and 2.2.x on sparc(?)
- To: Jack Howarth <howarth at bromo dot med dot uc dot edu>
- Subject: Re: __gmon_start__ issues between 2.1.x and 2.2.x on sparc(?)
- From: Andreas Jaeger <aj at suse dot de>
- Date: 21 Feb 2001 16:07:31 +0100
- Cc: libc-alpha at sourceware dot cygnus dot com
- References: <200102201541.HAA89286@bromo.med.uc.edu>
Jack Howarth <howarth@bromo.med.uc.edu> writes:
> Dan,
> Before you claim the patch doesn't work, make sure you are
> testing it correctly. Remember that this patch will not 'fix'
> broken binaries where you recompiled a program under glibc 2.2
> against glibc 2.1.3 built libs and then replaced those libs
> with ones compiled under glibc 2.2. You have to recompile anything
> you built under glibc 2.2 against the old binutils. Also it gets
> messy if you have recompiled a lot of libs against glibc 2.2. I would
> strongly recommend reverting to a clean installation of only glibc 2.1.3
> built rpms and then start rebuilding things against glibc 2.2 with
> the patched binutils. That will definitely work. It won't unbreak
> your currently broken binaries though.
With the current binutils CVS version I see the following:
$ objdump -R usr/bin/gencat |grep __gmon_start
0000000000023c60 R_SPARC_GLOB_DAT __gmon_start__
0000000000023c4c R_SPARC_JMP_SLOT __gmon_start__
Is this correct? Anything else I can do to check that binutils are
correct now?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj