Hi,
We have a requirement to build our own custom toolchain for BSP mips64
architecture.
We have to use glibc(2.13) instead of eglibc and newlib(1.20) instead of uclibc
as libraries. Toolchain to be build with version 4.6.3 . I am able to override
existing toolchain version SRC 4.7.2 to 4.6.3
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
rd"
DISTRO = "poky"
DISTRO_VERSION= "1.4+snapshot-20131117"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
meta-xilinx
meta-kc705
me
On Sun, 17 Nov 2013, Chris Larson wrote:
>
> On Sun, Nov 17, 2013 at 9:17 AM, Robert P. J. Day
> wrote:
> $ bb show -r core-image-base ROOTFS_PKGMANAGE
> Parsing recipes..done.
> # ROOTFS_PKGMANAGE=opkg opkg-collateral ${EXTRAOPKGCONFIG}
> ROOTFS_PKGMANAGE="opkg opkg-coll
On Sun, Nov 17, 2013 at 9:17 AM, Robert P. J. Day wrote:
> $ bb show -r core-image-base ROOTFS_PKGMANAGE
> Parsing recipes..done.
> # ROOTFS_PKGMANAGE=opkg opkg-collateral ${EXTRAOPKGCONFIG}
> ROOTFS_PKGMANAGE="opkg opkg-collateral poky-feed-config-opkg"
> $
>
> but that feature *also* pulls in ad
On Sun, 17 Nov 2013, Chris Larson wrote:
... huge snip that i hope won't be necessary ...
> This test you did makes no sense. Of course it’s in IMAGE_FEATURES,
> you put it there. What you didn’t check is whether
> ${ROOTFS_PKGMANAGE} ended up being installed in the image, which it
> won’t be.
On Sun, 17 Nov 2013, Chris Larson wrote:
>
> On Sun, Nov 17, 2013 at 5:45 AM, Robert P. J. Day
> wrote:
> leaving aside the bug report, i am now hopelessly confused. are you
> saying this line:
>
> PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"
>
> from core-i
On Sun, Nov 17, 2013 at 5:45 AM, Robert P. J. Day wrote:
> leaving aside the bug report, i am now hopelessly confused. are you
> saying this line:
>
> PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"
>
> from core-image.bbclass is currently *necessary* to properly support
> the image fea
On Sun, 17 Nov 2013, Paul Eggleton wrote:
> On Sunday 17 November 2013 06:30:01 Robert P. J. Day wrote:
> > On Sun, 17 Nov 2013, Paul Eggleton wrote:
> > > On Sunday 17 November 2013 04:19:19 Robert P. J. Day wrote:
> > > > think i may have asked this once upon a time, but why, in
> > > >
> > >
On Sunday 17 November 2013 06:30:01 Robert P. J. Day wrote:
> On Sun, 17 Nov 2013, Paul Eggleton wrote:
> > On Sunday 17 November 2013 04:19:19 Robert P. J. Day wrote:
> > > think i may have asked this once upon a time, but why, in
> > >
> > > core-image.bbclass, is there the line:
> > > PACKA
Hi Robert,
On Sunday 17 November 2013 04:19:19 Robert P. J. Day wrote:
> think i may have asked this once upon a time, but why, in
> core-image.bbclass, is there the line:
>
> PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"
>
> as i read it, package-management doesn't represent an a
On Sun, 17 Nov 2013, Paul Eggleton wrote:
> Hi Robert,
>
> On Sunday 17 November 2013 04:19:19 Robert P. J. Day wrote:
> > think i may have asked this once upon a time, but why, in
> > core-image.bbclass, is there the line:
> >
> > PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"
> >
>
On Saturday 16 November 2013 00:17:34 Martin Jansa wrote:
> On Fri, Nov 15, 2013 at 02:52:27PM -0800, Leo Schwab wrote:
> > I'm working on transitioning from 'dylan' to the 'dora' branch for our
> > Freescale-based project, and suddenly my kernel is building with the
> > wrong config. I've isolate
think i may have asked this once upon a time, but why, in
core-image.bbclass, is there the line:
PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"
as i read it, package-management doesn't represent an actual package
group, but rather represents one of a number of IMAGE_FEATURES that
a
15 matches
Mail list logo
