[rtems-libbsd] Building for zynq?

[Jonathan Brandmeyer]

Thanks.  My toolchain was a few months old, and its update is proceeding.
I began the update with a simple git pull followed by re-running the
sb-set-builder program, which is continuing to run as I write this.
However, I did not explicitly clean the build or start from a fresh git
checkout of the rtems-source-builder.  Will the sb-set-builder tool do The
Right Thing in the "recursive make considered harmful" sense with regard to
dependency tracking?

Phrased differently, is supporting an in-place update an explicitly
supported usage mode for sb-set-builder, or am I expected to start over
from scratch on a new build?

Thanks,
Jonathan Brandmeyer


On Tue, Apr 28, 2015 at 8:18 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello Jonathan,
>
> you need the latest tools (Newlib in particular must be the up to date) to
> build the libbsd. The Xilinx Zynq is supported.
>
> ----- Jonathan Brandmeyer <jonathan.brandmeyer at gmail.com> schrieb:
> >
> I'm trying to build rtems-libbsd targeting xilinx_zynq_zedboard and/or
> xilinx_zynq_qemu in order to test out networking with libbsd.  At least two
> files/types related to time are missing:
>
> rtemsbsd/include/rtems/bsd/sys/resource.h includes <sys/_timeval.h> which
> is not present in RTEMS, my BSP, or libbsd.  Numerous files then reference
> sys/resource.h
>
>
> freebsd/sys/opencrypto/cryptodev.h requests 'struct bintime' to be a
> member, which is an incomplete type.  Again, this type is not provided by
> RTEMS, my BSP, or libbsd.
>
> Does libbsd work for the ARM Xilinx targets, and if so, what can I do
> about libbsd's sense of time?
>
> Thanks,
> Jonathan Brandmeyer
>
>
> --
>
> 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.huber at embedded-brains.de <http://lists.rtems.org/mailman/listinfo/devel>
> PGP     : Public key available on request.
>
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20150428/c991bbaa/attachment-0002.html>