2010/1/15 Denys Dmytriyenko :
> On Thu, Jan 14, 2010 at 10:02:57AM +0100, Frans Meulenbroeks wrote:
>> I suggest to review the rules;. E.g. this one:
>> # This should all be on one line and you should leave an empty line
>> before any detailed commit information.
>> Nice, but if you use git commit
On Thu, Jan 14, 2010 at 1:05 PM, Perepelica Alexander
wrote:
> After some conf changes I get unknown device sda - but I look at kernel
> config seems all is ok
try one of /dev/hda or dev/sda1 or /dev/hda1
>
> * Khem Raj [Thu, 14 Jan 2010 12:25:41 -0800]:
>>
>> On (14/01/10 09:45), Martyn Welch
On Thu, Jan 14, 2010 at 2:17 PM, GNUtoo wrote:
> hi,
> every time I build the illume image I've the following failures:
>
>
> First failure:
> --
> The first failure is about libefso and its deps,it has missing includes
> and so it fails,long time ago I tried to fix it but at a point I
Dnia piątek, 15 stycznia 2010 o 02:35:13 Guo Hongruan napisał(a):
> 在 Fri, 15 Jan 2010 03:53:01 +0800，Khem Raj 写道:
> > On (14/01/10 17:19), Guo Hongruan wrote:
> >> After changing this way, the native tools can be shared with
> >> different buildings.
> >
> > They get shared even now. I have my TM
Guo Hongruan wrote:
> After applying my patch, all everything built based on uclibc will be
> placed in some directories different with glibc,eglibc. The stamps will
> be placed in ${TMPDIR}/stamps/${LIBC}, the package data will be placed
> in ${TMPDIR}/pkgdata/${LIBC} and so on. So you can see, wh
I'm running the latest (development) BeagleBoard image. I can't
seem to get FireFox to render fonts correctly. If you visit this
page http://www.w3schools.com/css/css_font.asp, it shows the
various font families, etc. However, when I run it on the
BeagleBoard, all I get is the default font, wha
On Thu, Jan 14, 2010 at 10:02:57AM +0100, Frans Meulenbroeks wrote:
> I suggest to review the rules;. E.g. this one:
> # This should all be on one line and you should leave an empty line
> before any detailed commit information.
> Nice, but if you use git commit and enter your message empty lines a
在 Fri, 15 Jan 2010 03:53:01 +0800，Khem Raj 写道:
On (14/01/10 17:19), Guo Hongruan wrote:
After changing this way, the native tools can be shared with
different buildings.
They get shared even now. I have my TMPDIR = /scratch/oe/build and
DEPLOY_DIR = ${TMPDIR}/deploy/${LIBC}
I share the nati
hi,
every time I build the illume image I've the following failures:
First failure:
--
The first failure is about libefso and its deps,it has missing includes
and so it fails,long time ago I tried to fix it but at a point I
abandonned,so is it ok to remove the following from illume-im
This is version 0.6.9 of wpa-gui (Qt4), not the old one. If you think the
package should be named qpa-gui-qt4, please tell me.
The stylesheet is made for SHR only as the application does not fit the screen
otherwise (font way to big).
Cheers,
Christian
diff --git a/recipes/wpa-supplicant/wpa-
After some conf changes I get unknown device sda - but I look at kernel
config seems all is ok
* Khem Raj [Thu, 14 Jan 2010 12:25:41 -0800]:
On (14/01/10 09:45), Martyn Welch wrote:
> Perepelica Alexander wrote:
> > When I try boot image in qemu I see
> > booting kernel ... and nothing.
> >
D
On (14/01/10 09:45), Martyn Welch wrote:
> Perepelica Alexander wrote:
> > When I try boot image in qemu I see
> > booting kernel ... and nothing.
> >
Did you set the console properly. i.e. -append "console=ttyS0" on qemu
invocation ?
___
Openembedded-d
On (14/01/10 11:49), Cliff Brake wrote:
> On Thu, Jan 14, 2010 at 8:35 AM, Philip Balister wrote:
> > On 01/13/2010 10:00 AM, Cliff Brake wrote:
> >> So what is the path forward on this issue?
> >
> > Try the top of the official u-boot repo, not the TI one. I keep meaning to
> > try this, but am n
On (14/01/10 17:19), Guo Hongruan wrote:
> After changing this way, the native tools can be shared with
> different buildings.
They get shared even now. I have my TMPDIR = /scratch/oe/build and
DEPLOY_DIR = ${TMPDIR}/deploy/${LIBC}
I share the native tools all the time
-Khem
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-01-10 15:45, Robert P. J. Day wrote:
>
> later today, i'll take another shot at building the BB-demo-image.
> based on whatever gets "git pull"ed at the time, is there any
> still-known breakage? in my case, for f12 since i know full well tha
On Thu, Jan 14, 2010 at 8:35 AM, Philip Balister wrote:
> On 01/13/2010 10:00 AM, Cliff Brake wrote:
>> So what is the path forward on this issue?
>
> Try the top of the official u-boot repo, not the TI one. I keep meaning to
> try this, but am not getting to it.
Not much better -- guess I'm simp
Acked-By: Michael 'Mickey' Lauer
--
:M:
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Am Donnerstag, den 14.01.2010, 09:47 -0500 schrieb Robert P. J. Day:
> as i'm currently playing with python 3 but also digging my way thru
> bitbake, are there any obvious incompatibilities between bitbake/OE
> and python 3? i'm assuming there is absolutely no guarantee that
> bitbake/OE will run
On Thursday 14 January 2010 15:47:35 Robert P. J. Day wrote:
> as i'm currently playing with python 3 but also digging my way thru
> bitbake, are there any obvious incompatibilities between bitbake/OE
> and python 3? i'm assuming there is absolutely no guarantee that
> bitbake/OE will run under
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It received 2 Acks, no NAKs, works well in the field: it's applied now
On 12-01-10 14:54, Koen Kooi wrote:
> Hi,
>
> What's your opinion on attached (untested) patch? If there's some
> consensus that this is a step in the right direction I'll create
But I've a basic linux system runing on my board then still I've any need of
bitbaiking
console-iamge?
if not then what procedure I should adopt for porting ossie.
can bitbaking only ossie related files will work or any other way?
saleh
On 01/14/2010 09:46 AM, saleh usman wrote:
>
> What co
On 01/14/2010 09:46 AM, saleh usman wrote:
What console-image actually does.There is a little information about it in
openembedded manual.
Read the bb file. Basically, it is an image that provides a basic linux
system with most of the familiar command line utilities.
Philip
Saleh
as i'm currently playing with python 3 but also digging my way thru
bitbake, are there any obvious incompatibilities between bitbake/OE
and python 3? i'm assuming there is absolutely no guarantee that
bitbake/OE will run under python 3.
rday
--
What console-image actually does.There is a little information about it in
openembedded manual.
Saleh
_
Windows Live Hotmail: Your friends can get your Facebook updates, right from
Hotmail®
later today, i'll take another shot at building the BB-demo-image.
based on whatever gets "git pull"ed at the time, is there any
still-known breakage? in my case, for f12 since i know full well that
other distros sometimes have no problem.
before i try to build, i'll clean e2fsprogs, mplayer
Hi
I've built helloworld and its exucatble is runing on my board.Since
linux is runnig on my board so I don't have any need of u-boot,kernel
and file systme then still I've to build console-iamge?
I want to port OSSIE(open source SCA imlementation embeddeb) on Davinci SOC and
executable of hell
On 01/14/2010 09:12 AM, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-01-10 14:52, Michael 'Mickey' Lauer wrote:
Am Donnerstag, den 14.01.2010, 10:14 +0100 schrieb Koen Kooi:
NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
people to catch up to, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-01-10 14:52, Michael 'Mickey' Lauer wrote:
> Am Donnerstag, den 14.01.2010, 10:14 +0100 schrieb Koen Kooi:
>> NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
>> people to catch up to, and it messes up the docs on the subject.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-01-10 14:48, Rolf Leggewie wrote:
> Koen Kooi wrote:
>> NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
>> people to catch up to, and it messes up the docs on the subject.
>
> With respect to "needless", the reasons for the
On 01/14/2010 04:02 AM, Frans Meulenbroeks wrote:
Commit messages were mentioned. It should be clear from reading the
commit message what the change applies to and why its necessary. The TSC
will start naming and shaming people making lousy commit messages and
reserve the right to impose sanctio
在 Thu, 14 Jan 2010 06:22:17 +0800，Richard Purdie
写道:
The QA issues are not something the TSC can really "rule" on. Yes
testing is good but we have no hardware or human resources we can assign
to this. Where a regression is identified as being from a particular
commit, it is expected the regre
Am Donnerstag, den 14.01.2010, 10:14 +0100 schrieb Koen Kooi:
> NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
> people to catch up to, and it messes up the docs on the subject.
Could you expand on that reason? I find the patch quite a useful
refactoring. If we don't allow pa
Koen Kooi wrote:
> NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
> people to catch up to, and it messes up the docs on the subject.
With respect to "needless", the reasons for the change were given in
this thread. Please revisit the discussion.
And in any case, the tremend
On 01/13/2010 10:06 AM, gagan singh wrote:
Hi Phil,
Thanks for the response. So you recon Asynchronous
Multi-Processing (AMP) concept is better suited in beagle board configuration.
If so what exactly I have to do in angstom to get such thing working.
regards
Read up on dspli
On 01/13/2010 10:00 AM, Cliff Brake wrote:
On Thu, Dec 24, 2009 at 6:56 PM, Philip Balister wrote:
On 12/24/2009 12:28 PM, Khem Raj wrote:
On Thu, Dec 24, 2009 at 1:36 AM, Koen Kooi
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NAK, uboot_git.bb should fetch from git.
It was int
With qt4 providers set only in compatibility-providers-conf and default
versions (no P_V for qt4 packages).
I got lots of bitbake errors like this:
NOTE: Runtime target 'qt4-x11-free-gles' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qt4-x11-free-gles',
'virtual/egl
I am going to be submitting revisions to the CUPS recipes, including a
new version, 1.4.2.
I also have revisions for Gutenprint, and GS.
This email is primarily a test, as prior attempts to post have been bounced.
Regards,
Jay Snyder
___
Openembedd
Hi guys,
I want to do incremental building when openembedded recipe changes. But
I found that when adding INHERIT += "rm_work" in local.conf, bitbake
always building lots of packages which recipes never were changed. I
verified it with the newest openembedded
667b7cb389a4cd8677fe5272f16c
On Wed, Jan 13, 2010 at 10:22:17PM +, Richard Purdie wrote:
> Patches were mentioned. The TSC is encouraging patches to have headers
> with information about who wrote them, when, why and if taken from
> somewhere else, where this was.
Debian has a draft standard for this:
http://dep
Perepelica Alexander wrote:
> When I try boot image in qemu I see
> booting kernel ... and nothing.
>
I'm afraid I have no experience with using qemu, so I don't think I can
really make any suggestions at this point.
Martyn
>
> 14.01.2010 10:59, Martyn Welch пишет:
>> Perepelica Alexander wrote:
Hello,
>> At a guess (as you haven't provided any specifics) I'd guess that you
>> need to look at the kernel configuration.
right
Setting DEFAULT_PREFERENCE_yourmachine = "1" is not enough: you have
to provide a specific defconfig for your machine, in a subdir of
linux-2.6.32+2.6.33-rc4
Actually
When I try boot image in qemu I see
booting kernel ... and nothing.
14.01.2010 10:59, Martyn Welch пишет:
Perepelica Alexander wrote:
Thank you, Martyn!
I remove my changes from linux_2.6.32+2.6.33-rc3.bb and I build was
successful but don't boot with image :( - all hangs
At what p
After changing this way, the native tools can be shared with different
buildings.
在 Thu, 14 Jan 2010 17:14:53 +0800，Marcin Juszkiewicz
写道:
Dnia czwartek, 14 stycznia 2010 o 08:55:39 Guo Hongruan napisał(a):
* Append ${LIBC} to CACHE, STAMP, WORKDIR, STAGING_DIR and CROSS_DIR
defination,
Dnia czwartek, 14 stycznia 2010 o 08:55:39 Guo Hongruan napisał(a):
> * Append ${LIBC} to CACHE, STAMP, WORKDIR, STAGING_DIR and CROSS_DIR
> defination, so that package building with different libc will not bother
> each other.
How does it differ from TMPDIR = "tmp/${LIBC}/" setting in local.con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
people to catch up to, and it messes up the docs on the subject.
On 14-01-10 01:38, Rolf Leggewie wrote:
> diff --git a/classes/image.bbclass b/classes/image.bbclass
> index ab58031.
Perepelica Alexander wrote:
> Thank you, Martyn!
> I remove my changes from linux_2.6.32+2.6.33-rc3.bb and I build was
> successful but don't boot with image :( - all hangs
At what point does it hang?
At a guess (as you haven't provided any specifics) I'd guess that you
need to look at the kerne
Richard, Thanks for making the minutes available.
A short reaction on a few things:
>
> Current Issues
> ==
>
> We did discuss the IMAGE_BOOT issue. We decided that weak defaults (?=)
> in the class where the variables are used is a good thing and that the
> current structure is pretty
47 matches
Mail list logo
