public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] latest glibc snapshot does not build on ia64?
Date: Tue, 03 Sep 2002 17:46:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701906011@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701906009@msgid-missing>

In reference to a message from Wichmann, Mats D, dated Sep 03:
> 
> > Haven't dug into this too much yet; wanted to see if anyone else has
> > seen this?
> 
> Yup.
> 
> There's a short glibc patch which takes care of this (should be on the
> Debian lists, else I can mail it to you once I get my machine back up).
> It's an "unofficial"  patch because it's felt the problem really lies 
> with binutils and not glibc, so it's not in glibc cvs.   The change
> is to dl-machine.h if it helps search...

there was a IA64_RELOC_NONE patch, but in a different area of glibc...
looks like we just hit it again at a different spot now...


    580   /* ??? Ignore MSB and Instruction format for now.  */
    581   if (R_IA64_FORMAT (r_type) = R_IA64_FORMAT_64LSB)
    582     *reloc_addr = value;
    583   else if (R_IA64_FORMAT (r_type) = R_IA64_FORMAT_32LSB)
    584     *(int *) reloc_addr = value;
    585   else if (r_type = R_IA64_IPLTLSB)
    586     {
    587       reloc_addr[0] = 0;
    588       reloc_addr[1] = 0;
    589     }
    590   else
    591     assert (! "unexpected dynamic reloc format");

r_type is 0 at the assertion 

randolph


  parent reply	other threads:[~2002-09-03 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 16:26 [Linux-ia64] latest glibc snapshot does not build on ia64? Randolph Chung
2002-09-03 16:55 ` Wichmann, Mats D
2002-09-03 17:46 ` Randolph Chung [this message]
2002-09-03 19:00 ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590701906011@msgid-missing \
    --to=randolph@tausq.org \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox