public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "kernel coder" <lhrkernelcoder@gmail.com>
To: "Piotr Pałka" <piopalka@interia.pl>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Porting gcc
Date: Tue, 20 Jun 2006 14:20:00 -0000	[thread overview]
Message-ID: <f69849430606200720r201a6be3vca95462705bd3169@mail.gmail.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAALKcLi1qHZhErgRGJNGL3/vCgAAAEAAAANwAHGxqc39GhqoBF1UHvtcBAAAAAA==@interia.pl>

> And the second think is the problem with compiling gcc source. I want to
> compile it for cris, so I do that:
> - configure --target=cris
> - make
> And I get the following error:
> "No rules to make object '/usr/local/bin/crx-as', needed by 'stamp-as'.
> Stop."

you need to give path of binutils for cris architecture.First compile
binutils for cris architecture and then set the PATH variable to the
directory containing compiled binutils for cris architecture.

shahzad

On 6/13/06, Piotr Pałka <piopalka@interia.pl> wrote:
> Hello,
>
> I want to "learn" gcc to work with mu0core microprocessor (see attachment).
> I would be appreciated for any useful advice how to accomplish that.
> I haven't much time to do that, so if you can, please provide the fastest
> solution.
> I read something about porting gcc, on cris example. Is that the right way I
> should go?
> Should I define md file?
>
> And the second think is the problem with compiling gcc source. I want to
> compile it for cris, so I do that:
> - configure --target=cris
> - make
> And I get the following error:
> "No rules to make object '/usr/local/bin/crx-as', needed by 'stamp-as'.
> Stop."
>
> If I cannot compile gcc for some target machine(eg. Mu0core) how could I
> test what I write?
>
> Best regards,
> Piotr Pałka
>
>
> ----------------------------------------------------------------------
> INTERIA.PL dla kobiet... >>> http://link.interia.pl/f193b
>
>
>

  reply	other threads:[~2006-06-20 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 18:48 Piotr Pałka
2006-06-20 14:20 ` kernel coder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 11:26 Porting GCC Petar Penchev
2000-09-13 23:42 porting gcc Kiran Kumar K
2000-09-13  2:59 brahmaiah vallabhaneni
2000-09-13 19:38 ` Alexandre Oliva
2000-09-13  2:56 brahmaiah vallabhaneni

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=f69849430606200720r201a6be3vca95462705bd3169@mail.gmail.com \
    --to=lhrkernelcoder@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=piopalka@interia.pl \
    /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).