From: Andrew Lunn <andrew@lunn.ch>
To: Juergen Lambrecht <J.Lambrecht@televic.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] redefinition of `cyg_uint32'
Date: Wed, 17 May 2006 15:58:00 -0000 [thread overview]
Message-ID: <20060517155527.GL14082@lunn.ch> (raw)
In-Reply-To: <446B3B59.70801@televic.com>
On Wed, May 17, 2006 at 05:03:53PM +0200, Juergen Lambrecht wrote:
> Hello,
>
> I get compiler errors for all `cyg_uintxxx' types, e.g.
>
> redefinition of `cyg_uint32'
>
> This is because the build directory
> ecos_ims/install/include/linux/types.h contains the following wrong code:
>
> #include "cyg/infra/cyg_type.h"
>
> #define uint8_t cyg_uint8
> #define uint16_t cyg_uint16
> #define uint32_t cyg_uint32
>
> #define int8_t cyg_int8
> #define int16_t cyg_int16
> #define int32_t cyg_int32
>
> The types above are redefined because "cyg/infra/cyg_type.h" already
> defines them (ecos/packages/infra/current/include/cyg_type.h
cyg_types.h only defines the cyg_* types. It does not define the onces
without cyg_ . Hence why the linux/types.h exists.
However i don't see how this can cause a problem. Please can you give
a real test case to reproduce the error.
Thanks
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-17 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 15:07 Juergen Lambrecht
2006-05-17 15:58 ` Andrew Lunn [this message]
2006-05-18 2:59 ` [ECOS] error building ecos application for LEON Agus Ariffianto
2006-05-18 14:45 ` [ECOS] redefinition of `cyg_uint32' Jürgen Lambrecht
2006-05-18 14:54 ` Andrew Lunn
2006-05-18 21:40 ` Jurgen Lambrecht
2006-05-23 8:23 ` [ECOS] Patch for " Juergen Lambrecht
2006-05-23 8:25 ` [ECOS] " Andrew Lunn
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=20060517155527.GL14082@lunn.ch \
--to=andrew@lunn.ch \
--cc=J.Lambrecht@televic.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).