From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from dude02.hi.pengutronix.de ([2001:67c:670:100:1d::28]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSEnR-0005uP-U2 for ptxdist@pengutronix.de; Tue, 13 Oct 2020 09:32:33 +0200 Received: from mol by dude02.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1kSEnR-00070F-L2 for ptxdist@pengutronix.de; Tue, 13 Oct 2020 09:32:33 +0200 Date: Tue, 13 Oct 2020 09:32:33 +0200 From: Michael Olbrich Message-ID: <20201013073233.GC3084@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] BUG: problem with barebox build: barebox_partitions.config List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de On Mon, Oct 12, 2020 at 01:37:45PM +0200, Enrico Weigelt, metux IT consult wrote: > I've stumpled across a really strange problem on building barebox build > (distrokit): > [...] > '/home/nekrad/src/dk/DistroKit/local_src/barebox.x86_64' > /opt/ptxdist/lib/ptxdist-2020.09.0/rules/barebox.make:216: recipe for > target > '/opt/ptxdist/lib/ptxdist-2020.09.0/config/images/barebox_partitions.config' > failed > make: *** > [/opt/ptxdist/lib/ptxdist-2020.09.0/config/images/barebox_partitions.config] > Error 2 > > > > Further debugging turned out it's trying to rebuild > > > /opt/ptxdist/lib/ptxdist-2020.09.0/config/images/barebox_partitions.config > > via world/kconfig call, which obviously should never happen. > The call is done from .../rules/barebox.make. > > > barebox_%config: $(STATEDIR)/barebox.extract > > This line makes the barebox_partitions.config file (coming from ptxdist > itself) dependent on the source extraction state file. Adding an > explicit no-op rule for that specific file (hardcoded full pathname) > makes the problem go away. > > I'm not quite sure how this rule really supposed to wor, but it looks > like the pattern is too wide. > > Any suggestion how to fix that in a clean way ? This should be fixed in ptxdist-2020.10.0 with the commit 7fa9235fb915e537d21054dc6a60af6981969ba5 ("kernel, barebox: use explicit list of config targets") Regards, Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de