[meta-freescale] Help - new to Yocto

Daiane Angolini daiane.list at gmail.com
Fri Aug 28 05:30:04 PDT 2015


On Fri, Aug 28, 2015 at 2:29 AM, Terry Farnham
<terry.farnham at quanergy.com> 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 "<build_folder>/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.

Have you tried to use the latest meta-oe layer as I said before?

You are using freescale release manifest. It is a stuck in time
manifest for every layer. What you've being built is not the same
Nicolay has built. So, please, try to use latest poky/meta-oe folder.

Or remove ptpd if you don't need it

Daiane
>
> Thanks,
>
> Terry
>
> -----Original Message-----
> From: angolini at gmail.com [mailto:angolini at gmail.com] On Behalf Of Daiane Angolini
> Sent: Thursday, August 27, 2015 9:15 AM
> To: Terry Farnham
> Cc: meta-freescale at yoctoproject.org
> Subject: Re: [meta-freescale] Help - new to Yocto
>
> On Thu, Aug 27, 2015 at 10:21 AM, Terry Farnham <terry.farnham at quanergy.com> wrote:
>> Thank you Daiane,
>>
>> I am assuming that the version name/number you are referring to is actually the name of the branch manifest that I pulled from using repo?  I am using imx-3.14.28-1.0.0_ga.
>>
>
> Yes
>
> Daiane
>> Thank you for your time.
>>
>> Terry
>>
>> -----Original Message-----
>> From: angolini at gmail.com [mailto:angolini at gmail.com] On Behalf Of
>> Daiane Angolini
>> Sent: Thursday, August 27, 2015 4:46 AM
>> To: Terry Farnham
>> Cc: meta-freescale at yoctoproject.org
>> Subject: Re: [meta-freescale] Help - new to Yocto
>>
>> On Wed, Aug 26, 2015 at 9:50 PM, Terry Farnham <terry.farnham at quanergy.com> wrote:
>>> Hello,
>>>
>>>
>>>
>>> Disclaimer:  I am totally new to Yocto as well as Linux development.
>>> So please bear with my ignorance.
>>
>> There are two important things you must know before anything else:
>>
>> 1 - http://freescale.github.io/doc/release-notes/1.8/
>> 2- when reporting error on Freescale Release, it's absolutely
>> important to know the release version name/number
>>
>> This error may be already fixed upstream, you can try to upgrade the original layer.
>>
>> Daiane
>>
>>>
>>>
>>>
>>> I am attempting to build from scratch a generic kernel image for the
>>> imx6qsabresd.  I have followed a number of steps in getting setup to
>>> build properly.  However after executing the final two steps:
>>>
>>>> MACHINE=imx6qsabresd source fsl-setup-release.sh –b build –e fb
>>>
>>>> bitbake fsl-image-gui
>>>
>>>
>>>
>>> I am getting a single compile error which I include after my
>>> signature.  The most pertinent information, however, seems to be the
>>> warning where it indicates that it is unsafe to use the “/usr/include” include location.
>>> This does indeed seem bad since I am on an x86 machine compiling for
>>> arm.  I am, however, totally oblivious as to why it would be looking
>>> in /usr/include for any include files.  Please Help, as I am clueless
>>> and I really need to figure out the basic build process before I move
>>> forward on more advanced setups.
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Terry Farnham
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> | cc1: warning: include location "/usr/include" is unsafe for
>>> cross-compilation [-Wpoison-system-directories]
>>>
>>> | In file included from /usr/include/bits/byteswap.h:35:0,
>>>
>>> |                  from /usr/include/endian.h:60,
>>>
>>> |                  from /usr/include/bits/waitstatus.h:64,
>>>
>>> |                  from /usr/include/stdlib.h:42,
>>>
>>> |                  from
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-pok
>>> y -linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/ptpd.h:40,
>>>
>>> |                  from
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/bmc.c:54:
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/bmc.c:
>>> In function 'initData':
>>>
>>> | /usr/include/bits/byteswap-16.h:31:5: error: invalid 'asm': invalid
>>> operand for code 'w'
>>>
>>> |      __asm__ ("rorw $8, %w0"           \
>>>
>>> |      ^
>>>
>>> | /usr/include/netinet/in.h:403:21: note: in expansion of macro '__bswap_16'
>>>
>>> |  #   define htons(x) __bswap_16 (x)
>>>
>>> |                      ^
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/bmc.c:83:21:
>>> note: in expansion of macro 'htons'
>>>
>>> |       uint16_t pid = htons(getpid());
>>>
>>> |                      ^
>>>
>>> | {standard input}: Assembler messages:
>>>
>>> | {standard input}:397: Error: bad instruction `rorw $8,'
>>>
>>> | make[2]: *** [bmc.o] Error 1
>>>
>>> | make[2]: *** Waiting for unfinished jobs....
>>>
>>> | In file included from /usr/include/bits/byteswap.h:35:0,
>>>
>>> |                  from /usr/include/endian.h:60,
>>>
>>> |                  from /usr/include/bits/waitstatus.h:64,
>>>
>>> |                  from /usr/include/stdlib.h:42,
>>>
>>> |                  from
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-pok
>>> y
>>> -linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/../ptpd.h:40,
>>>
>>> |                  from
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/msg.c:54:
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/msg.c:
>>> In function 'packEnumeration16':
>>>
>>> | /usr/include/bits/byteswap-16.h:31:5: error: invalid 'asm': invalid
>>> operand for code 'w'
>>>
>>> |      __asm__ ("rorw $8, %w0"           \
>>>
>>> |      ^
>>>
>>> | /usr/include/netinet/in.h:403:21: note: in expansion of macro '__bswap_16'
>>>
>>> |  #   define htons(x) __bswap_16 (x)
>>>
>>> |                      ^
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/../dep/ptpd_dep.h:120:19:
>>> note: in expansion of macro 'htons'
>>>
>>> |  #define flip16(x) htons(x)
>>>
>>> |                    ^
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/msg.c:71:16:
>>> note: in expansion of macro 'flip16'
>>>
>>> |   *(type *)to = flip##size( *(type *)from ); \
>>>
>>> |                 ^
>>>
>>> |
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/ptpd-2.3.1-rc2/src/dep/msg.c:107:1:
>>> note: in expansion of macro 'PACK_ENDIAN'
>>>
>>> |  PACK_ENDIAN( Enumeration16, 16 )
>>>
>>> |  ^
>>>
>>> | {standard input}: Assembler messages:
>>>
>>> | {standard input}:235: Error: bad instruction `rorw $8,'
>>>
>>> | make[2]: *** [dep/msg.o] Error 1
>>>
>>> | make[2]: Leaving directory
>>> `/home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/build/src'
>>>
>>> | make[1]: *** [all-recursive] Error 1
>>>
>>> | make[1]: Leaving directory
>>> `/home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/ptpd/2.3.1-rc2-r0/build'
>>>
>>> | make: *** [all] Error 2
>>>
>>> | ERROR: oe_runmake failed
>>>
>>> | WARNING: exit code 1 from a shell command.
>>>
>>> | ERROR: Function failed: do_compile (log file is located at
>>> /home/tfarnham/fsl-release-bsp/build/tmp/work/cortexa9hf-vfp-neon-pok
>>> y
>>> -linux-gnueabi/ptpd/2.3.1-rc2-r0/temp/log.do_compile.29823)
>>>
>>> ERROR: Task 1658
>>> (/home/tfarnham/fsl-release-bsp/sources/meta-openembedded/meta-networ
>>> k ing/recipes-daemons/ptpd/ptpd_2.3.1-rc2.bb,
>>> do_compile) failed with exit code '1'
>>>
>>> NOTE: Tasks Summary: Attempted 2447 tasks of which 2444 didn't need
>>> to be rerun and 1 failed.
>>>
>>> Waiting for 0 running tasks to finish:
>>>
>>>
>>>
>>> Summary: 1 task failed:
>>>
>>>
>>> /home/tfarnham/fsl-release-bsp/sources/meta-openembedded/meta-network
>>> i ng/recipes-daemons/ptpd/ptpd_2.3.1-rc2.bb,
>>> do_compile
>>>
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> _______________________________________________
>>> meta-freescale mailing list
>>> meta-freescale at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>>
>>


More information about the meta-freescale mailing list