devel Digest, Vol 49, Issue 57

Fri Dec 25 13:25:19 UTC 2015

On Mon, Dec 21, 2015 at 6:33 AM,  <devel-request at rtems.org> wrote:
> Send devel mailing list submissions to
>         devel at rtems.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.rtems.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         devel-request at rtems.org
>
> You can reach the person managing the list at
>         devel-owner at rtems.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>    1. Re: [PATCH] Chase Newlib sys/select.h changes (Nick Withers)
>    2. Re: ubuntu 15.04 build fail (Chris Johns)
>    3. Re: RTEMS User Level Tracing? (Chris Johns)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Dec 2015 10:45:42 +1100
> From: Nick Withers <nick.withers at anu.edu.au>
> To: Sebastian Huber <sebastian.huber at embedded-brains.de>,
>         <devel at rtems.org>
> Subject: Re: [PATCH] Chase Newlib sys/select.h changes
> Message-ID: <1450655142.1019.126.camel at anu.edu.au>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Sebastian,
>
> Here's an updated patch.
>
> On Tue, 2015-12-15 at 09:13 +0100, Sebastian Huber wrote:
>> Hello Nick,
>>
>> I checked in the shell changes separately. With them I can build the
>> latest Newlib with --disable-networking. It should be sufficient to
>> remove the <sys/select.h> from libnetworking.
>
> Now that Newlib's reverted the inclusion of sys/select.h in
> sys/types.h, it's largely the same as the previous version, minus the
> bits you've committed separately.
>
> Would you be able to test with libbsd?
>
>> On 14/12/15 10:09, Sebastian Huber wrote:
>> > Hello Nick,
>> >
>> > this patch needs an update once this is committed to Newlib:
>> >
>> > https://sourceware.org/ml/newlib/2015/msg00905.html
>> >
>> > On 10/12/15 10:04, Nick Withers wrote:
>> > > Hi all,
>> > >
>> > > Attached is a patch for master similar to that I posted to the
>> > > Newlib
>> > > mailing list in
>> > > https://sourceware.org/ml/newlib/2015/msg00888.html *.
>> > >
>> > > It chases Newlib changes to sys/types.h / sys/select.h and allows
>> > > us to
>> > > use Newlib's sys/select.h directly rather than rolling our own.
>> > >
>> > > A few notes:
>> > >   - I removed the BSD advertising clause from what's now
>> > > sys/selinfo.h,
>> > > but am not sure that I should have
>> > >   - I made a few not-really-related but minor changes to
>> > > cpukit/libmisc/shell/*.c printf()s to ensure format specifiers
>> > > matched
>> > > parameter types
>> > >   - the sys/selinfo.h file doesn't directly correspond to any
>> > > FreeBSD
>> > > revision, though it's basically the same as
>> > > https://svnweb.freebsd.org/
>> > > base/head/sys/sys/selinfo.h?revision=70650&view=markup , not sure
>> > > how
>> > > fussed we are with e.g., $FreeBSD$ tags and such...?
>> > >
>> > > * It doesn't mess with disabling dl tests on PSim; I ran into
>> > > troubles
>> > > with dl02 which I'll look into separately
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: sys_select.v2.patch
> Type: text/x-patch
> Size: 11877 bytes
> Desc: not available
> URL: <http://lists.rtems.org/pipermail/devel/attachments/20151221/17bb4eab/attachment-0001.bin>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 21 Dec 2015 11:03:28 +1100
> From: Chris Johns <chrisj at rtems.org>
> To: punit vara <punitvara at gmail.com>, devel at rtems.org
> Subject: Re: ubuntu 15.04 build fail
> Message-ID: <567741D0.5070900 at rtems.org>
> Content-Type: text/plain; charset=windows-1252
>
> On 18/12/2015 5:49 PM, punit vara wrote:
>> checking for python... /usr/local/bin/python
>> checking for python2.7... no
>> configure: error: python is missing or unusable
>> Makefile:8643: recipe for target 'configure-gdb' failed
>> make[1]: *** [configure-gdb] Error 1
>> make[1]: Leaving directory
>> '/home/punit/development/rtems/rsb/rtems-source-builder/rtems/build/arm-rtems4.11-gdb-7.9-x86_64-linux-gnu-1/build'
>> make: *** [all] Error 2
>> Makefile:836: recipe for target 'all' failed
>> shell cmd failed: /bin/sh -ex
>> /home/punit/development/rtems/rsb/rtems-source-builder/rtems/build/arm-rtems4.11-gdb-7.9-x86_64-linux-gnu-1/doit
>> error: building arm-rtems4.11-gdb-7.9-x86_64-linux-gnu-1
>>
>> I do not know why I am facing this build error.
>>
>> I have checked $python --version
>>
>> it is Python 2.7.10
>>
>> I have also installed $sudo apt-get install python-all-dev
>>
>
> Did you install the packages are listed in the doco:
>
>  https://docs.rtems.org/rsb/#_ubuntu
>
> Chris
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 21 Dec 2015 12:02:51 +1100
> From: Chris Johns <chrisj at rtems.org>
> To: devel at rtems.org
> Subject: Re: RTEMS User Level Tracing?
> Message-ID: <56774FBB.9010802 at rtems.org>
> Content-Type: text/plain; charset=windows-1252
>
> On 19/12/2015 6:36 AM, isaac.gutekunst wrote:
>>
>> We're interested in trace some application data in our RTEMS project.
>> Here's a bunch of background and thoughts:
>>
>> I've read the following pages:
>>     * https://devel.rtems.org/wiki/Developer/Tracing
>>     * https://devel.rtems.org/wiki/Developer/Tracing/Trace_Linker
>>
>> I think I have an understanding of the current system as documented.
>> Tracing user defined data types seems to be missing. I'm looking for
>> something more like barectf. Is there any such support available, or any
>> plans to support it? I don't want to reinvent the wheel.
>
> User defined data is not directly support but can be added if you add a
> custom generator. There is not a great deal of documentation about how
> to do this. An example generator is:
>
>  https://git.rtems.org/rtems-tools/tree/linkers/rtld-trace-buffer.ini
>
> You could add anything specific you want. It is not a great solution but
> tracing into data being passed by pointers is difficult.
>
> You would need to use the various options to get a copy of the trace
> wrapper file and then get the generator to see the headers and various
> data you want.
>
>> If there isn't support already, maybe some parts of the trace
>> infrastructure can be reused, notably the backed for storing the data,
>> and/or sending it out over the network. Are there plans to make the
>> Trace Linker natively output CTF data?
>
> We would like to support CTF output. Getting this done would need
> developer funding.
>
>> Perhaps barectf could be used for this purpose.
>
> I do not know what this. Do you have a reference?
>
> Chris
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
> ------------------------------
>
> End of devel Digest, Vol 49, Issue 57
> *************************************

I have installed https://docs.rtems.org/rsb/#_ubuntu

I have seen some one has same ubuntu fail problem in ubuntu 15.10  I
have read in this link
https://devel.rtems.org/wiki/GCI/Coding/HelloWorld
Do I know How he solve the problem ?