From: Piet/Pete Delaney <piet@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] elf64
Date: Fri, 22 Mar 2002 02:07:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905327@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905325@msgid-missing>
On Fri, Mar 22, 2002 at 12:26:48PM +1100, Keith Owens wrote:
> On Thu, 21 Mar 2002 17:20:30 -0800,
> Piet/Pete Delaney <piet@sgi.com> wrote:
> >I was wondering if elf64 is a feature provided in
> >recient version of binutils for ia64.
>
> Don't understand the question. All 64 bit machines require elf 64 bit
> support.
HP's gdb Autoconfig classified RedHat ia64 7.2 as a configuration with a 'oldld'
and I thought maybe it was just the autoconfig bdf files that were wrong
so I classified the linuxoldld as a elf64 and got a problem with the
the elf_em.h missing:
-------------------------------------------------------------------------
ia64*-*-*elf64*)
targ_defvec¿d_elf64_ia64_vec
targ_selvecs¿d_elf64_ia64_little_header_vec
;;
+ ia64-unknown-linuxoldld*)
+ targ_defvec¿d_elf64_ia64_vec
+ targ_selvecs¿d_elf64_ia64_little_header_vec
+ ;;
--------------------------------------------------------------------
Unfortunatley that results in:
---------------------------------------------------------------------
cc -c -DHOST_IA64 -I. -I. -I./../include elf64-ia64.c
elf64-ia64.c:43:20: elf_em.h: No such file or directory
make[1]: *** [elf64-ia64.o] Error 1
make[1]: Leaving directory `/home/piet/src/kwdb/src/bfd'
make: *** [all-bfd] Error 2
-------------------------------------------------------------------------
Looks like David Mosberger version of bdf/elf64-ia64.c has replaced
the Copyright 1993 version in HP's code.
Looks like I picked up code that's very out of date.
-piet
prev parent reply other threads:[~2002-03-22 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 1:20 [Linux-ia64] elf64 Piet/Pete Delaney
2002-03-22 1:26 ` Keith Owens
2002-03-22 2:07 ` Piet/Pete Delaney [this message]
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-105590701905327@msgid-missing \
--to=piet@sgi.com \
--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