From: Sriharsha Vedurmudi <sriharsha.v@redpinesignals.com>
To: gcc <gcc-help@gcc.gnu.org>
Subject: Re: FW: TS-Linux
Date: Thu, 07 Oct 2004 18:20:00 -0000 [thread overview]
Message-ID: <41658AB7.2070402@redpinesignals.com> (raw)
In-Reply-To: <200410071536.i97Fa1j06489@redpinesignals.com>
The Wells Family wrote:
>We are building a robot and are running TS-Linux on it (I believe it is a
>variant of redhat). The point is we do have much space on the robot but we
>want to add the ability to compile C/C++ programs using makefiles. I am not
>sure where to download just these components or how to get them installed.
>Where should we start? Thanks.
>
>
>
1. Use RT-Linux/uCOS/ThreadX/QNX or a similar RTOS for robots/real-time
applications.
2. If it already does not come pre-installed with the compiler you are
looking for, see if GNU GCC supports that platform/processor. If it
does, the best thing is to build gcc with ONLY C front end enabled and
also remove unwanted/unnecessary options.
3. If it does not come with GNU GCC or if GCC does not support that
processor/platform, you need to port it to that processor.
So, first you visit GNU site gcc.gnu.org and check if your processor is
supported. If not, search the net for any C compiler that does. When
everything fails, in your interest, you can start a Porting Project (if
it is worthy enough for your project).
Cheers,
Harsha.
--
*****************************
* Sriharsha Vedurmudi
* Software Engineer
*
* Redpine Signals Inc.
* Gate #395, Plot 87,88
* Sagar Society, Road #2,
* Banjara Hills,
* Hyderabad - 500 034
* www.redpinesignals.com
*
* +91-40-23559911 (Office)
* +91-9849133133 (Mobile)
*****************************
next parent reply other threads:[~2004-10-07 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410071536.i97Fa1j06489@redpinesignals.com>
2004-10-07 18:20 ` Sriharsha Vedurmudi [this message]
2004-10-07 17:55 The Wells Family
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 17:55 The Wells Family
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=41658AB7.2070402@redpinesignals.com \
--to=sriharsha.v@redpinesignals.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).