This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1002026] uSTL does not build


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

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

Ilija Kocho [ÐÐÐÑÐ ÐÐÑÐ] <ilijak@siva.com.mk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #2555|0                           |1
        is obsolete|                            |

--- Comment #9 from Ilija Kocho [ÐÐÐÑÐ ÐÐÑÐ] <ilijak@siva.com.mk> ---
Created attachment 2556
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2556&action=edit
stdint.h with applied patch. 141201

(In reply to comment #8)
> 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.
> 

I did some overview of isoinfra includes. Then I tried /#include_next/ method,
used by some headers but it didn't work for stdint.h. I also found out that the
stdint.h found in USTL package is adapted for eCos from NewLib [Ref:
https://sourceware.org/ml/newlib/2005/msg00555.html]. Here I attach the patched
version for easy inclusion.


> 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.

I am not involved inuSTL project, and producing parches would take me too much
time. However I can submit eCos paches, they should be able to locate them in
their code.

Ilija

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]