On Fri, Jul 15, 2011 at 5:10 PM, Joshua Lock wrote:
> On Fri, 2011-07-15 at 11:44 +0100, Gray, Mark D wrote:
> This would lead me to make a guess at your proxy settings not being
> configured correctly for git with nc.
>
>
>> On closer inspection, the file
>> http://autobuilder.yoctoproject.org/so
On Fri, 2011-07-15 at 11:44 +0100, Gray, Mark D wrote:
> I have been trying to build on Ubuntu 11.0.4. I think I have followed
> the online documentation correctly. I have also followed the wiki
> page, which is required for me, to set up the proxy servers. However,
> the build is still failing for
Robert,
These are handled.
Thanks again.
ScottR
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Friday, July 15, 2011 10:10 AM
To: Yocto discussion list
Subject: [yocto] last observations about quick s
Fixed.
Thanks Robert.
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Friday, July 15, 2011 5:21 AM
To: Yocto discussion list
Subject: [yocto] [PATCH] DOCS: Correct format of command continuation.
Signe
"--host-armv5te..." should be "--host=armv5te..."
Signed-off-by: Robert P. J. Day
---
there's a fair amount in the ADT manual (and others) that can be
cleaned in terms of proper docbook semantic markup and entity usage,
but this looks like a fairly obvious error that should be fixed now.
di
;>
>>>> Any ideas ?
>>>>
>>>> - k
>>>>
>>>> [kumar@right build-p2020]$ bitbake meta-toolchain
>>>>
>>>> OE Build Configuration:
>>>> BB_VERSION= "1.13.2"
>>>> TARGET
[kumar@right build-p2020]$ bitbake meta-toolchain
>>>
>>> OE Build Configuration:
>>> BB_VERSION = "1.13.2"
>>> TARGET_ARCH = "powerpc"
>>> TARGET_OS = "linux-gnuspe"
>>> MACHINE = "p2020
N= "1.13.2"
>> TARGET_ARCH = "powerpc"
>> TARGET_OS = "linux-gnuspe"
>> MACHINE = "p2020-ds"
>> DISTRO= "poky"
>> DISTRO_VERSION= "1.0+snapshot-20110715"
>> TARGET_FPU
On Fri, Jul 15, 2011 at 2:13 PM, Kumar Gala wrote:
>
> On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
>
>> On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala
>> wrote:
>>> Where is the best place to ask questions and try and get support for adding
>>> some toolchain variations in?
>>>
>>> I'm wanting to
"
> MACHINE = "p2020-ds"
> DISTRO = "poky"
> DISTRO_VERSION = "1.0+snapshot-20110715"
> TARGET_FPU = "spe"
> meta
> meta-yocto = "master:068839698fe192d8846c0ed4db65861448e8e524"
>
> N
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
> On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala wrote:
>> Where is the best place to ask questions and try and get support for adding
>> some toolchain variations in?
>>
>> I'm wanting to add support in for a few different flavors of PPC that are
>>
uild-p2020]$ bitbake meta-toolchain
OE Build Configuration:
BB_VERSION= "1.13.2"
TARGET_ARCH = "powerpc"
TARGET_OS = "linux-gnuspe"
MACHINE = "p2020-ds"
DISTRO = "poky"
DISTRO_VERSION= "1.0
A couple commands are missing the version number directory level under
the /opt/poky toolchain installation directory.
Signed-off-by: Robert P. J. Day
---
i'll let scott take this as well, and decide whether it's worth
fixing this or just waiting for 1.1. either way works for me.
diff --gi
On 07/15/2011 03:12 PM, Koen Kooi wrote:
Op 15 jul 2011, om 20:33 heeft Darren Hart het volgende geschreven:
Jason, Koen,
Does anything spring to mind as an obvious fix for this? Perhaps
some kernel parameter initialization string for the graphics
hardware?
I've never seen it in angstrom, s
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala wrote:
> Where is the best place to ask questions and try and get support for adding
> some toolchain variations in?
>
> I'm wanting to add support in for a few different flavors of PPC that are not
> currently supported:
>
> * e500v2 (gcc needs --enab
Op 15 jul 2011, om 20:33 heeft Darren Hart het volgende geschreven:
> Jason, Koen,
>
> Does anything spring to mind as an obvious fix for this? Perhaps some
> kernel parameter initialization string for the graphics hardware?
I've never seen it in angstrom, so you'd have to see what meta-yocto i
On Fri, 15 Jul 2011, Darren Hart wrote:
> On 07/14/2011 05:01 PM, Robert P. J. Day wrote:
> >
> > just so i'm doing this the right way, what is the appropriate way to
> > report bitbake fetch errors? with a fully-updated git repo, i just
> > ran:
> >
> > $ bitbake -c fetchall -k core-image-sat
On 07/15/2011 09:55 AM, Scott Garman wrote:
> On 07/15/2011 07:15 AM, Robert P. J. Day wrote:
>>
>>(look on the bright side -- eventually, after many, many patches, i
>> will have nothing left to whine about.)
>
> :)
>
> I know I can speak for the team in saying we're incredibly grateful fo
Jason, Koen,
Does anything spring to mind as an obvious fix for this? Perhaps some
kernel parameter initialization string for the graphics hardware?
--
Darren
On 07/15/2011 08:30 AM, Jeff Mitchell wrote:
> Darren Hart suggested I send this to the list...
>
> Attached is a picture of my screen r
On 07/14/2011 05:55 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The meta-intel BSPs currently have a number of machine settings common
> to all - factor these out into a couple common include files.
>
> Signed-off-by: Tom Zanussi
> ---
> common/common-bsp-mach.inc | 13 +++
On 07/14/2011 05:01 PM, Robert P. J. Day wrote:
>
> just so i'm doing this the right way, what is the appropriate way to
> report bitbake fetch errors? with a fully-updated git repo, i just
> ran:
>
> $ bitbake -c fetchall -k core-image-sato
>
> and got fetch errors for both of:
>
> * s
Thanks Robert... I will deal with each of these.
ScottR
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Friday, July 15, 2011 10:10 AM
To: Yocto discussion list
Subject: [yocto] last observations about
1) "This optional GNOME mobile-based UI, which is intended for
devices with resolution but restricted size screens ..."
pretty sure there's a word missing before "resolution," no?
2) "OpenSUSE" vs "OpenSuse" ... actually, both of those are wrong,
it should be "openSUSE". :-P
3)
On 07/15/2011 07:15 AM, Robert P. J. Day wrote:
(look on the bright side -- eventually, after many, many patches, i
will have nothing left to whine about.)
:)
I know I can speak for the team in saying we're incredibly grateful for
your help in combing through our documentation. This is a
On Jul 15, 2011, at 8:37 AM, Richard Purdie wrote:
> On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
>> On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
>>
>>> Where is the best place to ask questions and try and get support for adding
>>> some toolchain variations in?
>>>
>>> I'm wanting t
Attendees:
Dave, Paul, Darren, Jeff, Dirk, Richard, Josh, Tom, Koen, Saul, Mark, Denys,
Jason, Beth, Song
Action item list:
* Team: please take a look at the proposed post 1.1 items (yellow in the M3
table, this is a draft, may change) on the wiki page and let Song know if there
is any com
Robert,
You can cross this off your list.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Friday, July 15, 2011 7:47 AM
To: Yocto discussion list
Subject: [yocto] [PATCH] DOCS: Fix toolchain filen
On Fri, 15 Jul 2011, Rifenbark, Scott M wrote:
> Wording change taken care of.
>
> Scott
ok, i can cross that off my list, thanks.
rday
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Signed-off-by: Robert P. J. Day
---
i think i got them all, i didn't see any other references anywhere
in the docs directory. does this look right?
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml
b/documentation/yocto-project-qs/yocto-project-qs.xml
index 52f7391..62c95ae
Wording change taken care of.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Richard Purdie
Sent: Friday, July 15, 2011 7:25 AM
To: Robert P. J. Day
Cc: Yocto discussion list
Subject: Re: [yocto] couple questions about t
Good catch Robert. I have fixed this and pushed. Will notify maintainer.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Friday, July 15, 2011 5:04 AM
To: Yocto discussion list
Subject: [yocto] [P
On Fri, 15 Jul 2011, Richard Purdie wrote:
> On Fri, 2011-07-15 at 10:15 -0400, Robert P. J. Day wrote:
> > (look on the bright side -- eventually, after many, many patches, i
> > will have nothing left to whine about.)
>
> :)
>
> > from quick start manual, i notice that all toolchain tarballs h
On Fri, 2011-07-15 at 10:15 -0400, Robert P. J. Day wrote:
> (look on the bright side -- eventually, after many, many patches, i
> will have nothing left to whine about.)
:)
> from quick start manual, i notice that all toolchain tarballs have
> "sdk" in the filename, whereas the actual download
(look on the bright side -- eventually, after many, many patches, i
will have nothing left to whine about.)
from quick start manual, i notice that all toolchain tarballs have
"sdk" in the filename, whereas the actual downloads have "gmae". a
simple textual fix, i'm assuming. (what means "gm
On 07/14/11 18:27, Darren Hart wrote:
From: Darren Hart
The following patch from mainline addresses an issues that prevented my
qemu testing from booting in less than 17M of memory. With this page,
the kernel can boot to init in 8M of memory.
Apply to yocto/standard/base
The following changes
On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
> On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
>
> > Where is the best place to ask questions and try and get support for adding
> > some toolchain variations in?
> >
> > I'm wanting to add support in for a few different flavors of PPC that
On Fri, 2011-07-15 at 06:23 -0700, Richard Purdie wrote:
> Hi Tom,
>
> On Thu, 2011-07-14 at 19:55 -0500, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > The meta-intel BSPs currently have a number of machine settings common
> > to all - factor these out into a couple common include f
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
> Where is the best place to ask questions and try and get support for adding
> some toolchain variations in?
>
> I'm wanting to add support in for a few different flavors of PPC that are not
> currently supported:
>
> * e500v2 (gcc needs --enabl
Hi Tom,
On Thu, 2011-07-14 at 19:55 -0500, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The meta-intel BSPs currently have a number of machine settings common
> to all - factor these out into a couple common include files.
For reference common include files are usually placed in
conf/ma
On 07/15/11 08:29, Kumar Gala wrote:
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
On 11-07-15 12:56 AM, Kumar Gala wrote:
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.
'SPE' floating point is what exists on the e500v2 core.
Acked-by: Bruce Ashfiel
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
> On 11-07-15 12:56 AM, Kumar Gala wrote:
>> The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
>> floating point.
>>
>> 'SPE' floating point is what exists on the e500v2 core.
>
> Acked-by: Bruce Ashfield
>
> Been meaning to
Signed-off-by: Robert P. J. Day
---
i *think* this is what the author had in mind.
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml
b/documentation/yocto-project-qs/yocto-project-qs.xml
index 52f7391..d2e85ba 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml
b/documentation/yocto-project-qs/yocto-project-qs.xml
index 52f7391..c0ba207 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-
On Fri, 15 Jul 2011, Paul Eggleton wrote:
> On Friday 15 July 2011 11:47:44 Robert P. J. Day wrote:
> > unsurprisingly, the fetch for the linux tarball still failed for the
> > same reason as before -- incorrect checksums. huh. i typically don't
> > expect to see that in a simple fetch. so chec
On Friday 15 July 2011 11:47:44 Robert P. J. Day wrote:
> unsurprisingly, the fetch for the linux tarball still failed for the
> same reason as before -- incorrect checksums. huh. i typically don't
> expect to see that in a simple fetch. so check KERNELORG_MIRROR (http
> site), *manually* downlo
while the problem has since gone away, something strange happened
yesterday i figured i'd share.
as a quick test, wanted to build core-image-sato so started with:
$ bitbake -c fetchall core-image-sato
just to grab everything and i'd start the build later. but, as i
reported yesterday, fe
Hi all,
I have been trying to build on Ubuntu 11.0.4. I think I have followed the
online documentation correctly. I have also followed the wiki page, which is
required for me, to set up the proxy servers. However, the build is still
failing for me. This is for Bernard-5.0.1. I get the following
47 matches
Mail list logo
