Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Florent AUMAITRE <florent.aumaitre@medianesysteme.com>
Cc: Peter Seiderer <ps.report@gmx.net>,
	Julien Corjon <corjon.j@ecagroup.com>,
	Naumann Andreas <ANaumann@ultratronik.de>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/qt5: fix parallel build qmake package (qt5) doesn't build when using parallel build.
Date: Sun, 26 Dec 2021 23:50:13 +0100	[thread overview]
Message-ID: <20211226235013.22faad2e@windsurf> (raw)
In-Reply-To: <FAABCD35A3EE5E419EC2DCD8792107CABC6F998E@ikhexmbxc02n01.ikhex.ikoula.com>

Hello Florent,

On Thu, 16 Dec 2021 09:25:19 +0000
Florent AUMAITRE <florent.aumaitre@medianesysteme.com> wrote:

> > Which failure? Does it happen with per-package enabled or without (would like
> > to avoid the forced MAKE1 for all qt packages install) too? In case it happens
> > with per-package disabled it should go to an extra patch...  
> 
> I observe a race condition with some install target
> 2021-11-04T12:43:36 Makefile:886: recipe for target 'install_do_install_qmltypes' failed
> 2021-11-04T12:43:36 Makefile:400: recipe for target 'sub-wavefrontmesh-install_subtargets' failed
> 2021-11-04T12:43:36 make[4]: *** [sub-wavefrontmesh-install_subtargets] Error 2
> 2021-11-04T12:43:36 make[4]: *** Waiting for unfinished jobs...
> 
> Qt5declarative generated makefile (qt5declarative-5.15.2/src/imports/wavefrontmesh/Makefile) install twice /usr/qml/Qt/labs/wavefrontmesh/plugins.qmltypes in target install_qmlfiles and install_do_install_qmltypes.

Could you specify whether this happens with BR2_PER_PACKAGE_DIRECTORIES
enabled or disabled? Also, do you have an example Buildroot
configuration that exhibits this problem?

According to http://autobuild.buildroot.net/?reason=qt5declarative%
there are only 3 "recent" failures of qt5declarative-5.15.2 and they
are not what you're pointing.

We unfortunately can't "blindly" apply a workaround for a problem that
isn't "visible".

However, your commit seems to mix up the $(MAKE) -> $(MAKE1) change
with those PKG_QMAKE_FIXUP_ABSOLUTE_PATH and QT5BASE_CMAKECONFIG_FIXUP
macros which are not explained in the commit log. Could you give more
details?

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-26 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  7:51 [Buildroot] [PATCH 1/1] package/qt5: fix parallel build qmake package (qt5) doesn't build when using parallel build Florent AUMAITRE
2021-12-15 22:28 ` Peter Seiderer
2021-12-16  8:51   ` Andreas Naumann
2021-12-16  9:25   ` Florent AUMAITRE
2021-12-26 22:50     ` Thomas Petazzoni [this message]
2022-01-03 16:36       ` Florent AUMAITRE

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=20211226235013.22faad2e@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=ANaumann@ultratronik.de \
    --cc=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=florent.aumaitre@medianesysteme.com \
    --cc=ps.report@gmx.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