Hello all.
I'm trying to build core-image-minimal with external toolchain (
codesourcery).
I added meta, meta-yocto, meta-yocto-bsp to my bblayer.conf and also added
below lines to local.conf
TCMODE := "external-csl"
EXTERNAL_TOOLCHAIN := "/opt/armv7/codesourcery/"
After running bitbake core-im
>> I have a MACHINE_FEATURES which *does not* include "rtc", as the platform I
>> am working on doesn't have an RTC.
>>
>> The busybox bbappend I'm using (attached below) uses the provided
>> defconfig, but
>> disables the HWCLOCK features.
>>
>> However, my build is failing due to packagegroup-cor
Allow vmdk images to be run through the 'runqemu' facility.
---
scripts/runqemu | 39 +--
scripts/runqemu-internal | 20
2 files changed, 45 insertions(+), 14 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index fb7ac5
On Monday 10 December 2012 18:58:14 Jon Szymaniak wrote:
> I have a MACHINE_FEATURES which *does not* include "rtc", as the platform I
> am working on doesn't have an RTC.
>
> The busybox bbappend I'm using (attached below) uses the provided
> defconfig, but
> disables the HWCLOCK features.
>
> H
Hi all,
I have a MACHINE_FEATURES which *does not* include "rtc", as the platform I
am working on doesn't have an RTC.
The busybox bbappend I'm using (attached below) uses the provided
defconfig, but
disables the HWCLOCK features.
However, my build is failing due to packagegroup-core-boot being
On Mon, 10 Dec 2012, Tim Coote wrote:
> So I wasn't being totally stupid when I couldn't work out where the
> kernel images were.
i just checked, they have been restored.
rday
--
Robert P. J. Day
So I wasn't being totally stupid when I couldn't work out where the kernel
images were.
On 10 Dec 2012, at 17:07, Robert P. J. Day wrote:
>
> in the section "Using Pre-Built Binaries and QEMU" in the QS guide
> that i contributed to, there's a link to the qemu download
> directories:
>
> http
good. I was about to send you email about auditdir but your email
did not convey lot of what was going on.
On Mon, Dec 10, 2012 at 8:24 AM, Elvis Dowson wrote:
> Hi Khem,
>
> On Dec 9, 2012, at 10:58 PM, Elvis Dowson wrote:
>
> I get the following error while attempting to backport support for
Hi Ioana,
I can apply the patch with --ignore-whitespace option since you introduce extra
white spaces in your patch. Besides that, by looking at your patch, seems we
still have the option of "Validate existing git project loction option" showing
which we need to eliminate. For validate the
On Mon, Dec 10, 2012 at 9:07 AM, Robert P. J. Day wrote:
>
> in the section "Using Pre-Built Binaries and QEMU" in the QS guide
> that i contributed to, there's a link to the qemu download
> directories:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/machines/qemu
>
> and a sugge
Hi Timo,
On Monday 10 December 2012 09:13:41 m...@timomueller.eu wrote:
> From: Timo Mueller
>
> Hi,
>
> I've rebased the patch series. It should now apply to the current master.
>
> Best regards,
>Timo
>
> From the original cover letter:
>
> if you build eclipse-poky with the provid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
The first milestone for the upcoming Yocto Project 1.4 release is now
available at:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.4-m1/poky-yocto-1.4-m1.tar.bz2
Thank you everyone for all the hard work.
Elizabeth Flan
in the section "Using Pre-Built Binaries and QEMU" in the QS guide
that i contributed to, there's a link to the qemu download
directories:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/machines/qemu
and a suggestion that one can go there and download the appropriate
kernel for the
- when browsing through files in poky repository, files that contain '<', '>',
':','"', '/', '\', '|', '?', '*' will not be displayed on a Windows environment
and will through a ResourceException
- since these files are needed for the internal cooking files should not be
deleted, but the user do
- when browsing through files in poky repository, files that contain '<', '>',
':','"', '/', '\', '|', '?', '*' will not be displayed on a Windows environment
and will through a ResourceException
- since these files are needed for the internal cooking files should not be
deleted, but the user do
Hi Khem,
On Dec 9, 2012, at 10:58 PM, Elvis Dowson wrote:
> I get the following error while attempting to backport support for the older
> eglibc-2.13 recipe and gcc-4.5.4, to make it work with the latest poky master.
>
> I got the image to build and execute correctly, temporarily by commentin
Okay - I will put this on my TODO list
Thanks for the input.
Scott
>-Original Message-
>From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
>Sent: Monday, December 10, 2012 6:32 AM
>To: Rifenbark, Scott M
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] slight clarification for y
On Monday 10 December 2012 11:52:56 Rifenbark, Scott M wrote:
> Robert,
>
> This "poky" term in the link is because back when the manual was first set
> up I used "poky-ref-manual" as the manuals folder. The easiest fix would
> be set up a symlink from a more appropriately named link. A fix that
On 8 December 2012 17:24, Edward Vidal wrote:
> [2058242.932] (EE) module ABI major version (11) doesn't match the server's
> version (13)
That's because you used a driver that was built against an older
Xserver, don't do that. The omapfp package is still in oe-core, so
you can just build and us
Robert,
This "poky" term in the link is because back when the manual was first set up I
used "poky-ref-manual" as the manuals folder. The easiest fix would be set up
a symlink from a more appropriately named link. A fix that has a lot more
ripples would be to rename the directory to somethin
more pedantry, but here:
https://www.yoctoproject.org/documentation/inprogress
the link for the "Reference Manual" takes one to a link whose name
includes the word "poky" but whose manual has the name "yocto project
reference manual". is that properly a "poky" ref manual, or a "yocto"
ref man
On 9 Dec 2012, at 16:57, Chris Tapp wrote:
>
> On 9 Dec 2012, at 16:47, Chris Larson wrote:
>
>>
>>
>> On Sun, Dec 9, 2012 at 9:44 AM, Chris Tapp wrote:
>> On 9 Dec 2012, at 16:30, Chris Larson wrote:
>>
>>> On Sun, Dec 9, 2012 at 7:50 AM, Bruce Ashfield
>>> wrote:
>>> On 12-12-09 5:48 AM,
Hi Jessica,
I double checked and everything applies correctly on jzhang/windows-build.
The option --keep-cr expects to receive a patch who's line terminator is
carriage return, maybe in the process of saving & applying the patches these
line terminators get removed somehow?
I can send you the
From: Timo Mueller
If USE_LOCAL_GIT_REPO is set to 1 the build scripts uses the local
repository of the eclipse poky project for building instead of the
upstream project. The local repository is derived from the location
for the build script.
---
scripts/build.sh |8
1 files changed
From: Timo Mueller
Hi,
I've rebased the patch series. It should now apply to the current master.
Best regards,
Timo
>From the original cover letter:
if you build eclipse-poky with the provided build script it will always use
the upstream version of the IDE.
During development I wante
From: Timo Mueller
If the script is called with the -l option the local git repository is
used instead of the upstream repository.
---
scripts/build.sh |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/scripts/build.sh b/scripts/build.sh
index 693dcf7..54081d5 100755
From: Timo Mueller
Calling the build script with the -h option will now show the usage.
The cmdline parsing can be extended to add new options in the future.
---
scripts/build.sh | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/scripts/build.sh b/scripts
27 matches
Mail list logo
