public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: James Yates <j.yates@quartzuk.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problems with var_mk_defs.c
Date: Wed, 15 Oct 2003 14:41:00 -0000	[thread overview]
Message-ID: <1066228899.32461.51.camel@hermes> (raw)
In-Reply-To: <CB39E7B8FC98924D85DFBED207E4CC9831F8F8@ip02.quartzelec.adsl.gxn.net>

On Wed, 2003-10-15 at 08:35, James Yates wrote:
> In the SH Hal architecture I am getting build problems relating to var_mk_defs.c.  
> If I comment out the code within int main(void), the compile problems go away. 
> When included, every call to DEFINE throws up a bad expression. Can anyone 
> explain to me what this file is actually doing, or indeed why it isn't working 
> as I am completely stuck.

What this program does is to use the target compiler to generate
machine dependent offsets within various structures used by eCos.
These are necessary for various assembly coded modules as they
have no other way to find data within objects (or other values
defined by the C/C++ environment).

We'd need to see the actual errors to be much more help.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-10-15 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 14:34 James Yates
2003-10-15 14:41 ` Gary Thomas [this message]
2003-10-15 15:02 James Yates
2003-10-15 15:09 ` Gary Thomas
2003-10-15 15:45 James Yates
2003-10-15 15:50 ` Gary Thomas
2003-10-16  7:55 James Yates
2003-10-16 12:04 ` Gary Thomas

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=1066228899.32461.51.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=j.yates@quartzuk.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).