From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Subject: Re: cross-compiling alternatives (was Re: [PATCH 0/1] Embedded Maintainer(s)...) Date: Fri, 13 Jun 2008 20:55:44 +0200 Message-ID: <20080613185544.GB8780@uranus.ravnborg.org> References: <1209577322.25560.402.camel@pmac.infradead.org> <8bd0f97a0806120905u532ce5f9sf231e185173de791@mail.gmail.com> <200806121925.35883.rob@landley.net> <1213340652.26255.224.camel@pmac.infradead.org> <20080613100231.btmn0xgmqog884cs@localhost> <1213376457.26255.281.camel@pmac.infradead.org> <2a5b3cfbb9eccd7885735ea46b115541.squirrel@www.geekisp.com> <4852C026.8060203@am.sony.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <4852C026.8060203@am.sony.com> Sender: linux-embedded-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Tim Bird Cc: Bill Traynor , David Woodhouse , linux-embedded-owner@reliableembeddedsystems.com, Rob Landley , "Robert P. J. Day" , Mike Frysinger , Greg Ungerer , Leon Woestenberg , linux-embedded@vger.kernel.org On Fri, Jun 13, 2008 at 11:44:54AM -0700, Tim Bird wrote: > Bill Traynor wrote: > >>> Do you wanna set some breakpoints and inspect variables in makefiles? > >>> Have a look at a simple makefile debugger (written in make): > > http://www.embedded.com/columns/technicalinsights/197003517?printable=true > > The article above shows some macros you can add to your Makefile to show > you the values of certain things. It is helpful, but not an interactive > debugger. > > However, the guy who wrote that article did indeed write a full > Makefile debugger. I took it for a spin, and found that it worked as > advertised on a simple Makefile. I tried it on the kernel Makefile, but > without success (but I didn't try very hard). > > YMMV. I put some of the resources and info I found at: > http://elinux.org/Debugging_Makefiles > > The link from the package's README doesn't work, but here's a link > I found to an article about the debugger: > http://www.cmcrossroads.com/content/view/6479/120/ Quite impressive what he got out of the make features. The kernel does a few unusual tricks so I do understand why it does not work there. Speaking about the kernel... Try "make V=2" one day to see why a target are build. It is quite useful when a small change results in much more being build than you expected. But this is kernel specific and not a general feature. Sam