From: Alexander Popov <s_popov@prosyst.bg>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] problem with cyg/kernel/kapi.h
Date: Fri, 17 Oct 2003 14:44:00 -0000 [thread overview]
Message-ID: <3F900030.8060904@prosyst.bg> (raw)
In-Reply-To: <3F8FFD49.5090606@prosyst.bg>
I can't find cyg_handlg_t in the header files for the target.
What am I doing wrog - can I use cyg/kernel/kapi.h that way?
Alexander Popov wrote:
> Hi,
>
> I am trying to port Wonka to ecos/i386 and I came to this problem when
> ytrying to include <target>_install/include/cyg/kernel/kapi.h:
>
>
> [long@popov delme]$i386-elf-gcc
> -I/opt/ecos/ecos-2.0/tools/bin/default-i386_install/include -nostdlib
> -Ttarget.ld -static -o delme delme.c
> In file included from delme.c:1:
> /opt/ecos/ecos-2.0/tools/bin/default-i386_install/include/cyg/kernel/kapi.h:481:
> parse error before "mbox"
> [long@popov delme]$ cat delme.c
> #include
> "/opt/ecos/ecos-2.0/tools/bin/default-i386_install/include/cyg/kernel/kapi.h"
>
> #include <stdio.h>
>
> int main(){
>
> printf("Echo World!\n");
> }
>
> Any hints?
>
> Best Regards,
--
Alexander Popov ProSyst Bulgaria Inc.
RTOS Leader 48 Vladajska Str.
RTOS and JVM Dept. Sofia 1606, Bulgaria
Phone: +359 2 952 3581/203 http://www.prosyst.com
Mobile: +359 887 663 193 OSGi Technology Leaders
----------------------------------------------------------
The wonderful thing about Linux is that there is always at
least one more undiscovered way to do almost anything.
Lewin A.R.W. Edwards (comp.os.linux.embedded)
----------------------------------------------------------
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-17 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 14:31 Alexander Popov
2003-10-17 14:44 ` Alexander Popov [this message]
2003-10-17 15:33 ` Andrew Lunn
2003-10-17 16:23 ` Alexander Popov
2003-10-17 16:45 ` 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=3F900030.8060904@prosyst.bg \
--to=s_popov@prosyst.bg \
--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).