public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002026] uSTL does not build
Date: Sat, 29 Nov 2014 12:51:00 -0000	[thread overview]
Message-ID: <bug-1002026-13-T3zdSaB2Ch@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1002026-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002026

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |MODIFIED

--- Comment #8 from John Dallaway <john@dallaway.org.uk> ---
Hi Ilija 

(In reply to comment #7)

> RFC / proposal
> 
> stdint.h file does not belong to USTL. Probably it has been added in order
> to satisfy USTL need for some (ISO) typedefs.
> 
> The file in it's contents and design is quite general and the types that it
> defines are needed by many software packages.
> 
> Therefore I propose to move this file in isoinfra/current/include .
> 
> Please comment. If necessary I can open a bug.

Agree. stdint.h is not part of uSTL upstream. Ideally we would update eCos to
fully support C99. I have no problem with relocating stdint.h as a step in this
direction. The isoinfra/current/include/*.h headers appear to wrap headers
provided by the various C library packages so we should probably mirror the
mechanism used with these other headers.

Regarding the compiler warnings, they may be already fixed upstream. Ideally,
this sort of fix should be contributed upstream first to keep divergence to an
absolute minimum.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-29 12:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-09 21:16 [Bug 1002026] New: " bugzilla-daemon
2014-11-09 21:18 ` [Bug 1002026] " bugzilla-daemon
2014-11-10  8:36 ` bugzilla-daemon
2014-11-10 11:39 ` bugzilla-daemon
2014-11-17 11:57 ` bugzilla-daemon
2014-11-29 12:51 ` bugzilla-daemon [this message]
2014-12-01  0:02 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2014-11-09 21:16 [Bug 1002026] New: " bugzilla-daemon
2014-11-10  8:36 ` [Bug 1002026] " bugzilla-daemon

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=bug-1002026-13-T3zdSaB2Ch@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@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).