public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Daniel.Andersson@combitechsystems.com
To: Linus.Nielsen@elema.siemens.se, crossgcc@sourceware.cygnus.com
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Macro problem with gcc and eCos
Date: Thu, 19 Apr 2001 23:51:00 -0000	[thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B02DA4CBA@pluto.combitech.se> (raw)

Yes you were right, it was the CR/LF problem. I have now wrote a tcl script
that converts all files from dos2unix format.

Thanks!

/Daniel

-----Original Message-----
From: Nielsen Linus [ mailto:Linus.Nielsen@elema.siemens.se ]
Sent: den 19 april 2001 15:09
To: Andersson Daniel; crossgcc@sourceware.cygnus.com
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Macro problem with gcc and eCos


This looks like a CR/LF problem. AFAIK, the GCC preprocessor isn't
always too happy about text files that end with CR/LF.
Try to remove the CR's and compile again.

/Linus

> Hi,
> 
> I have problems when I compile my application together with eCos
> using gcc for ARM. When I try to compile the code section with 
> VC++ it works without problem.
> 

<snippe
> The eCos code I got problem with looks like this:
> 
> ------snip--------
> #define CYG_MACRO_START do{
> #define CYG_MACRO_END   }while (0)
> 
> #define CYG_EMPTY_STATEMENT CYG_MACRO_START CYG_MACRO_END
> 
> #define CYG_UNUSED_PARAM( _type_, _name_ ) CYG_MACRO_START      \
>   _type_ __tmp1 = (_name_);                                     \
>   _type_ __tmp2 = __tmp1;                                       \
>   __tmp1 = __tmp2;                                              \
> CYG_MACRO_END
> -------end snip----
> 
> 
> It gives me the following error:
> 
> ------snip--------
> arm-elf-gcc -mcpu=arm7tdmi                         -c -o 
> twothreads.o -g
> -Wall -I/ecos-work/include -ffunct
> ion-sections -fdata-sections  twothreads.c
> In file included from /ecos-work/include/cyg/kernel/kapi.h:53,
>                  from twothreads.c:1:
> /ecos-work/include/cyg/infra/cyg_type.h:169: parse error 
> before `__tmp1'
> /ecos-work/include/cyg/infra/cyg_type.h:169: warning: type 
> defaults to `int'
> in declaration of `__tmp1'
> /ecos-work/include/cyg/infra/cyg_type.h:169: `_name_' 
> undeclared here (not
> in a function)
> /ecos-work/include/cyg/infra/cyg_type.h:169: warning: data 
> definition has no
> type or storage class
> -------end snip----
> 
> Does anyone know what the problem is?
> 
> /Daniel
> 

             reply	other threads:[~2001-04-19 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 23:51 Daniel.Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19  6:10 Nielsen Linus
2001-04-19  5:58 Daniel.Andersson

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=2253171AF143D21185A60000F8FA748B02DA4CBA@pluto.combitech.se \
    --to=daniel.andersson@combitechsystems.com \
    --cc=Linus.Nielsen@elema.siemens.se \
    --cc=crossgcc@sourceware.cygnus.com \
    --cc=ecos-discuss@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).