From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8019FE00C39; Fri, 28 Aug 2015 03:00:12 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.119 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx3.mail.bg (mx3.mail.bg [193.201.172.119]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 952FEE00BB3 for ; Fri, 28 Aug 2015 03:00:09 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx3.mail.bg (Postfix) with ESMTPSA id 4CBA2203E464; Fri, 28 Aug 2015 13:00:06 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1440756007; bh=LX7KJUMQj9Yn1uF54GHHCGhrxqXy8TIb+gVrJ4AZrQw=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=IpDkSJmnhy2LcWzBxlOWu/mT56+ZGrOseiWYNuqHqJ/HtyfpRyv61MHq+GR3NkmOB qs1aq+6VGCWztZ4C97+VcwL8UwgBCDe+ZYGD8ATM5VuDGGJXbVC0QkhBh0g5Sgy3Rw WVM2O/wZAfxDk1pxI+vBKEZjjJ1pLVZUAhEJfopk= Message-ID: <55E03126.1000107@mail.bg> Date: Fri, 28 Aug 2015 13:00:06 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Terry Farnham References: <001301d0e062$6b04fc10$410ef430$@quanergy.com> <001d01d0e0cb$472e8b80$d58ba280$@quanergy.com> <000601d0e152$852581a0$8f7084e0$@quanergy.com> In-Reply-To: <000601d0e152$852581a0$8f7084e0$@quanergy.com> Cc: meta-freescale@yoctoproject.org Subject: Re: Help - new to Yocto X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2015 10:00:12 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hi Terry, On 08/28/2015 08:29 AM, Terry Farnham wrote: > I attempted a clean build today to see if I could get past this > issue. I am still encountering the same compile problem. > > I’m not exactly sure where I must be going wrong with the steps for > setting up to build OE and the Yocto packages, but it always seems to > fail to build the ptpd daemon. Looking at the Makefiles that are > generated, it seems to me that the mechanics which sets up the > compiler include directives are generating an include reference into > the host machines /usr/include folder rather than into the proper arm > version of the includes. I attached the Makefile from my > "/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/build" > folder. You can see that the includedir seems to improperly > reference /usr/include. The error that gets generated is a result of > including from nested includes that eventually land on > /usr/include/bits/byteswap.h which happens to have x86 specific > assembler in it. I’m surprised that I am not seeing more compile > errors than this, as I suspect that a lot of the code being compiled > from the cortexa9hf-vfp-neon-poky-linux-gnueabi is referencing into > the host machines /usr/include instead of the hardware specific > version. > > I'm hoping someone has a clue that will help me get past this > problem. > > Thanks, > > Terry Just tried to build ptpd on a Debian 7 host and it works like a charm. Here's what I'm doing: // Get Yocto mkdir ~/yocto-master cd ~/yocto-master repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b fido repo sync . setup-environment build // Change PACKAGE_CLASSES to package_ipk to avoid waiting for RPMs nano conf/local.conf // Add meta-networking and meta-python to BBLAYERS nano conf/bblayers.conf // Default MACHINE is imx6qsabresd, so no need to set it explicitly bitbake ptpd This worked on both master and fido branches. Regards, Nikolay