From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from astoria.ccjclearline.com ([64.235.106.9]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1NBrNo-0004ha-M2 for openembedded-devel@lists.openembedded.org; Sat, 21 Nov 2009 15:56:19 +0100 Received: from cpe00142a336e11-cm001ac318e826.cpe.net.cable.rogers.com ([174.113.191.234] helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NBrMR-0004No-1m for openembedded-devel@lists.openembedded.org; Sat, 21 Nov 2009 09:54:51 -0500 Date: Sat, 21 Nov 2009 09:54:45 -0500 (EST) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost To: OpenEmbedded Development mailing list Message-ID: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - lists.openembedded.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: X-SA-Exim-Connect-IP: 64.235.106.9 X-SA-Exim-Mail-From: rpjday@crashcourse.ca X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: No (on linuxtogo.org); Unknown failure Subject: FYI, beagleboard-demo-image now builds on fedora 12 X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2009 14:56:19 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII for anyone who cares, i can now build beagleboard-demo-image from scratch on my (effectively) f12 system, so i'm happy. but it might be worth watching out for other packages that will fail because of that cpp linemarkers issue. so far, so good, though, and thanks to everyone for their patience. rday p.s. out of curiosity, if i just finished a build and *immediately* do the same build again, it appears to rerun the last 3 or 4 steps, which on this system takes *many* minutes. those steps represent, uh, rebuilding the root filesystem? if nothing's changed, why is that work being repeated? -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================