From: Henning Schild <henning.schild@siemens.com>
To: "[ext] sven.schultschik@siemens.com" <sven.schultschik@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: trouble creating recipe for TF-A with dpkg
Date: Mon, 24 Feb 2020 17:34:49 +0100 [thread overview]
Message-ID: <20200224173449.5d793bdf@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM0PR10MB2289F6166EF00B6BE1B47D0B90EC0@AM0PR10MB2289.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
Hi,
not sure whether that solves your problem ... but there are working
recipes out there ...
https://github.com/siemens/jailhouse-images/tree/master/recipes-bsp/arm-trusted-firmware
Henning
On Mon, 24 Feb 2020 16:17:07 +0000
"[ext] sven.schultschik@siemens.com" <sven.schultschik@siemens.com>
wrote:
> Hi all,
>
>
>
> does someone managed to build TF-A with ISAR dpkg recipe?
> https://github.com/ARM-software/arm-trusted-firmware/blob/master/Makefile
>
>
>
> with the make XXXXX command I can build the binary, but I didn't get
> it to run with dpkg-buildpackage.
>
>
>
> I always get linker errors about "unknown -Wl,-z,-relro" parameter,
> but if I change DEB_BUILD_MAINT_OPTIONS to hardening=-relro I get
> errors about "undefinde reference to stack_chk_guard"
>
>
>
> Does someone have an example recipe setup for build TF-A?
>
>
>
> Thank you
>
> With best regards,
> Sven Angelo Schultschik
>
> Siemens AG
> Digital Industries
> Process Automation
> Software House Khe
> DI PA CI R&D 2
> Oestliche Rheinbrueckenstr. 50
> 76187 Karlsruhe, Germany
> Tel.: +49 721 595-2827
> <mailto:sven.schultschik@siemens.com>
> mailto:sven.schultschik@siemens.com
> <https://siemens.com/ingenuityforlife>
> www.siemens.com/ingenuityforlife
>
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim
> Hagemann Snabe; Managing Board: Joe Kaeser, Chairman, President and
> Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich,
> Cedrik Neike, Michael Sen, Ralf P. Thomas; Registered offices: Berlin
> and Munich, Germany; Commercial registries: Berlin Charlottenburg,
> HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
>
> Important notice: This e-mail and any attachment thereof contain
> corporate proprietary information. If you have received it by
> mistake, please notify us immediately by reply e-mail and delete this
> e-mail and its attachments from your system. Thank you.
>
>
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6562 bytes --]
next prev parent reply other threads:[~2020-02-24 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 16:17 sven.schultschik
2020-02-24 16:34 ` Henning Schild [this message]
2020-02-24 16:46 ` AW: " sven.schultschik
2020-02-24 16:35 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200224173449.5d793bdf@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=sven.schultschik@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox