From: Alexander Popov <s_popov@prosyst.bg>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] problem with cyg/kernel/kapi.h
Date: Fri, 17 Oct 2003 16:23:00 -0000 [thread overview]
Message-ID: <3F901793.3080702@prosyst.bg> (raw)
In-Reply-To: <20031017153338.GA6086@lunn.ch>
Andrew Lunn wrote:
> On Fri, Oct 17, 2003 at 05:44:00PM +0300, Alexander Popov wrote:
>
>>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?
>
>
> Yes you can, with a correctly configured and built system. Not you
> don't need to give the full path either, which is a bad idea.
>
> A guess would be you have a confused build directory. Have you build
> redboot in the same directory? Thats a common mistake.
>
> Start from an empty directory and do a clean configuration and build.
>
> ecosconfig new pc
> ecosconfig tree
> make
10x Andrew,
I found the problem...
When I added the POSIX compatibility layers this was resolved...
btw: the target image that I used was built with the pc-i386 template
(trough configtool)...
bbtw: when I added the POSIX compatibility layer the build failed... it
came out that the CYGSEM_LIBC_SIGNALS_POSIX directive was not added to
the build options ( I had to do this manualy - is that wrong? ).
Without it the cyg/posix/export.h failed on line 100 ( sigset_t was not
defined - it was in cyg/libc/signals/signal.h in the
#ifdef CYGSEM_LIBC_SIGNALS_POSIX ).
>
> Then try your "hello world" with this.
>
> Andrew
>
>
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 16:23 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
2003-10-17 15:33 ` Andrew Lunn
2003-10-17 16:23 ` Alexander Popov [this message]
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=3F901793.3080702@prosyst.bg \
--to=s_popov@prosyst.bg \
--cc=andrew@lunn.ch \
--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).