[meta-xilinx] Yocto for ZYBO: various build problems

[Nathan Rossi]

On 14 December 2017 at 00:42, Robert Szafarczyk <robertsaf94 at gmail.com> wrote:
> Hello,
>
> i am trying to get Yocto working on a ZYBO board. Unfortunately i face many
> errors, which i am pretty confused about.
> Let me guide you through them:
>
> I started  with a clean-state Ubuntu 17 distro. I matched all the
> requirements and tried to build the morty/pyro versions - it failed.
> Upon realizing that Ubuntu17 was not supperted yet, i got myself Ubuntu
> 16.04 LTS, and started trying to build the pyro version of Yocto.
> At first i recieved a parsing error, which i fixed using this aproach:
> https://github.com/Xilinx/meta-xilinx/commit/07783c3cea24768ffc08d9102de6ae0c666a841e

I had backported that commit to pyro a month ago. Seems
github.com/Xilinx/meta-xilinx is out of sync. Manju could you sync it
up please, thanks.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/commit/?h=pyro&id=b6462e55e65b44afed4b7a4e8b2af3381c961110

> After that,  i was able to build the pyro version and get the image for the
> board.
> After trying to boot i  encountered another problem  which i fixed with the
> following:
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-June/003011.html
> (the problem was bassically the same as described in this mailing). Now i am

That email describes two issues, was the problem the uenv.txt content
or the slow mmc needing rescan out of curiosity?

> trying to build the thing again, but somehow Ubuntu is logging out at the
> 3297 which packaging the boost library.

I have not seen that issue myself. However it is likely unrelated to
Zynq or the meta-xilinx layer (since there is no special config for
boost in the layer or for the target).

Since it's logging you out it might be related to user
process/resource limits being reached? Try to gather more information
about the issue if you can. Also if possible search the log files in
the boost workdir, since you see do_package as the task that causes
the logout look at the log.do_package first.

You should post on the oe-core or yocto mailings lists about this
specific issue, its likely someone else has hit the same problem since
you are using a common host and targeting a common architecture (arm).

Regards,
Nathan

>
> Do you have any Idea what i might be doing wrong, faceing so many problems?
> Is there some newcomer msitake i might be doing in genereal?
>
> Maybe you can help me out somehow,
> Robert
>
> --
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>