public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: larwe@larwe.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] A hello world problem
Date: Mon, 04 Dec 2000 11:21:00 -0000	[thread overview]
Message-ID: <200012041920.eB4JKnL22128@sheesh.cygnus> (raw)
In-Reply-To: <4.3.2.7.2.20001204120947.00ab8e50@larwe.com>

>>>>> "Lewin" == Lewin A R W Edwards <larwe@larwe.com> writes:

    Lewin> In file included from ../ecos_work/DigiOS_install/include/stdio.h:56, from 
    Lewin> hello.c:1:
    Lewin> ../ecos_work/DigiOS_install/include/cyg/infra/cyg_type.h:160: parse error 
    Lewin> before '__tmp1'
    Lewin> ../ecos_work/DigiOS_install/include/cyg/infra/cyg_type.h:160: '_name_' 
    Lewin> undeclared here (not in a function)
    Lewin> ../ecos_work/DigiOS_install/include/cyg/infra/cyg_type.h:160: warning: data 
    Lewin> definition has no type or storage class
    Lewin> ../ecos_work/DigiOS_install/include/cyg/infra/cyg_type.h:160: stray '\' in 
    Lewin> program

    Lewin> [and many more errors]

    Lewin> Can anyone help? This is using a "canonical" installation of eCos cygwin 
    Lewin> arm-elf, ie binutils 2.10 and gcc 2.95.2, and eCos 1.3.1 so it ought to work.

Looking at the relevant header file, it appears to be the following
macro that is causing the problem:

#define CYG_UNUSED_PARAM( _type_, _name_ ) CYG_MACRO_START      \
  _type_ __tmp1 = (_name_);                                     \
  _type_ __tmp2 = __tmp1;                                       \
  __tmp1 = __tmp2;                                              \
CYG_MACRO_END

Note the backslashes at the end of the line. The error messages you
are seeing are a sure sign that they are ignored, i.e. there is junk
data at the end of the line. Under Windows the most likely problem is
that you are using a file containing carriage-return/linefeed pairs
via a binary mount point. The eCos sources and build trees should be
kept on a text mount point. The sources as supplied contain carriage
returns for the benefit of any Windows users who want to use utilities
like notepad. The instructions for installing under Windows,
http://sources.redhat.com/ecos/install-windows.html ,
specifically mention text mount points.

See e.g.
http://sources.redhat.com/ml/ecos-discuss/2000-10/msg00283.html and
http://sources.redhat.com/ml/ecos-discuss/2000-10/msg00297.html for
an earlier discussion.

Bart

  parent reply	other threads:[~2000-12-04 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-04  9:32 Lewin A.R.W. Edwards
2000-12-04  9:52 ` Andrew Lunn
2000-12-04 10:13   ` Lewin A.R.W. Edwards
2000-12-04 10:26     ` Andrew Lunn
2000-12-04 10:37       ` Lewin A.R.W. Edwards
2000-12-04 11:21 ` Bart Veer [this message]
2000-12-04 11:39   ` Lewin A.R.W. Edwards
2000-12-06  1:04 Fano Ramparany

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=200012041920.eB4JKnL22128@sheesh.cygnus \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=larwe@larwe.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).