public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Jasmin J." <jasmin@anw.at>
To: pcm@ptd.net, crossgcc@sourceware.org
Subject: Re: Ct-ng powerpc-eabi target unrecognized
Date: Wed, 16 Mar 2016 20:44:00 -0000	[thread overview]
Message-ID: <56E9C5C2.2050403@anw.at> (raw)
In-Reply-To: <0F6636B8-C69C-4B99-8B24-B8AB01ACC385@ptd.net>

Hi!

 > but ct-ng doesn't seem to support powerpc-eabi.
Why you think this?
I guess, because there is currently no sample existing for this combination.

 > On the other hand, I see traffic on crossgcc and elsewhere where people
 > claim to be building it.
You can see, it is possible to build such a compiler.

CT-NG is a very intelligent script collection, which builds any cross compiler
you want. The only thing you need to do is configuring it according to you
needs. Generally spoken, if GCC supports it, CT-NG can build it. But there
is also the libc, which needs to support your combination. And sometimes there
are really problems and this is why we have patches for all the different
tools you need to build a cross compiler.

 > I need to build a toolchain which works with the Metrowerks powerpc
 > elf/dwarf2 toolchain, which is eabi(I think).
Sorry, I can't help you here.
Maybe you can find a build script for your specific compiler and use it as a
pattern to configure CT-NG or simply try it on yourself. Once you have it, it
would be nice if you could contribute your configuration as new sample.

BR,
    Jasmin

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2016-03-16 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 20:09 pcm
2016-03-16 20:44 ` Jasmin J. [this message]
2016-03-17  8:51 ` Vania Joloboff

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=56E9C5C2.2050403@anw.at \
    --to=jasmin@anw.at \
    --cc=crossgcc@sourceware.org \
    --cc=pcm@ptd.net \
    /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).