All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <michael@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig)
Date: Fri, 7 Apr 2017 10:09:11 +0200	[thread overview]
Message-ID: <20170407080909.GB12962@panicking> (raw)
In-Reply-To: <20170407100654.32f1da84@free-electrons.com>

Hi

On Fri, Apr 07, 2017 at 10:06:54AM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 7 Apr 2017 09:54:46 +0200, Michael Trimarchi wrote:
> 
> > diff --git a/board/beaglebone/genimage.cfg b/board/beaglebone/genimage.cfg
> > index cfc1039ec..ba60297dd 100644
> > --- a/board/beaglebone/genimage.cfg
> > +++ b/board/beaglebone/genimage.cfg
> > @@ -9,7 +9,6 @@ image boot.vfat {
> >  			"am335x-evmsk.dtb",
> >  			"am335x-bone.dtb",
> >  			"am335x-boneblack.dtb",
> > -			"am335x-bonegreen.dtb",
> 
> No, we want to keep this one. Instead, we want to upgrade the kernel
> version used in beaglebone_qt5_defconfig.
> 
> Can you try replacing:
> 
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="52c4aa7cdb93d61f8008f380135beaf7b8fa6593"
> 
> by:
> 
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="adde2ca9f86797071f6e7b2b9e779fa5e4a8f3cd"
>

Yes ok
 
> in beaglebone_qt5_defconfig.
> 
> I'm adding Lothar in Cc as well, since he did the
> beaglebone_qt5_defconfig, and he will know if the SGX stuff works fine
> with the 4.4 TI kernel.
> 
> 
> > 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

Michael

> 
> Why is this needed?
> 
> Thanks!
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

-- 
| Michael Nazzareno Trimarchi                     Amarula Solutions BV |
| COO  -  Founder                                      Cruquiuskade 47 |
| +31(0)851119172                                 Amsterdam 1018 AM NL |
|                  [`as] http://www.amarulasolutions.com               |

  reply	other threads:[~2017-04-07  8:09 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 [this message]
2017-04-07  8:19               ` Thomas Petazzoni
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=20170407080909.GB12962@panicking \
    --to=michael@amarulasolutions.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.