From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from plane.gmane.org ([80.91.229.3]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1TSzgA-0006Ad-Uc for ptxdist@pengutronix.de; Tue, 30 Oct 2012 01:27:40 +0100 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TSzgG-0001jn-8W for ptxdist@pengutronix.de; Tue, 30 Oct 2012 01:27:44 +0100 Received: from 208.80.102.28 ([208.80.102.28]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Oct 2012 01:27:44 +0100 Received: from steve by 208.80.102.28 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Oct 2012 01:27:44 +0100 From: Steve Schefter Date: Tue, 30 Oct 2012 00:27:24 +0000 (UTC) Message-ID: References: <20121025140956.GF23204@pengutronix.de> <20121028171315.GD22246@pengutronix.de> <20121029212653.GF22246@pengutronix.de> Mime-Version: 1.0 Subject: Re: [ptxdist] dependency issue Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Thank you Michael. Your questions lead me to see the error of my ways. It starts with the fact that, while mesalib depends on host-makedepend, it does the extract of mesalib before it does the install of host-makedepend. It just saves the further steps in building mesalib until later. The problem is that I had it run mesalib's autogen.sh during the extract. At that point, makedepend doesn't exist and mesalib's configure fails. Why did I put it as part of extract and not prepare? According to the notes I put in the mesalib.make file, I was finding with it in prepare, ptxdist was attempting to use the configure script included in the tarball (not suitable for cross compile) before autogen.sh generated a new one. Now moving it back to prepare I am not finding this to be an issue, so I am not sure what else might have been wrong at the time. Thanks again for your help and gaining a better insight into how ptxdist decides when to do what. Regards, Steve -- ptxdist mailing list ptxdist@pengutronix.de