Re: [PATCH] vprintf: Add handler that mutes all output.

Hello Chris, I added a small note in libbsd.txt. The rest of the patch is left the same. If you don't disagree with that, I'll push this slightly adapted patch in the next few days. Best regards Christian ___ devel mailing list devel@rtems.org http://

[PATCH v2] vprintf: Add handler that mutes all output.

This adds a vprintf handler that can be used to suppress all outputs of the libbsd. --- libbsd.txt| 24 rtemsbsd/include/rtems/bsd/bsd.h | 9 + rtemsbsd/rtems/rtems-kernel-vprintf.c | 10 ++ 3 files changed, 43 insertions(+

Re: GSOC proposal - Runtime tracing

Hello Vidushi, the RTEMS Trace Linker is definitely an interesting tool to track down difficult and specific issues. However, this is a nice to have optional feature from my point of view. We should focus on basic functionality and this is interrupt entry/exit and thread switching. This should

Re: [PATCH] libcpu: Only build if there is a valid configure.ac

Thanks for this patch. I used a git clean -iX, to get rid of the empty directories, but this was pretty annoying. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@emb

Re: Empting libcpu ...

On 23/03/2018 14:20, Joel Sherrill wrote: > I have been doing a bootstrap -c before each pull recently. If not, you have > to > manually remove any remnant Makefile.in files. Quite confusing and has bitten > myself, Jeff, and Jennifer. > > Maybe bootstrap -c could be smarter. > It makes no diff

Re: Empting libcpu ...

I have been doing a bootstrap -c before each pull recently. If not, you have to manually remove any remnant Makefile.in files. Quite confusing and has bitten myself, Jeff, and Jennifer. Maybe bootstrap -c could be smarter. On Mar 22, 2018 9:48 PM, "Chris Johns" wrote: > Hi, > > I have: > > ma

Empting libcpu ...

Hi, I have: make[6]: Entering directory '/opt/work/chris/rtems/kernel/bsps/xilinx_zynq_zedboard/arm-rtems5/c/xilinx_zynq_zedboard/lib/libcpu/arm' gmake[6]: *** No rule to make target 'all-am'. Stop. gmake[6]: Leaving directory '/opt/work/chris/rtems/kernel/bsps/xilinx_zynq_zedboard/arm-rtems5/c/

[PATCH] libcpu: Only build if there is a valid configure.ac

--- c/src/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/c/src/configure.ac b/c/src/configure.ac index 95a216334a..8d8778fc0e 100644 --- a/c/src/configure.ac +++ b/c/src/configure.ac @@ -129,7 +129,7 @@ AC_CONFIG_SUBDIRS([make]) BSP_SUBDIRS="$BSP_SUBDIRS make"

Re: [PATCH] vprintf: Add handler that mutes all output.

On 22/03/2018 18:22, Christian Mauderer wrote: > Am 22.03.2018 um 08:17 schrieb Chris Johns: >> On 22/03/2018 17:40, Christian Mauderer wrote: >>> This adds a vprintf handler that can be used to suppress all outputs of >>> the libbsd. >> >> Why would I want this? >> >> How would I enable the output

GSOC proposal - Runtime tracing

Hi! I apologise for the delay in submission. Was caught up with college project submission. PFA my proposal application for GSOC'18. I would appreciate insight and suggestions. Best, Vidushi Vashishth ​ GSOC_proposal_Vidushi_runtime_tracing

Re: file not recognized problem

Hello talos, What are you trying to compile? How did you configure and make? This error usually means the output of a previous build failed with some intermediate object file already generated, so you should 'make clean'. Gedare On Thu, Mar 22, 2018 at 12:10 AM, talos <2486580...@qq.com> wrote

Re: [PATCH] vprintf: Add handler that mutes all output.

Am 22.03.2018 um 08:17 schrieb Chris Johns: > On 22/03/2018 17:40, Christian Mauderer wrote: >> This adds a vprintf handler that can be used to suppress all outputs of >> the libbsd. > > Why would I want this? > > How would I enable the output so I could see it, for example when working with > th

Re: [PATCH] vprintf: Add handler that mutes all output.

On 22/03/2018 17:40, Christian Mauderer wrote: > This adds a vprintf handler that can be used to suppress all outputs of > the libbsd. Why would I want this? How would I enable the output so I could see it, for example when working with the code? Chris _