public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: mark@codesourcery.com (Mark Mitchell)
Cc: ian@zembu.com (Ian Lance Taylor), binutils@sourceware.cygnus.com
Subject: Re: A 32bit BFD patch
Date: Sun, 11 Jul 1999 00:26:00 -0000	[thread overview]
Message-ID: <19990711072608.BB14157B9@ocean.lucon.org> (raw)
In-Reply-To: <19990710235053Q.mitchell@codesourcery.com>

> 
> 
> H.J., what exactly are the places that fail on a 32-bit host?  I made
> an effort to conditionalize the places that required 64-bit support
> with `#ifdef BFD_64' (or BFD64, I forget which one is the right
> spelling). 
> 
> If you can tell me where the problems lie, I bet I conditionalize the
> right sections.
> 

# cd bfd
# elf64 elf32-mips.c
   ? bfd_elf64_add_dynamic_entry (info, tag, val)  \
bfd_mips_elf64_swap_reginfo_in (abfd, ex, in)
bfd_mips_elf64_swap_reginfo_out (abfd, in, ex)
	      bfd_mips_elf64_swap_reginfo_in
	? bfd_elf64_bfd_final_link (abfd, info)

bfd_elf64_add_dynamic_entry and bfd_elf64_bfd_final_link are only
available for 64bit bfd.

You can verify it by doing

# ..../configure --enable-targets=all --enable-shared

on Linux/x86.


-- 
H.J. Lu (hjl@gnu.org)

  reply	other threads:[~1999-07-11  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-10 10:47 H.J. Lu
1999-07-10 17:53 ` Ian Lance Taylor
1999-07-10 23:47   ` Mark Mitchell
1999-07-11  0:26     ` H.J. Lu [this message]
1999-07-11  9:30       ` Mark Mitchell
1999-07-11  9:37         ` H.J. Lu
1999-07-11  9:46           ` Mark Mitchell
1999-07-11 19:48         ` Ian Lance Taylor

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=19990711072608.BB14157B9@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sourceware.cygnus.com \
    --cc=ian@zembu.com \
    --cc=mark@codesourcery.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).