[meta-ti] bitbake of syslink fails
Koen Kooi
koen at dominion.thruhere.net
Thu Feb 23 13:42:57 PST 2012
Op 23 feb. 2012, om 22:27 heeft Monk, Roger het volgende geschreven:
> On 23 Feb 2012, at 21:22, "Brian Hutchinson" <b.hutchman at gmail.com> wrote:
>
>> Hi,
>>
>> Hopefully this is the appropriate place to ask this ... I'm trying to
>> build syslink in meta-ti with Angstrom/OE Core.
>>
>> I've downloaded ti_cgt_tms470_4.6.6_setup_linux_x86.bin and
>> ti_cgt_c6000_7.2.7_setup_linux_x86.bin and placed this in my
>> source/downloads directory.
>>
>> When I do a bitbake ti-syslink I get lots of messages like these:
>>
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/csignal
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/numeric
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/ostream
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/xlocnum
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/stdiostream.h
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/xstddef
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/stdexcept
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/iosfwd
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/cfloat
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/cpp_inline_math.h
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/stdlib.h
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/clocale
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/fstream
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/ciso646
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/Std_Types.h
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/iterator
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/strstream.h
>> WARNING: /usr/share/ti/ti-cgt470-tree/include/ios
>> ERROR: runstrip: ''arm-angstrom-linux-gnueabi-strip'
>> --remove-section=.comment --remove-section=.note
>> '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/ti-cgt6x-1_7_2_7-r4/package/usr/share/ti/ti-cgt6x-tree/bin/lnk6x''
>> strip command failed
>> ERROR: runstrip: ''arm-angstrom-linux-gnueabi-strip'
>> --remove-section=.comment --remove-section=.note
>> '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/ti-cgt6x-1_7_2_7-r4/package/usr/share/ti/ti-cgt6x-tree/bin/clist6x''
>> strip command failed
>> ERROR: runstrip: ''arm-angstrom-linux-gnueabi-strip'
>> --remove-section=.comment --remove-section=.note
>> '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/ti-cgt6x-1_7_2_7-r4/package/usr/share/ti/ti-cgt6x-tree/bin/abs6x''
>> strip command failed
>> ERROR: runstrip: ''arm-angstrom-linux-gnueabi-strip'
>> --remove-section=.comment --remove-section=.note
>> '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/ti-cgt6x-1_7_2_7-r4/package/usr/share/ti/ti-cgt6x-tree/bin/cmp6x''
>> strip command failed
>>
>>
>>
>>
>> .. and these go on for a while and then the build fails with this context below:
>>
>>
>>
>> NOTE: package ti-syslink-2_00_00_78-r115a: task do_prepsources: Started
>> ERROR: Function failed: do_prepsources (see
>> /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/ti-syslink-2_00_00_78-r115a/temp/log.do_prepsources.28692
>> for further information)
>> ERROR: Logfile of failure stored in:
>> /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/ti-syslink-2_00_00_78-r115a/temp/log.do_prepsources.28692
>> Log data follows:
>> | + cd /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/ti-syslink-2_00_00_78-r115a/syslink_2_00_00_78
>> | + do_prepsources
>> | + cd /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/ti-syslink-2_00_00_78-r115a/syslink_2_00_00_78/packages//ti/syslink
>> | + /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-xdctools-tree/xdc
>> --jobs=12 .make -PR .
>> | making .make: Thu Feb 23 14:25:57 EST 2012 ...
>> | ======== .make [./buildutils/rtos/buildScripts] ========
>> | ======== .make [./family/rtos/bios6/ti814x] ========
>> | ======== .make [./ipc/rtos] ========
>> | ======== .make [.] ========
>> | ======== .make [./ipc/rtos/interfaces] ========
>> | ======== .make [./ipc/rtos/shMem] ========
>> | ======== .make [./ipc/rtos/syslinkMemMgr] ========
>> | ======== .make [./ipc/rtos/syslinkMemMgr/shMemMgr] ========
>> | ======== .make [./ipc/rtos/syslinkMemMgr/tilerMemMgr] ========
>> | ======== .make [./ipc/rtos/syslinkMemMgr/nullMemMgr] ========
>> | ======== .make [./procMgr/rtos/bios6] ========
>> | ======== .make [./samples/hlos/tilerDaemon] ========
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of
>> /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-xdctools-tree/packages/xdc/bld/bld.js)
>> ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package
>> path.Warning: no config.bld file was found along the package path.
>> |
>> | The config.bld file specifies the location of the
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> compiler tool-chains required to compile runtime content.
>> |
>> | Without this file, the XDC tools assume no targets are to
>> be Without this file, the XDC tools assume no targets are to
>> be
>> |
>> | used. used.
>> |
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.Warning: no config.bld file was found along the package path.
>> |
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to
>> beWarning: no config.bld file was found along the package path.
>> | used.
>> |
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | js: "./package.bld", line 76: xdc.services.global.XDCException:
>> xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.syslink.ipc' along
>> the path: '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-ipc-tree/packages;/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-sysbios-tree/packages;/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-xdctools-tree/packages;../../../../..;'.
>> Ensure that the package path is set correctly.
>> | make[1]: *** Deleting file `package.mak'
>> | making package.mak (because of package.bld) ...
>> | makefiles are up to date.
>> | ======== .make [./samples/rtos/frameq] ========
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | ======== .make [./samples/rtos/heapBufMP] ========
>> | ======== .make [./samples/rtos/gateMP] ========
>> | ======== .make [./samples/rtos/heapMemMP] ========
>> | makefiles are up to date.
>> | ======== .make [./samples/rtos/knlNotify] ========
>> | making package.mak (because of package.bld) ...
>> | ======== .make [./samples/rtos/listMP] ========
>> | ======== .make [./samples/rtos/notify] ========
>> | ======== .make [./samples/rtos/platforms/evm6472/core0] ========
>> | ======== .make [./samples/rtos/messageQ] ========
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | ======== .make [./samples/rtos/platforms/evm6472/core1] ========
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | ======== .make [./samples/rtos/platforms/evm6472/core2] ========
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | making package.mak (because of package.bld) ...
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | js: "./package.bld", line 76: xdc.services.global.XDCException:
>> xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.syslink.ipc' along
>> the path: '/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-ipc-tree/packages;/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-sysbios-tree/packages;/home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/share/ti/ti-xdctools-tree/packages;../../../../..;'.
>> Ensure that the package path is set correctly.
>> | make[1]: *** Deleting file `package.mak'
>> | make[1]: *** No rule to make target `package.mak', neededERROR:
>> Function failed: do_prepsources (see
>> /home/hutch/angstrom/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/ti-syslink-2_00_00_78-r115a/temp/log.do_prepsources.28692
>> for further information)
>> | by `.make'. Stop.
>> | gmake: *** [samples/hlos/tilerDaemon,.make] Error 2
>> | gmake: *** Waiting for unfinished jobs....
>> | Warning: Target specification 'ti.targets.C64P' does not match any
>> loaded target module.
>> | No target modules were loaded.
>> |
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | makefiles are up to date.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | makefiles are up to date.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: Target specification 'ti.targets.C64P' does not match any
>> loaded target module.
>> | No target modules were loaded.
>> |
>> | Warning: Target specification 'ti.targets.C64P' does not match any
>> loaded target module.
>> | No target modules were loaded.
>> |
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | makefiles are up to date.
>> | Warning: no config.bld file was found along the package path.
>> | The config.bld file specifies the location of the
>> | compiler tool-chains required to compile runtime content.
>> | Without this file, the XDC tools assume no targets are to be
>> | used.
>> | makefiles are up to date.
>> NOTE: package ti-syslink-2_00_00_78-r115a: task do_prepsources: Failed
>> ERROR: Task 7 (/home/hutch/angstrom/setup-scripts/sources/meta-ti/recipes-ti/syslink/ti-syslink_2.00.00.78.bb,
>> do_prepsources) failed with exit code '1'
>> Waiting for 2 active tasks to finish:
>> 0: ti-ipc-1_24_00_16-r0 do_package (pid 28318)
>> 1: ti-syslink-2_00_00_78-r115a do_make_scripts (pid 28678)
>> Waiting for 1 active tasks to finish:
>> 0: ti-ipc-1_24_00_16-r0 do_package (pid 28318)
>> NOTE: package ti-syslink-2_00_00_78-r115a: task do_make_scripts: Succeeded
>> NOTE: package ti-ipc-1_24_00_16-r0: task do_package: Succeeded
>> NOTE: Tasks Summary: Attempted 1188 tasks of which 1156 didn't need to
>> be rerun and 1 failed.
>>
>> Summary: 1 task failed:
>> /home/hutch/angstrom/setup-scripts/sources/meta-ti/recipes-ti/syslink/ti-syslink_2.00.00.78.bb,
>> do_prepsources
>> Summary: There were 4520 WARNING messages shown.
>> Summary: There were 57 ERROR messages shown, returning a non-zero exit code.
>> hutch at neo:~/angstrom/setup-scripts$
>>
>>
>>
>> Any idea what steps I've missed or what the problem is?
>>
>
> Hi Brian,
>
> Syslink isn't supported on omap3 targets like beagleboard. For IPC on beagleboard we use dsplink instead.
Brian has a 816x evm to try as well :)
regards,
Koen
More information about the meta-ti
mailing list