Re: memprof trouble on debian

[Owen Taylor <otaylor redhat com>]

Kristian Rietveld <kris gtk org> writes:

> On Thu, 2002-10-03 at 18:33, Owen Taylor wrote:
> > 
> > yves vlaanderen net writes:
> > 
> > > I have looked at the sources of memprof and noticed some i386
> > > asm. My memprob 0.5.0 on debian PPC doesn't seem to find any symbols
> > > when i want to look up memleaks... Is this a i386-only app ?
> > 
> > The i386 asm isn't the (main) reason why it is an i386-only, app, but
> > yes, it is an i386 only app.
> > 
> > (The main reason it is i386-only, is that it doesn't contain the
> > necessary code to get stack tracebacks on other architectures - and in
> > fact, on many other architectures, a completely different and more
> > complex method would be needed. It also (not relevant for ppc32) is
> > badly non-64bit-clean.)
> 
> Would it be useful to add some code to configure.in which checks the
> compiler using gcc -dumpmachine? And if it's not an i386 compiler,
> configure bails out? If so, I can provide a patch to do this.

I think checking the host that autoconf detects probably is better -
you can steal the bits from gtk+'s configure that are used to tell
whether to enable the mmx assembly:

AC_CANONICAL_HOST

[...]

AC_MSG_CHECKING(for x86 platform)
case $host_cpu in
  i386|i486|i586|i686|i786|k6|k7)
	use_x86_asm=yes
        ;;
   *)
  	use_x86_asm=no
esac
AC_MSG_RESULT($use_x86_asm)

Regards,
                                        Owen