Re: [PATCH 0/1] Adding aio.h to newlib

For testing, I followed the instruction in the blog written by @Vaibhav Gupta last year for applying a patch to newlib (the blog can be read here: https://medium.com/my-gsoc-2019-journey/apply-newlib-patch-to-rtems-source-builder-6873b0fb31b8 ) After building the toolchain again, aio.h was present

Re: [PATCH 0/1] Adding aio.h to newlib

Hi Eshan, How did you test it? On Thu, Apr 23, 2020 at 12:58 PM Eshan Dhawan wrote: > > hello, > This patch adds aio.h to newlib. > If it is ok should I send it to newlib mailing list?? > thanks > -Eshan > > > On Fri, Apr 24, 2020 at 12:04 AM Eshan dhawan wrote: >> >> Added aio.h in newlib/libc

Re: [PATCH 0/1] Adding aio.h to newlib

hello, This patch adds aio.h to newlib. If it is ok should I send it to newlib mailing list?? thanks -Eshan On Fri, Apr 24, 2020 at 12:04 AM Eshan dhawan wrote: > Added aio.h in newlib/libc/include > > the file is taken from RTEMS (rtems/cpukit/include) > > Build successful for sparc-rtems5 and

[PATCH 1/1] Removed aio.h form cpukit/include and added to newlib

This posix header was in RTEMS and for simplicity had to be shifted to newlib The implementation of the aio.h still stays in posix/src but the header is shifted to newlib/libc/include Closes #3676 Signed-off-by: Eshan dhawan --- cpukit/headers.am| 1 - cpukit/include/aio.h | 193

[PATCH 0/1] shifting aio.h to newlib

This patch removes aio.h from rtems and moves it to newlib This patch will be applied after the newlib patch of adding aio.h to libc/include is pushed and newlib version is bumped in RTEMS Source Builder. Eshan dhawan (1): Removed aio.h form cpukit/include and added to newlib cpukit/headers.am

[PATCH 0/1] Adding aio.h to newlib

Added aio.h in newlib/libc/include the file is taken from RTEMS (rtems/cpukit/include) Build successful for sparc-rtems5 and tested it RTEMS Source Builder (rsb) Eshan dhawan (1): Adding aio.h to newlib/libc/include from RTEMS newlib/libc/include/aio.h | 193 +

[PATCH 1/1] Adding aio.h to newlib/libc/include from RTEMS

Signed-off-by: Eshan dhawan --- newlib/libc/include/aio.h | 193 ++ 1 file changed, 193 insertions(+) create mode 100644 newlib/libc/include/aio.h diff --git a/newlib/libc/include/aio.h b/newlib/libc/include/aio.h new file mode 100644 index 0..95ed0fd

Re: [PATCH] Removes build time warning for all smp-disabled bsps

Although this fixes the warning in the testsuite, it is hackish to require users to copy this kind of conditional compilation to their code, and I don't really like how it looks personally. I might prefer Joel's approach, but applied to the test, e.g., static const char name[] = "test"; (void) nam

Re: [PATCH v12] tests for fenv.h functions

Hello everyone, I sent this patch adding test cases for fenv methods. I would request you all to look into it. And tell if it requires any changes. Or if it could be merged. Thanks -Eshan On Mon, Apr 20, 2020 at 11:52 PM Eshan dhawan wrote: > added tests for fesetexeptflag(), fegetexeptflag(),

Re: Small doubt in a build time warning of sp test of leon3

Dear Dr. Sherill and Huber, Thanks a lot for your help. I have made a patch and sent it on devel. Please check it out. On Thu, Apr 23, 2020 at 12:28 AM Joel Sherrill wrote: > > > > On Wed, Apr 22, 2020 at 1:55 PM Sebastian Huber > wrote: >> >> On 22/04/2020 16:12, Joel Sherrill wrote: >> >> >

[PATCH] Removes build time warning for all smp-disabled bsps

Hey everyone, I made this small change and rebuilt the leon32 bsp. It stopped showing the earlier warnings: log/sparc-leon3.log:../../../../../../rtems/c/src/../../testsuites/sptests/sp37/init.c:172:21: warning: unused variable 'name' [-Wunused-variable] log/sparc-leon3.log:../../../../../../rt

Re: Release task request for help

Dear Mr. Johns, I know Niteesh has agreed to help you with this. But if you ever need another person to work on this,I'll be happy to lend my hands. I always wanted to learn more about the release process and how the merging of different branches take place. Thanks, Richi. On Thu, Apr 23, 2020 a

Re: New build system update

Hello, I updated the documentation to reflect the recent changes (removal of Doorstop usage): https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf ___ devel mailing list devel@rtems.org http://lis

[PATCH] eng: Update requirements engineering chapter

Update requirements engineering chapter due to the removal of Doorstop as the requirements management tool. Update the application configuration related specification items. Update #3715. --- I removed the binary patches due to mailing list size limits. You find a generated document here: http

Re: doubts in new RTEMS Test framework

Hello Eshan, thanks for your interest in the new RTEMS Test Framework. It is good that you ask these questions. It highlights an opportunity to improve the documentation. For the test framework you need a so called runner, for example: https://git.rtems.org/rtems/tree/testsuites/libtests/tte