public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: mnskrishna@soc-soft.com
Cc: sid@sources.redhat.com
Subject: Re: Need information about passing command line arguments.
Date: Thu, 12 Jan 2006 13:15:00 -0000	[thread overview]
Message-ID: <20060112131517.GB21458@redhat.com> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C012893FF@soc-mail.soc-soft.com>

Hi -

On Thu, Jan 12, 2006 at 11:22:42AM +0530, mnskrishna@soc-soft.com wrote:
> One more request how to find GLOSS-COMPONENT, I tried --save-temps it
> gives help information related to options mentioned below
> [...]
> --save-temps=FILE     Write config to FILE, '-' for stdout.
> [...]

As the option says, you have to give "--save-temps" an argument
to specify where the sid configuration file should be written to.

> please let us know what is GLOSS-COMPONENT?

In general, a GLOSS sid component emulates the system call / OS layer
by intercepting CPUs' trap instructions.  Such a component should be
configured into the simulation in order for it to run "hosted" C
programs that use stdio, argv[], and so on.  If the "--board=MM_.."
does not already have it, you may have to add the sid "--gloss"
option, if that is a supported configuration for the MM* (mep)?
family.

For "GLOSS-COMPONENT" in my command line example, substitute the
reference name of the gloss component instance that you will find in
the sid configuration file, the one hooked up to the CPU.

- FChE

  reply	other threads:[~2006-01-12 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  5:52 mnskrishna
2006-01-12 13:15 ` Frank Ch. Eigler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-12 13:51 mnskrishna
2006-01-12 15:52 ` Frank Ch. Eigler
2006-01-12 10:19 mnskrishna
2006-01-12 10:07 mnskrishna
2006-01-12  7:20 mnskrishna
     [not found] <4BF47D56A0DD2346A1B8D622C5C5902C01288F49@soc-mail.soc-soft.com>
2006-01-12  0:10 ` Frank Ch. Eigler

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=20060112131517.GB21458@redhat.com \
    --to=fche@redhat.com \
    --cc=mnskrishna@soc-soft.com \
    --cc=sid@sources.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).