From: Gervais, Francois <FGervais@distech-controls.com>
To: buildroot@busybox.net
Subject: [Buildroot] [EXT] Re: [PATCH v4 5/9] boot/arm-trusted-firmware: introduce two new options
Date: Mon, 10 Feb 2020 14:30:13 +0000 [thread overview]
Message-ID: <DM6PR01MB58491DFF606B05CFFFD84A01F3190@DM6PR01MB5849.prod.exchangelabs.com> (raw)
> > two new options for arm-trusted-firmware:
> > 1. BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS
> >?????? - for additional targets, E.G. "pbl".
>
> This option was already added in commit
> 05b8c7da6de863561d66717735a4870f2766454c, which is part of Buildroot
> master.
Somebody reported a problem with my patch last week. I'm still investigating with
him but it seems that the qstrip wrapping might be required which
05b8c7da6de863561d66717735a4870f2766454c is missing.
Jerry maybe you can try on your side? You could rebase your v5 on top
of master and try to build arm-trusted-firmware from scratch with
BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS empty.
You might see this error message:
make: *** empty string invalid as file name. Stop.
next reply other threads:[~2020-02-10 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 14:30 Gervais, Francois [this message]
2020-02-10 14:42 ` [Buildroot] [EXT] Re: [PATCH v4 5/9] boot/arm-trusted-firmware: introduce two new options Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2020-02-05 10:52 [Buildroot] [PATCH v4 1/9] package/nxp: new package directory Changming Huang
2020-02-05 10:52 ` [Buildroot] [PATCH v4 5/9] boot/arm-trusted-firmware: introduce two new options Changming Huang
2020-02-05 12:29 ` Thomas Petazzoni
2020-02-07 1:21 ` [Buildroot] [EXT] " Jerry Huang
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=DM6PR01MB58491DFF606B05CFFFD84A01F3190@DM6PR01MB5849.prod.exchangelabs.com \
--to=fgervais@distech-controls.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.