public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew McCall <andrew.mccall@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: Compiling, --target question...
Date: Tue, 05 Jul 2005 09:34:00 -0000	[thread overview]
Message-ID: <4aa50a460507050234e00789e@mail.gmail.com> (raw)
In-Reply-To: <42CA4D25.8010705@redhat.com>

On 7/5/05, Nick Clifton <nickc@redhat.com> wrote:
> Hi Andrew,
> 
> > As the target powerpc-*-beos already exists making coff's do I need to
> > create a new platform powerpc-*-haiku that will make elf's, or is
> > there anyway to specify that -powerpc-*-beos can produce elf's too?
> 
> No sorry you need a new target.  powerpc-*-haiku is OK, but since there
> is already an i*86-*-beoself target supported you might prefer to use:
> powerpc-*-beoself.

I spoke to a few members of the Haiku project last night about this -
they are planning to use *-*-haiku and submit a patch to yourselves,
so its going to be best to use powerpc-pc-haiku, i586-pc-haiku or
sparc-pc-haiku (thinking a bit too far ahead here :) ).  All versions
are going to use elf.

I spent the night hacking around the build system, and I think I
managed to get it to target powerpc-pc-haiku using elf, but I don't
really know how to extract what I have done to make a patch.  If I
upload a tar.gz of what I have done, can someone take a look to see if
its right?

Thanks,

Andrew McCall

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

  reply	other threads:[~2005-07-05  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 15:49 Andrew McCall
2005-07-04 22:12 ` Andrew McCall
2005-07-05  9:00   ` Nick Clifton
2005-07-05  9:34     ` Andrew McCall [this message]
2005-07-05  9:40       ` Nick Clifton

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=4aa50a460507050234e00789e@mail.gmail.com \
    --to=andrew.mccall@gmail.com \
    --cc=binutils@sources.redhat.com \
    --cc=nickc@redhat.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).