From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig)
Date: Fri, 7 Apr 2017 10:19:10 +0200 [thread overview]
Message-ID: <20170407101910.57e2a19d@free-electrons.com> (raw)
In-Reply-To: <20170407080909.GB12962@panicking>
Hello,
On Fri, 7 Apr 2017 10:09:11 +0200, Michael Trimarchi wrote:
> > > diff --git a/boot/uboot/uboot.mk b/boot/uboot/uboot.mk
> > > index 1d464d967..edfc27fa7 100644
> > > --- a/boot/uboot/uboot.mk
> > > +++ b/boot/uboot/uboot.mk
> > > @@ -195,8 +195,9 @@ endef
> > > endif # BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
> > >
> > > define UBOOT_BUILD_CMDS
> > > - $(if $(BR2_TARGET_UBOOT_CUSTOM_DTS_PATH),
> > > - cp -f $(call qstrip,$(BR2_TARGET_UBOOT_CUSTOM_DTS_PATH)) $(@D)/arch/$(UBOOT_ARCH)/dts/
> > > + UBOOT_CUSTOM_DTS_PATH=$(call qstrip,$(BR2_TARGET_UBOOT_CUSTOM_DTS_PATH))
> > > + $(if $(UBOOT_CUSTOM_DTS_PATH),
> > > + cp -f $(UBOOT_CUSTOM_DTS_PATH) $(@D)/arch/$(UBOOT_ARCH)/dts/
> > > )
>
> My error was cp -f with just one parameter. Test pass and cp -f fail
Ah, yes, obviously. Though it would be nicer to define
UBOOT_CUSTOM_DTS_PATH outside of UBOOT_BUILD_CMDS.
Could you send a separate patch, fixing just that?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-07 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 10:57 [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig) Arnout Vandecappelle
2017-04-06 11:47 ` Peter Seiderer
2017-04-06 16:12 ` Michael Nazzareno Trimarchi
2017-04-06 16:32 ` Thomas Petazzoni
2017-04-06 16:57 ` Thomas Petazzoni
2017-04-07 7:54 ` Michael Trimarchi
2017-04-07 8:06 ` Thomas Petazzoni
2017-04-07 8:09 ` Michael Trimarchi
2017-04-07 8:19 ` Thomas Petazzoni [this message]
2017-04-06 21:27 ` txt.file
2017-04-07 7:28 ` Michael Nazzareno Trimarchi
2017-04-06 16:33 ` Thomas Petazzoni
2017-04-07 18:47 ` Peter Seiderer
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=20170407101910.57e2a19d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox