Re: gcc problems

From: David Mosberger <davidm_at_napali.hpl.hp.com>
Date: 2004-02-10 18:37:00
>>>>> On Fri, 6 Feb 2004 08:30:50 -0800, Andrew Morton <akpm@osdl.org> said:

  Andrew> Andreas Schwab <schwab@suse.de> wrote:
  >>  The fields were named differently in old versions of glibc, but
  >> the whole layout didn't change in any way.

  >> - unsigned long int sc_rsvd[16];/* reserved for future use */ +
  >> unsigned long int sc_rbs_base;/* NULL or new base of sighandler's
  >> rbs */ + unsigned long int sc_loadrs; /* see description above */
  >> + unsigned long int sc_ar25; /* cmp8xchg16 uses this */ +
  >> unsigned long int sc_ar26; /* rsvd for scratch use */ + unsigned
  >> long int sc_rsvd[12];/* reserved for future use */

  >> > The easiest workaround is probably to install libunwind on your
  >> system

  >> The right fix is not to use a 2 years old glibc.

  Andrew> That's not very old.  One shouldn't have to upgrade libc
  Andrew> just to build gcc?

True in general, but in this particular case, many bugs have been
fixed in glibc in the meantime, especially with respect to unwinding.
So 2 years is old when trying to build a compiler which has reasonable
support for unwinding.

	--david
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Tue Feb 10 02:40:53 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:22 EST