[yocto] mpc8315e-rdb core-image-minimal fails
Anyone got any ideas about the following: | ERROR: Function 'do_rootfs' failed (see /local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-image-minimal-1.0-r0/temp/log.do_rootfs.19834 for fu rther information) | Generating solve db for /local/home/galak/git/poky/build/tmp/deploy/rpm/mpc8315e_rdb... |total: 1 0.00 MB 1.573137 secs |fingerprint: 816 0.004148 MB 0.062215 secs |install: 272 0.00 MB 0.384963 secs |dbadd: 272 0.00 MB 0.375238 secs |dbget: 0.00 MB 0.003093 secs |dbput: 272 1.315744 MB 0.302582 secs |readhdr: 2721 2.573624 MB 0.178385 secs |hdrload: 1360 3.828344 MB 0.007262 secs |hdrget: 49259 0.00 MB 0.048944 secs | Generating solve db for /local/home/galak/git/poky/build/tmp/deploy/rpm/all... |total: 1 0.00 MB 0.29 secs |fingerprint:18 0.24 MB 0.000280 secs |install: 6 0.00 MB 0.044466 secs |dbadd: 6 0.00 MB 0.039504 secs |dbget: 19 0.00 MB 0.000103 secs |dbput: 6 0.018916 MB 0.006250 secs |readhdr:61 0.038096 MB 0.000212 secs |hdrload:33 0.063864 MB 0.000327 secs |hdrget:983 0.00 MB 0.001306 secs | Generating solve db for /local/home/galak/git/poky/build/tmp/deploy/rpm/all... | Processing task-core-boot... | error: Failed dependencies: | tinylogin is needed by task-core-boot-1.0-r7.mpc8315e_rdb | busybox is needed by task-core-boot-1.0-r7.mpc8315e_rdb | modutils-initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb | initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb | update-alternatives-cworth is needed by task-core-boot-1.0-r7.mpc8315e_rdb | udev is needed by task-core-boot-1.0-r7.mpc8315e_rdb | sysvinit is needed by task-core-boot-1.0-r7.mpc8315e_rdb | netbase is needed by task-core-boot-1.0-r7.mpc8315e_rdb | base-passwd is needed by task-core-boot-1.0-r7.mpc8315e_rdb | console-tools is needed by keymaps-1.0-r19.mpc8315e_rdb | initscripts is needed by keymaps-1.0-r19.mpc8315e_rdb | /bin/sh is needed by keymaps-1.0-r19.mpc8315e_rdb NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed ERROR: Task 8 (/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1' ERROR: '/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.bb' failed - k ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails
Hi Kumar,
I'm just debugging the same issue.
It's caused by folder for the target specific packages being mis-named
"powerpcppc603e" instead of "ppc603e" which the rpm package bbclass is
expecting.
I haven't figured out why this is happening yet but I have a workaround
which is to move ${BUILD_DIR}/deploy/rpm/powerpcppc603e to
${BUILD_DIR}/deploy/rpm/ppc603e.
I will let you know as soon as I find the cause.
Regards
Malcolm
-Original Message-
From: yocto-boun...@yoctoproject.org
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar Gala
Sent: 28 July 2011 15:26
To: Patches and discussions about the oe-core layer
Cc: Yocto discussion list
Subject: [yocto] mpc8315e-rdb core-image-minimal fails
Anyone got any ideas about the following:
| ERROR: Function 'do_rootfs' failed (see
/local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-i
mage-minimal-1.0-r0/temp/log.do_rootfs.19834 for fu
rther information)
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/mpc8315e_rdb...
|total: 1 0.00 MB 1.573137 secs
|fingerprint: 816 0.004148 MB 0.062215 secs
|install: 272 0.00 MB 0.384963 secs
|dbadd: 272 0.00 MB 0.375238 secs
|dbget: 0.00 MB 0.003093 secs
|dbput: 272 1.315744 MB 0.302582 secs
|readhdr: 2721 2.573624 MB 0.178385 secs
|hdrload: 1360 3.828344 MB 0.007262 secs
|hdrget: 49259 0.00 MB 0.048944 secs
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/all...
|total: 1 0.00 MB 0.29 secs
|fingerprint:18 0.24 MB 0.000280 secs
|install: 6 0.00 MB 0.044466 secs
|dbadd: 6 0.00 MB 0.039504 secs
|dbget: 19 0.00 MB 0.000103 secs
|dbput: 6 0.018916 MB 0.006250 secs
|readhdr:61 0.038096 MB 0.000212 secs
|hdrload:33 0.063864 MB 0.000327 secs
|hdrget:983 0.00 MB 0.001306 secs
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/all...
| Processing task-core-boot...
| error: Failed dependencies:
| tinylogin is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| busybox is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| modutils-initscripts is needed by
task-core-boot-1.0-r7.mpc8315e_rdb
| initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| update-alternatives-cworth is needed by
task-core-boot-1.0-r7.mpc8315e_rdb
| udev is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| sysvinit is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| netbase is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| base-passwd is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| console-tools is needed by keymaps-1.0-r19.mpc8315e_rdb
| initscripts is needed by keymaps-1.0-r19.mpc8315e_rdb
| /bin/sh is needed by keymaps-1.0-r19.mpc8315e_rdb
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
ERROR: Task 8
(/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
bb, do_rootfs) failed with exit code '1'
ERROR:
'/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
bb' failed
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails
I think I know the cause, let me dig up the change that is related. What bit
is looking for just ppc603e?
- k
On Jul 28, 2011, at 10:42 AM, Crossley, Malcolm (GE Intelligent Platforms)
wrote:
> Hi Kumar,
>
> I'm just debugging the same issue.
>
> It's caused by folder for the target specific packages being mis-named
> "powerpcppc603e" instead of "ppc603e" which the rpm package bbclass is
> expecting.
>
> I haven't figured out why this is happening yet but I have a workaround
> which is to move ${BUILD_DIR}/deploy/rpm/powerpcppc603e to
> ${BUILD_DIR}/deploy/rpm/ppc603e.
>
> I will let you know as soon as I find the cause.
>
> Regards
>
> Malcolm
>
> -Original Message-
> From: yocto-boun...@yoctoproject.org
> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar Gala
> Sent: 28 July 2011 15:26
> To: Patches and discussions about the oe-core layer
> Cc: Yocto discussion list
> Subject: [yocto] mpc8315e-rdb core-image-minimal fails
>
> Anyone got any ideas about the following:
>
> | ERROR: Function 'do_rootfs' failed (see
> /local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-i
> mage-minimal-1.0-r0/temp/log.do_rootfs.19834 for fu
> rther information)
> | Generating solve db for
> /local/home/galak/git/poky/build/tmp/deploy/rpm/mpc8315e_rdb...
> |total: 1 0.00 MB 1.573137 secs
> |fingerprint: 816 0.004148 MB 0.062215 secs
> |install: 272 0.00 MB 0.384963 secs
> |dbadd: 272 0.00 MB 0.375238 secs
> |dbget: 0.00 MB 0.003093 secs
> |dbput: 272 1.315744 MB 0.302582 secs
> |readhdr: 2721 2.573624 MB 0.178385 secs
> |hdrload: 1360 3.828344 MB 0.007262 secs
> |hdrget: 49259 0.00 MB 0.048944 secs
> | Generating solve db for
> /local/home/galak/git/poky/build/tmp/deploy/rpm/all...
> |total: 1 0.00 MB 0.29 secs
> |fingerprint:18 0.24 MB 0.000280 secs
> |install: 6 0.00 MB 0.044466 secs
> |dbadd: 6 0.00 MB 0.039504 secs
> |dbget: 19 0.00 MB 0.000103 secs
> |dbput: 6 0.018916 MB 0.006250 secs
> |readhdr:61 0.038096 MB 0.000212 secs
> |hdrload:33 0.063864 MB 0.000327 secs
> |hdrget:983 0.00 MB 0.001306 secs
> | Generating solve db for
> /local/home/galak/git/poky/build/tmp/deploy/rpm/all...
> | Processing task-core-boot...
> | error: Failed dependencies:
> | tinylogin is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | busybox is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | modutils-initscripts is needed by
> task-core-boot-1.0-r7.mpc8315e_rdb
> | initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | update-alternatives-cworth is needed by
> task-core-boot-1.0-r7.mpc8315e_rdb
> | udev is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | sysvinit is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | netbase is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | base-passwd is needed by task-core-boot-1.0-r7.mpc8315e_rdb
> | console-tools is needed by keymaps-1.0-r19.mpc8315e_rdb
> | initscripts is needed by keymaps-1.0-r19.mpc8315e_rdb
> | /bin/sh is needed by keymaps-1.0-r19.mpc8315e_rdb
> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
> ERROR: Task 8
> (/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
> bb, do_rootfs) failed with exit code '1'
> ERROR:
> '/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
> bb' failed
>
> - k
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails
On 07/28/2011 08:45 AM, Kumar Gala wrote:
I think I know the cause, let me dig up the change that is related. What bit
is looking for just ppc603e?
This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try
the patch that Koen posted.
Thanks
Sau!
- k
On Jul 28, 2011, at 10:42 AM, Crossley, Malcolm (GE Intelligent Platforms)
wrote:
Hi Kumar,
I'm just debugging the same issue.
It's caused by folder for the target specific packages being mis-named
"powerpcppc603e" instead of "ppc603e" which the rpm package bbclass is
expecting.
I haven't figured out why this is happening yet but I have a workaround
which is to move ${BUILD_DIR}/deploy/rpm/powerpcppc603e to
${BUILD_DIR}/deploy/rpm/ppc603e.
I will let you know as soon as I find the cause.
Regards
Malcolm
-Original Message-
From: yocto-boun...@yoctoproject.org
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar Gala
Sent: 28 July 2011 15:26
To: Patches and discussions about the oe-core layer
Cc: Yocto discussion list
Subject: [yocto] mpc8315e-rdb core-image-minimal fails
Anyone got any ideas about the following:
| ERROR: Function 'do_rootfs' failed (see
/local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-i
mage-minimal-1.0-r0/temp/log.do_rootfs.19834 for fu
rther information)
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/mpc8315e_rdb...
|total: 1 0.00 MB 1.573137 secs
|fingerprint: 816 0.004148 MB 0.062215 secs
|install: 272 0.00 MB 0.384963 secs
|dbadd: 272 0.00 MB 0.375238 secs
|dbget: 0.00 MB 0.003093 secs
|dbput: 272 1.315744 MB 0.302582 secs
|readhdr: 2721 2.573624 MB 0.178385 secs
|hdrload: 1360 3.828344 MB 0.007262 secs
|hdrget: 49259 0.00 MB 0.048944 secs
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/all...
|total: 1 0.00 MB 0.29 secs
|fingerprint:18 0.24 MB 0.000280 secs
|install: 6 0.00 MB 0.044466 secs
|dbadd: 6 0.00 MB 0.039504 secs
|dbget: 19 0.00 MB 0.000103 secs
|dbput: 6 0.018916 MB 0.006250 secs
|readhdr:61 0.038096 MB 0.000212 secs
|hdrload:33 0.063864 MB 0.000327 secs
|hdrget:983 0.00 MB 0.001306 secs
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deploy/rpm/all...
| Processing task-core-boot...
| error: Failed dependencies:
| tinylogin is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| busybox is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| modutils-initscripts is needed by
task-core-boot-1.0-r7.mpc8315e_rdb
| initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| update-alternatives-cworth is needed by
task-core-boot-1.0-r7.mpc8315e_rdb
| udev is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| sysvinit is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| netbase is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| base-passwd is needed by task-core-boot-1.0-r7.mpc8315e_rdb
| console-tools is needed by keymaps-1.0-r19.mpc8315e_rdb
| initscripts is needed by keymaps-1.0-r19.mpc8315e_rdb
| /bin/sh is needed by keymaps-1.0-r19.mpc8315e_rdb
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
ERROR: Task 8
(/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
bb, do_rootfs) failed with exit code '1'
ERROR:
'/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
bb' failed
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails
I have, it doesn't help. I believe its partly due to how we are appending to
TUNE_PKGARCH, but what's not clear to me is what case is failing and looking
for just ppc603e instead of powerpcppc603e
- k
On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
> On 07/28/2011 08:45 AM, Kumar Gala wrote:
>> I think I know the cause, let me dig up the change that is related. What
>> bit is looking for just ppc603e?
>>
> This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try the
> patch that Koen posted.
>
> Thanks
> Sau!
>
>> - k
>>
>> On Jul 28, 2011, at 10:42 AM, Crossley, Malcolm (GE Intelligent Platforms)
>> wrote:
>>
>>> Hi Kumar,
>>>
>>> I'm just debugging the same issue.
>>>
>>> It's caused by folder for the target specific packages being mis-named
>>> "powerpcppc603e" instead of "ppc603e" which the rpm package bbclass is
>>> expecting.
>>>
>>> I haven't figured out why this is happening yet but I have a workaround
>>> which is to move ${BUILD_DIR}/deploy/rpm/powerpcppc603e to
>>> ${BUILD_DIR}/deploy/rpm/ppc603e.
>>>
>>> I will let you know as soon as I find the cause.
>>>
>>> Regards
>>>
>>> Malcolm
>>>
>>> -Original Message-
>>> From: yocto-boun...@yoctoproject.org
>>> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar Gala
>>> Sent: 28 July 2011 15:26
>>> To: Patches and discussions about the oe-core layer
>>> Cc: Yocto discussion list
>>> Subject: [yocto] mpc8315e-rdb core-image-minimal fails
>>>
>>> Anyone got any ideas about the following:
>>>
>>> | ERROR: Function 'do_rootfs' failed (see
>>> /local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-i
>>> mage-minimal-1.0-r0/temp/log.do_rootfs.19834 for fu
>>> rther information)
>>> | Generating solve db for
>>> /local/home/galak/git/poky/build/tmp/deploy/rpm/mpc8315e_rdb...
>>> |total: 1 0.00 MB 1.573137 secs
>>> |fingerprint: 816 0.004148 MB 0.062215 secs
>>> |install: 272 0.00 MB 0.384963 secs
>>> |dbadd: 272 0.00 MB 0.375238 secs
>>> |dbget: 0.00 MB 0.003093 secs
>>> |dbput: 272 1.315744 MB 0.302582 secs
>>> |readhdr: 2721 2.573624 MB 0.178385 secs
>>> |hdrload: 1360 3.828344 MB 0.007262 secs
>>> |hdrget: 49259 0.00 MB 0.048944 secs
>>> | Generating solve db for
>>> /local/home/galak/git/poky/build/tmp/deploy/rpm/all...
>>> |total: 1 0.00 MB 0.29 secs
>>> |fingerprint:18 0.24 MB 0.000280 secs
>>> |install: 6 0.00 MB 0.044466 secs
>>> |dbadd: 6 0.00 MB 0.039504 secs
>>> |dbget: 19 0.00 MB 0.000103 secs
>>> |dbput: 6 0.018916 MB 0.006250 secs
>>> |readhdr:61 0.038096 MB 0.000212 secs
>>> |hdrload:33 0.063864 MB 0.000327 secs
>>> |hdrget:983 0.00 MB 0.001306 secs
>>> | Generating solve db for
>>> /local/home/galak/git/poky/build/tmp/deploy/rpm/all...
>>> | Processing task-core-boot...
>>> | error: Failed dependencies:
>>> | tinylogin is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | busybox is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | modutils-initscripts is needed by
>>> task-core-boot-1.0-r7.mpc8315e_rdb
>>> | initscripts is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | update-alternatives-cworth is needed by
>>> task-core-boot-1.0-r7.mpc8315e_rdb
>>> | udev is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | sysvinit is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | netbase is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | base-passwd is needed by task-core-boot-1.0-r7.mpc8315e_rdb
>>> | console-tools is needed by keymaps-1.0-r19.mpc8315e_rdb
>>> | initscripts is needed by keymaps-1.0-r19.mpc8315e_rdb
>>> | /bin/sh is needed by keymaps-1.0-r19.mpc8315e_rdb
>>> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
>>> ERROR: Task 8
>>> (/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
>>> bb, do_rootfs) failed with exit code '1'
>>> ERROR:
>>> '/local/home/galak/git/poky/meta/recipes-core/images/core-image-minimal.
>>> bb' failed
>>>
>>> - k
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [PATCH] Switch to using perl-native for various packages instead of host perl
On Wed, Jul 27, 2011 at 10:22 PM, Saul Wold wrote: > On 07/26/2011 12:22 PM, Matthew McClintock wrote: >> >> Several builds are using perl on the host instead of perl built by >> poky. This fixes the issue for several packages. >> > Matthew, > > Thanks for submitting this. > > A similar fix was recently rejected, as we are looking at a different way to > accomplish this. > > See > http://lists.linuxtogo.org/pipermail/openembedded-core/2011-July/006439.html Why do we let the host perl in the path for target installs at all? Is there some precedence for what can be used from the host machine and what can not? -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails (PACKAGE_ARCHS question)
On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
> On 07/28/2011 08:45 AM, Kumar Gala wrote:
>> I think I know the cause, let me dig up the change that is related. What
>> bit is looking for just ppc603e?
>>
> This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try the
> patch that Koen posted.
>
> Thanks
> Sau!
so in conf/bitbake.conf
PACKAGE_ARCH = "${TUNE_PKGARCH}"
MACHINE_ARCH = "${@[bb.data.getVar('TUNE_PKGARCH', d, 1),
bb.data.getVar('MACHINE', d, 1)][bool(bb.data.getVar('MACHINE', d,
1))].replace('-', '_')}"
PACKAGE_EXTRA_ARCHS ??= "${PACKAGE_EXTRA_ARCHS_tune-${DEFAULTTUNE}}"
PACKAGE_ARCHS = "all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}"
Shouldn't PACKAGE_ARCHS be:
PACKAGE_ARCHS = "all any noarch ${PACKAGE_ARCH} ${PACKAGE_EXTRA_ARCHS}
${MACHINE_ARCH}"
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] mpc8315e-rdb core-image-minimal fails (PACKAGE_ARCHS question)
On Thu, Jul 28, 2011 at 01:43:45PM -0500, Kumar Gala wrote:
>
> On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
>
> > On 07/28/2011 08:45 AM, Kumar Gala wrote:
> >> I think I know the cause, let me dig up the change that is related. What
> >> bit is looking for just ppc603e?
> >>
> > This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try the
> > patch that Koen posted.
> >
> > Thanks
> > Sau!
>
> so in conf/bitbake.conf
>
> PACKAGE_ARCH = "${TUNE_PKGARCH}"
> MACHINE_ARCH = "${@[bb.data.getVar('TUNE_PKGARCH', d, 1),
> bb.data.getVar('MACHINE', d, 1)][bool(bb.data.getVar('MACHINE', d,
> 1))].replace('-', '_')}"
> PACKAGE_EXTRA_ARCHS ??= "${PACKAGE_EXTRA_ARCHS_tune-${DEFAULTTUNE}}"
> PACKAGE_ARCHS = "all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}"
>
>
> Shouldn't PACKAGE_ARCHS be:
>
> PACKAGE_ARCHS = "all any noarch ${PACKAGE_ARCH} ${PACKAGE_EXTRA_ARCHS}
> ${MACHINE_ARCH}"
this change causes ERROR here with nokia900:
Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are
listed more than once: armv7a-vfp-neon
Regards,
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] mpc8315e-rdb core-image-minimal fails (PACKAGE_ARCHS question)
On Thu, 2011-07-28 at 20:54 +0200, Martin Jansa wrote: > this change causes ERROR here with nokia900: > Error, the PACKAGE_ARCHS variable contains duplicates. The following archs > are listed more than once: armv7a-vfp-neon It isn't totally obvious to me that it needs to be an error for PACKAGE_ARCHS to contain dupes. AFAIK there is no reason that it couldn't simply be uniquified before use. p. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] mpc8315e-rdb core-image-minimal fails (PACKAGE_ARCHS question)
On Jul 28, 2011, at 2:04 PM, Phil Blundell wrote:
> On Thu, 2011-07-28 at 20:54 +0200, Martin Jansa wrote:
>> this change causes ERROR here with nokia900:
>> Error, the PACKAGE_ARCHS variable contains duplicates. The following archs
>> are listed more than once: armv7a-vfp-neon
>
> It isn't totally obvious to me that it needs to be an error for
> PACKAGE_ARCHS to contain dupes. AFAIK there is no reason that it
> couldn't simply be uniquified before use.
>
> p.
>
Ok, maybe we want:
-PACKAGE_ARCHS = "all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}"
+PACKAGE_ARCHS = "all any noarch ${TUNE_PKGARCH} ${PACKAGE_EXTRA_ARCHS}
${MACHINE_ARCH}"
instead as we redefine PACKAGE_ARCH in different places.
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trying to create OpenDDS recipe
Hi Paul,
On 07/19/2011 07:41 AM, Ourada, Paul wrote:
> I hope this is the correct place to post this. If not, please let me
> know.
This is the right place. In the future please don't reply to an existing
post as your message then gets threaded with the one you replied to
(likely why you didn't receive a response so far - that I see anyway).
>
> I'm trying to create a recipe for OpenDDS. The recipe works so far as
> fetching, unpacking, and configuration. Or it seems to. :) Part of the
> configuration piece is that it also pulls down ACE+TAO real-time CORBA.
> This part works fine as well.
>
> I set S as follows to match the unpacking directories enforced by the
> tar file:
>
> S = ${WORKINGDIR}/DDS
>
> The package comes with a configuration script pre-built, and it expects
> to be told where glibc is. So, I write do_configure as follows:
>
> EXTRA_OECONF = "-glibc=${STAGING_DIR}/${MACHINE}/usr"
>
> do_configure() {
> ${S}/configure ${EXTRA_OECONF}
> }
>
> The problem that I run into is during compilation. I write the following
> for do_compile()
>
> do_compile() {
> oenote ${STAGING_DIR}
> cd ${S} && make
> }
Is there a reason you are overriding configure and compile? These appear
to be autoconf projects, which should just work for recipes using
autotools.bbclass.
>
> This works right up until there is a compile error in ACE+TAO. Of
> course, I build the entire DDS package, including ACE+TAO, with no
> hiccups in Ubuntu, so I understand that this is a
> cross-compile/environment issue.
>
> The compile error is that it cannot find features.h, which is clearly in
> ${STAGING_LIBDIR}/${MACHINE}/usr/include. The compile command which is
> being executed is as follows (this is going to be ugly, let me know if
> there's a better way to include this, such as a pastebin somewhere):
This is better - the pastebin isn't as reliable, and having it inline to
review and for future reference is much preferred.
>
> | make[1]: Entering directory
> `/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE
> _wrappers/TAO/TAO_IDL'
> |
> | GNUmakefile:
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/TAO/TAO_IDL/GNUmakefile.TAO_IDL_EXE MAKEFLAGS=w
> |
> | i586-poky-linux-g++ -march=i586
> --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86
> -fvisibility=hidden -fvisibility-inlines-hidden -W -Wall -Wpointer-arith
> -ggdb -pipe -D_REENTRANT -DACE_HAS_AIO_CALLS -D_GNU_SOURCE
> -I/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/AC
> E_wrappers -DACE_HAS_EXCEPTIONS -DACE_NO_INLINE -I../.. -Iinclude
> -Ibe_include -Ife -I.. -DTAO_IDL_PREPROCESSOR=\"i586-poky-linux-g++
> -march=i586 --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86\"
> -c -o .obj/driver/drv_preproc.o driver/drv_preproc.cpp
> | :0:22: warning: missing terminating " character
> | In file included from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-linux-common.h:30:0,
> | from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-linux.h:14,
> | from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config.h:1,
> | from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-macros.h:24,
> | from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-lite.h:24,
> | from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/os_include/os_limits.h:21,
> | from include/idl_defines.h:70,
> | from driver/drv_preproc.cpp:70:
> |
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-posix.h:7:20: fatal error: unistd.h: No such file or
> directory
Do you see unistd.h under /opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86 ?
> | compilation terminated.
> | make[1]: *** [.obj/driver/drv_preproc.o] Error 1
> | make[1]: Leaving directory
> `/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE
> _wrappers/TAO/TAO_IDL'
> | make: *** [TAO_IDL_EXE] Error 2
> | ERROR: Function 'do_compile' failed (see
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/temp
> /log.do_compile.17412 for further information)
> NOTE: package opendds-2.3-r0: task do_compile: Failed
> ERROR: Task 5
> (/opt/yocto/poky-bernard-5.0.1/meta/recipes-middleware/opendds/opendds_2
> .3.bb, do_compile) failed with exit code '1'
>
> The thing that is puzzling me is that --sysroot seems to be pointing in
> the general direction of ${STAGING_DIR} and so the include directive,
> #include should be good. I have checked, and features.h is
> in the /usr/include subdirectory there.
I see unistd.h missing, not features.h.
--
Darren
>
> Does anyone have a cl
Re: [yocto] Trying to create OpenDDS recipe
Hi Darren -
Thanks for getting back to me. I have been able to get a lot further with the
recipe. It turns out that the problem is in the makefiles for OpenDDS. I'll
detail further below.
Paul E. Ourada
Sr. Principal Software Engineer
Covidien, Energy-based Devices
5920 Longbow Drive
Boulder, CO 80301
paul.our...@covidien.com
www.covidien.com
Main: 303-530-2300
Ofc: 303-581-6940
Fax: 303-581-6741
> Hi Paul,
On 07/19/2011 07:41 AM, Ourada, Paul wrote:
>> I hope this is the correct place to post this. If not, please let me
>> know.
> This is the right place. In the future please don't reply to an existing
> post as your message then gets threaded with the one you replied to
> (likely why you didn't receive a response so far - that I see anyway).
I guess I thought that changing the subject would have fixed that. Guess the
mail list s/w is smarter than that. :)
>>
>> I'm trying to create a recipe for OpenDDS. The recipe works so far as
>> fetching, unpacking, and configuration. Or it seems to. :) Part of the
>> configuration piece is that it also pulls down ACE+TAO real-time CORBA.
>> This part works fine as well.
>>
>> I set S as follows to match the unpacking directories enforced by the
>> tar file:
>>
>> S = ${WORKINGDIR}/DDS
>>
>> The package comes with a configuration script pre-built, and it expects
>> to be told where glibc is. So, I write do_configure as follows:
>>
>> EXTRA_OECONF = "-glibc=${STAGING_DIR}/${MACHINE}/usr"
>>
>> do_configure() {
>> ${S}/configure ${EXTRA_OECONF}
>> }
>>
>> The problem that I run into is during compilation. I write the following
>> for do_compile()
>>
>> do_compile() {
>> oenote ${STAGING_DIR}
>> cd ${S} && make
>> }
> Is there a reason you are overriding configure and compile? These appear
> to be autoconf projects, which should just work for recipes using
> autotools.bbclass.
I had tried that initially. The configuration file is already supplied, so
running autotools to create the configure script is not necessary, but running
./configure is. Is there a better way to do that?
:
:
<< most of the compiler command line gobblety-gook snipped>>
>> -DTAO_IDL_PREPROCESSOR=\"i586-poky-linux-g++
>> -march=i586 --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86\"
>> The thing that is puzzling me is that --sysroot seems to be pointing in
>> the general direction of ${STAGING_DIR} and so the include directive,
>> #include > should be good. I have checked, and features.h is
>> in the /usr/include subdirectory there.
> I see unistd.h missing, not features.h.
You're right, it was complaining about unistd.h, but it turns out that the real
culprit was the TAO_IDL_PREPROCESSOR macro above. When I compared it to what
was being emitted in the Ubuntu compile, I saw that the long, nasty, compound,
double-quoted thing should have just been "i586-poky-linux-g++."
TAO_ID_PREPROCESSOR was being assigned the value of ${CXX}.
It appears that instead of pre-pending the ${CPPFLAGS} variable, yocto/poky
recipes were appending the cross-compile build variables to ${CXX}. I patched
the OpenDDS makefile(s) to look for the first word in the ${CXX} macro, and
substituted that in the assignment of TAO_IDL_PREPROCESSOR. Dunno if that's the
"right" way to do it, or if there's a bug in ${CXX} assignment?
Anyway, I think that I'm getting there w/the recipe. I'm sure that there are
some things I'm doing wrong. For instance, I'm no longer cd'ing to ${S}, as OE
already takes me there. I'm also using oe_runmake in do_compile().
I expect that I'll be running some version of "make install" at some point.
I'm sure I'll have more questions as I go along.
Thanks for helping an OE/Yocto N00b!
Paul
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH][linux-yocto-3.0] drivers/misc/pch_phub.c: don't oops if dmi_get_system_info returns NULL
Bruce,
Please apply to yocto/base. Fixes a boot issue for a
tunnel creek development board.
--
commit 2b934c6236983392d01bef22e43af3051cac16f5
If dmi_get_system_info() returns NULL, pch_phub_probe() will dereferencea
a zero pointer.
This oops was observed on an Atom based board which has no BIOS, but a
bootloder which doesn't privde DMI data.
Signed-off-by: Alexander Stein
Cc: Tomoya MORINAGA
Cc: Greg KH
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
---
drivers/misc/pch_phub.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/misc/pch_phub.c b/drivers/misc/pch_phub.c
index 5fe79df..01eb67b 100644
--- a/drivers/misc/pch_phub.c
+++ b/drivers/misc/pch_phub.c
@@ -686,6 +686,8 @@ static int __devinit pch_phub_probe(struct pci_dev *pdev,
}
if (id->driver_data == 1) { /* EG20T PCH */
+ const char *board_name;
+
retval = sysfs_create_file(&pdev->dev.kobj,
&dev_attr_pch_mac.attr);
if (retval)
@@ -701,7 +703,8 @@ static int __devinit pch_phub_probe(struct pci_dev *pdev,
CLKCFG_CANCLK_MASK);
/* quirk for CM-iTC board */
- if (strstr(dmi_get_system_info(DMI_BOARD_NAME), "CM-iTC"))
+ board_name = dmi_get_system_info(DMI_BOARD_NAME);
+ if (board_name && strstr(board_name, "CM-iTC"))
pch_phub_read_modify_write_reg(chip,
(unsigned int)CLKCFG_REG_OFFSET,
CLKCFG_UART_48MHZ |
CLKCFG_BAUDDIV |
--
1.7.1
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trying to create OpenDDS recipe
Nitin, Khem, some toolchain related (I think) questions inline below.
On 07/28/2011 04:16 PM, Ourada, Paul wrote:
> Hi Darren -
>
> Thanks for getting back to me. I have been able to get a lot further
> with the recipe. It turns out that the problem is in the makefiles
> for OpenDDS. I'll detail further below.
>
> Paul E. Ourada Sr. Principal Software Engineer Covidien, Energy-based
> Devices 5920 Longbow Drive Boulder, CO 80301
> paul.our...@covidien.com www.covidien.com Main: 303-530-2300 Ofc:
> 303-581-6940 Fax: 303-581-6741
>
>
>> Hi Paul,
>
> On 07/19/2011 07:41 AM, Ourada, Paul wrote:
>>> I hope this is the correct place to post this. If not, please let
>>> me know.
>
>> This is the right place. In the future please don't reply to an
>> existing post as your message then gets threaded with the one you
>> replied to (likely why you didn't receive a response so far - that
>> I see anyway).
>
> I guess I thought that changing the subject would have fixed that.
> Guess the mail list s/w is smarter than that. :)
In case you're actually curious :-) it's your mail client. It inserts
the following header:
In-Reply-To:
Which a compliant mail reader will thread with that message.
>
>>>
>>> I'm trying to create a recipe for OpenDDS. The recipe works so
>>> far as fetching, unpacking, and configuration. Or it seems to. :)
>>> Part of the configuration piece is that it also pulls down
>>> ACE+TAO real-time CORBA. This part works fine as well.
>>>
>>> I set S as follows to match the unpacking directories enforced by
>>> the tar file:
>>>
>>> S = ${WORKINGDIR}/DDS
>>>
>>> The package comes with a configuration script pre-built, and it
>>> expects to be told where glibc is. So, I write do_configure as
>>> follows:
>>>
>>> EXTRA_OECONF = "-glibc=${STAGING_DIR}/${MACHINE}/usr"
>>>
>>> do_configure() { ${S}/configure ${EXTRA_OECONF} }
>>>
>>> The problem that I run into is during compilation. I write the
>>> following for do_compile()
>>>
>>> do_compile() { oenote ${STAGING_DIR} cd ${S} && make }
>
>> Is there a reason you are overriding configure and compile? These
>> appear to be autoconf projects, which should just work for recipes
>> using autotools.bbclass.
>
> I had tried that initially. The configuration file is already
> supplied, so running autotools to create the configure script is not
> necessary, but running ./configure is. Is there a better way to do
> that?
Does regenerating .configure actually cause a problem? If not, I would
still suggest using the autotools base and simplify your recipe.
>
> : : << most of the compiler command line gobblety-gook snipped>>
>
>>> -DTAO_IDL_PREPROCESSOR=\"i586-poky-linux-g++ -march=i586
>>> --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86\"
>
>
>>> The thing that is puzzling me is that --sysroot seems to be
>>> pointing in the general direction of ${STAGING_DIR} and so the
>>> include directive, #include > should be good. I have
>>> checked, and features.h is in the /usr/include subdirectory
>>> there.
>
>> I see unistd.h missing, not features.h.
>
> You're right, it was complaining about unistd.h, but it turns out
> that the real culprit was the TAO_IDL_PREPROCESSOR macro above. When
> I compared it to what was being emitted in the Ubuntu compile, I saw
> that the long, nasty, compound, double-quoted thing should have just
> been "i586-poky-linux-g++." TAO_ID_PREPROCESSOR was being assigned
> the value of ${CXX}.
>
> It appears that instead of pre-pending the ${CPPFLAGS} variable,
> yocto/poky recipes were appending the cross-compile build variables
> to ${CXX}. I patched the OpenDDS makefile(s) to look for the first
> word in the ${CXX} macro, and substituted that in the assignment of
> TAO_IDL_PREPROCESSOR. Dunno if that's the "right" way to do it, or if
> there's a bug in ${CXX} assignment?
These are good toolchain questions for Nitin or Khem, now on CC.
>
> Anyway, I think that I'm getting there w/the recipe. I'm sure that
> there are some things I'm doing wrong. For instance, I'm no longer
> cd'ing to ${S}, as OE already takes me there. I'm also using
> oe_runmake in do_compile().
If you're running oe_runmake from do_compile then you might be able to
omit do_compile and use the base class implementation.
>
> I expect that I'll be running some version of "make install" at some
> point.
Again, should be automagic.
>
> I'm sure I'll have more questions as I go along.
>
> Thanks for helping an OE/Yocto N00b!
>
> Paul
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][linux-yocto-3.0] drivers/misc/pch_phub.c: don't oops if dmi_get_system_info returns NULL
On 11-07-28 7:51 PM, Darren Hart wrote:
Bruce,
Please apply to yocto/base. Fixes a boot issue for a
tunnel creek development board.
I fetched and updated master in linux-yocto-3.0 and cherry picked
this into yocto/base, and merged it out.
e6625fa..55f9c40 master -> master
935b896..c33fc74 yocto/base -> yocto/base
67283c12..30a2cec yocto/standard/arm-versatile-926ejs ->
yocto/standard/arm-versatile-926ejs
dee149a..318b059 yocto/standard/base -> yocto/standard/base
850784c..f79313d yocto/standard/beagleboard ->
yocto/standard/beagleboard
b584e72..c30a568 yocto/standard/common-pc-64/base ->
yocto/standard/common-pc-64/base
8064012..61da1e3 yocto/standard/common-pc-64/jasperforest ->
yocto/standard/common-pc-64/jasperforest
69faf26..ac5c59d yocto/standard/common-pc-64/romley ->
yocto/standard/common-pc-64/romley
1da9aad..c49c587 yocto/standard/common-pc-64/sugarbay ->
yocto/standard/common-pc-64/sugarbay
287479a..9e321ee yocto/standard/common-pc/atom-pc ->
yocto/standard/common-pc/atom-pc
f56a137..efaab1f yocto/standard/common-pc/base ->
yocto/standard/common-pc/base
34a9e0e..9a259cf yocto/standard/crownbay -> yocto/standard/crownbay
311152b..8c09403 yocto/standard/emenlow -> yocto/standard/emenlow
813ec5a..e556c2a yocto/standard/fishriver -> yocto/standard/fishriver
2d19d3f..5e08aa8 yocto/standard/fri2 -> yocto/standard/fri2
1562ec0..a8eef04 yocto/standard/fsl-mpc8315e-rdb ->
yocto/standard/fsl-mpc8315e-rdb
ac0f36e..f9b9688 yocto/standard/mti-malta32-be ->
yocto/standard/mti-malta32-be
7d24c08..bb024ac yocto/standard/mti-malta32-le ->
yocto/standard/mti-malta32-le
40381c3..6c76d97 yocto/standard/preempt-rt/base ->
yocto/standard/preempt-rt/base
40381c3..5ae5cb6 yocto/standard/preempt-rt/common-pc ->
yocto/standard/preempt-rt/common-pc
38525f1..a46a4c3 yocto/standard/qemu-ppc32 -> yocto/standard/qemu-ppc32
5eaea5c..df9213c yocto/standard/routerstationpro ->
yocto/standard/routerstationpro
You'll need to use kernel-dev or update your SRCREVs manually to pick
it up. I've got a pending update that I'll send out later. But we'd have
to wait for it to merge into poky master anyway.
Cheers,
Bruce
--
commit 2b934c6236983392d01bef22e43af3051cac16f5
If dmi_get_system_info() returns NULL, pch_phub_probe() will dereferencea
a zero pointer.
This oops was observed on an Atom based board which has no BIOS, but a
bootloder which doesn't privde DMI data.
Signed-off-by: Alexander Stein
Cc: Tomoya MORINAGA
Cc: Greg KH
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
---
drivers/misc/pch_phub.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/misc/pch_phub.c b/drivers/misc/pch_phub.c
index 5fe79df..01eb67b 100644
--- a/drivers/misc/pch_phub.c
+++ b/drivers/misc/pch_phub.c
@@ -686,6 +686,8 @@ static int __devinit pch_phub_probe(struct pci_dev *pdev,
}
if (id->driver_data == 1) { /* EG20T PCH */
+ const char *board_name;
+
retval = sysfs_create_file(&pdev->dev.kobj,
&dev_attr_pch_mac.attr);
if (retval)
@@ -701,7 +703,8 @@ static int __devinit pch_phub_probe(struct pci_dev *pdev,
CLKCFG_CANCLK_MASK);
/* quirk for CM-iTC board */
- if (strstr(dmi_get_system_info(DMI_BOARD_NAME), "CM-iTC"))
+ board_name = dmi_get_system_info(DMI_BOARD_NAME);
+ if (board_name&& strstr(board_name, "CM-iTC"))
pch_phub_read_modify_write_reg(chip,
(unsigned int)CLKCFG_REG_OFFSET,
CLKCFG_UART_48MHZ |
CLKCFG_BAUDDIV |
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
Scott - I have had a couple of questions about this exact topic. Can you please submit a bug on this? Thanks. Sent from my Blackberry - Original Message - From: Kumar Gala [mailto:ga...@kernel.crashing.org] Sent: Wednesday, July 27, 2011 08:37 PM To: Yocto discussion list Subject: [yocto] examples / docs on utilizing an external toolchain It seems like there is a way to use a prebuilt toolchain with poky but no real details. Some refs in the docs like: POKYMODE Toolchain selector. It can be external toolchain built from Poky or few supported combinations of upstream GCC or CodeSourcery Labs toolchain. But grepping the code there doesn't seem to be any actual use of POKYMODE. There seems to be some references even on the autobuilder about this 'nightly-external-toolchain'. So wondering what the details where on how to configure things to use an external toolchain. - k ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
