Rod Whitby (MokoMakefile author) moves on to start WebOS Internals

http://www.rwhitby.net/blog/webos-internals/palm-pre-lands-in-australia.html It is with some sadness that I must say goodbye to the OpenMoko community, and move on to new things. My dream of an OpenMoko phone with a hardware keyboard to replace my aging Treo 650 was never realised, and you al

Re: Question about MokoMakeFile

Al Johnson wrote: > On Saturday 14 March 2009, Andreas Willich wrote: >> Hi List >> >> >> Some time ago it was possible to build a single package and it's >> dependencies with the MokoMakeFile with make >> build-package-"packagename". >> >> With the current Makefile this command is not valid anymor

Re: FSO fails and fails

Daniel Spies wrote: > I knew about downloads.freesmartphone.org, but as you can see there is no > build after 18th Jan. and one build for M5. > downloads.openmoko.org has got the images indeed, thanks! Thanks for reporting it - I've been concentrating on FSO milestone5 feeds and updated images (h

Re: FSO fails and fails

Daniel Spies wrote: > I wonder if anyone would be interested in daily automated builds as I build > on my root server anyway? > I could also do some other builds if s/o needs it... There are already FSO automated builds on downloads.freesmartphone.org (maintained by me) and downloads.openmoko.org

Re: Openmoko Autobuilder

Angus Ainslie wrote: > The Openmoko autobuilder is back online. It is generating > images for gta01 and gta02 devices. ... > For those interested in improving or commenting on the build > scripts used to generate the unstable and experimental images > they can be found here: > > http://downloads

Re: Location of official Openmoko git repository (Was: Re: Xorg / Glamo ?)

Angus Ainslie wrote: > On Thu, 2009-02-05 at 09:29 +1030, Rod Whitby wrote: >> Surely there is someone in OM who is building the official "next" image >> today, and that person can immediately share their build configuration? >> > > Yes there is Rod. I am

Re: Location of official Openmoko git repository (Was: Re: Xorg / Glamo ?)

Marek Lindner wrote: > On Wednesday 04 February 2009 20:17:54 Rod Whitby wrote: >> What I haven't seen yet is a message which says "Openmoko has officially >> completed the migration to git.openembedded.net, > > I'm confident that the subject "

Re: Location of official Openmoko git repository (Was: Re: Xorg / Glamo ?)

Marek Lindner wrote: > On Wednesday 04 February 2009 09:04:57 Rod Whitby wrote: >> I have not had official word from Openmoko that they have moved from >> git.openmoko.org to git.openembedded.org >> >> If Openmoko has officially moved, then please just tell me the new gi

Re: Xorg / Glamo ?

Christopher Friedt wrote: > I was just checking out another thread, between Rod & Graeme, and the > 'official' changeover to OpenEmbedded Git is still underway. > > That being said, it's probably still safe to update most parts of the > wiki. For example, I can rearrange the OpenEmbedded page slig

Re: Xorg / Glamo ?

Angus Ainslie wrote: > Hi Rod, > > On Wed, 2009-02-04 at 12:36 +1030, Rod Whitby wrote: >>> Must development is now occurring in OE upstream. AFAIK the >>> org.openmoko.* branches are now all legacy and not developed any more. >> Graeme, >> >> Is

Xorg / Glamo ?

> Must development is now occurring in OE upstream. AFAIK the > org.openmoko.* branches are now all legacy and not developed any more. Graeme, Is this official? Who is the official Openmoko distribution manager today? Is that you? Where was the official announcement to developers of the move f

Re: Xorg / Glamo ?

Thomas has one opinion about MokoMakefile. It is not the only opinion held by various Openmoko and third-party developers. It is true that the delta between the normal OE build process, and the Openmoko build process is progressively getting smaller. However, there are many people who find the n

Location of official Openmoko git repository (Was: Re: Xorg / Glamo ?)

[Subject changed to reflect the actual conversation] Juan Alberto Aranda Alvarez wrote: > Harald Welte wrote: > >> So if somebody decides that git.openmoko.org is no longer used but instead >> upstream OE, then whoever makes that decision: Please update the wiki to >> reflect that change. > > So

Re: Xorg / Glamo ?

Thomas Gstädtner wrote: > On Wed, Feb 4, 2009 at 12:57 AM, Juan Alberto Aranda Alvarez > wrote: >> So basically MokoMakefile is broken? > > It not only is broken, it also is unmaintained. I suggest you to use > plain Openembedded, makes everything much easier. What makes you think MokoMakefile i

Re: FSO and Paroli

c_c wrote: > Hi, > I have quite a few suggestions and questions. > > Questions > Can't we have a daily build? FSO has continuous incremental builds at downloads.freesmartphone.org/fso-unstable -- Rod ___ devel mailing list devel@lists.openmoko.org h

Re: Bitbake - is it possible to specify which fetcher to use?

Use git://.;protocol=http: -- Rod -Original Message- From: Leonti Bielski Date: Saturday, Jan 10, 2009 11:01 pm Subject: Bitbake - is it possible to specify which fetcher to use? To: devel@lists.openmoko.org Hello! >I'm trying to build kernel using bitbake. >I'm behind proxy, so

Re: Whats up with downloads.freesmartphone.org?

digger vermont wrote: > On Fri, 2009-01-02 at 19:03 +1030, Rod Whitby wrote: >> The README on downloads.freesmartphone.org will point you to the build logs, >> from where you can determine which OE packages are causing the builds to >> fail. Then you can raise bug reports f

Re: Whats up with downloads.freesmartphone.org?

Mark Chandler wrote: > Rod - may I ask what's wrong with your moko? If it's a h/w issue, I'd be > glad to send you either my 1973 or FreeRunner. I have a pre-release US FreeRunner which, irrespective of having an externally fully charged battery, only decides to turn on once in between 50 and 200

Re: Whats up with downloads.freesmartphone.org?

digger vermont wrote: > On Fri, 2009-01-02 at 19:03 +1030, Rod Whitby wrote: >> The README on downloads.freesmartphone.org will point you to the build logs, >> from where you can determine which OE packages are causing the builds to >> fail. Then you can raise bug reports f

Re: Whats up with downloads.freesmartphone.org?

Erland Lewin wrote: > 2009/1/2 Rod Whitby mailto:r...@whitby.id.au>> > > The README on downloads.freesmartphone.org > <http://downloads.freesmartphone.org> will point you to the build > logs, from where you can determine which OE packages are causing the

Re: Whats up with downloads.freesmartphone.org?

The README on downloads.freesmartphone.org will point you to the build logs, from where you can determine which OE packages are causing the builds to fail. Then you can raise bug reports for those failures and when they are all fixed the images will be built again. Unfortunately, I don't have a

Re: status of projects.openmoko.org

Sean Moss-Pultz wrote: > On 12/16/08 Rod Whitby wrote: >> The closure of projects.openmoko.org is (IMHO) a step in the wrong >> direction, since it further fragments the openmoko developer resources >> and community. >> >> This action says "Openmoko d

Re: status of projects.openmoko.org

Marek Lindner wrote: > as discussed some weeks back Openmoko wants to reduce the time spent on other > things next to the phone. Part of that process is the shutdown of our > projects.openmoko.org server. In the past we spent considerable time and > effort > maintaining it. As many people notic

Re: When http://www.angstrom-distribution.org/unstable/sources/ is updated

Leonti Bielski wrote: > Hello! > I'm trying to build FSO for a couple of days by now with bitbake. > Now I'm stack on the freesmartphone.org stuff. > bitbake first tries to donwload sources from > ttp://www.angstrom-distribution.org/unstable/sources/ >

Re: Weekly Engineering News 41/2008

Wolfgang Spraul wrote: > Hi everybody, > back to the basics! > > That's the main news from Taipei last week. We decided to focus our > engineering on just the basics, even less eye candy: Robust kernel, > fast boot time, basic telephony with great audio quality, powerful > configuration from

Re: What should a community manager do?

Wolfgang Spraul wrote: > Rod, > >> It seems that access was granted sometime between then and now > > oh great, I'm happy to hear that. > Maybe we don't talk about it enough publicly: We have an 'admin trac' > issue tracker, that _EVERYBODY_ can use to send requests to the > Openmoko admins.

Re: FSO git - warning: remote HEAD refers to nonexistent ref, unable to checkout.

Leonti Bielski wrote: > Hello! I'm trying to checkout fso, to build it for developing. > I run: > git clone http://git.freesmartphone.org/fso-makefile common The command in the Makefile is: git clone git://git.freesmartphone.org/fso-makefile.git common (you're missing a .git on the end of the UR

Re: What should a community manager do?

Rod Whitby wrote: > (Wolfgang told the Openmoko admins > to give me svn and git access on the 22 Sept, and nothing has happened yet). I want to make a public retraction and apology on this point. It seems that access was granted sometime between then and now, but either I wasn't infor

What should a community manager do?

n repositories producing packages and images for four different distributions (targeted to four different use cases) using the same top-level build system and ending up in common official feeds on a single official download site. See the following documents for more details: http://w

Re: FDOM=OM was (omview & community repository)

Holger Freyther wrote: > On Monday 06 October 2008 00:16:13 Rod Whitby wrote: > >> It is a negative reflection on OM for not taking the things you have >> fixed and fixing them at the source. > > Well, I'm not aware of any bug reports mentioning resolv.conf. Could yo

Re: FDOM=OM was (omview & community repository)

If FDOM was something you could "ipkg install" on another distro, then I would not call it a separate distribution. As it stands today, it *is* a separate distribution. And you cannot deny that there are things done in FDOM which are simply there becuase they have not been fixed in the official O

Re: omview & community repository

Tick Chen wrote: > There is a sample local.conf in attached file. > PREFERRED_VERSION_glib-2.0 = "2.16.1" Why is this not in the standard conf/distro/openmoko.conf distribution configuration file? Why are you recommending each individual builder put this in their own local.conf file? This is o

Re: omview & community repository

Tick Chen wrote: > For OE stuff, > you can do this. > make sure you have 20Gb+ disk space, and a fast > computer, with ubuntu or debian (I only tested these two.) > $ cd ~/;mkdir moko;cd moko; > $ echo "export OMDIR=\"$HOME/moko\"" > setup-env > $ echo "export BBPATH=\"${OMDIR}/build:${OMDIR}/op

Re: unable to read from Sandisk 8Gb SD

Sander van Grieken wrote: > On Wednesday 24 September 2008 23:42:13 Rod Whitby wrote: >> Sander van Grieken wrote: >>>> Sander van Grieken wrote: >>>>>>> That may be, but despite that I need a daily package for kernel I can >>>>>>> p

Re: unable to read from Sandisk 8Gb SD

Holger Freyther wrote: > On Wednesday 24 September 2008 09:08:57 Rod Whitby wrote: >> Andy Green wrote: >>> It used to be that our kernel packages followed our stable kernel git >>> daily. >>> >>> But the hash on that one tells it is stuck at Aug 2

Re: unable to read from Sandisk 8Gb SD

Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > |> That may be, but despite that I need a daily package for kernel I > |> can point people to. Actually blocking current stable kernel from > |> users by not packaging it, which se

Re: unable to read from Sandisk 8Gb SD

Sander van Grieken wrote: >> Sander van Grieken wrote: > That may be, but despite that I need a daily package for kernel I can > point people > to. > Actually blocking current stable kernel from users by not packaging it, > which seems > to > be the case, is completely

Re: unable to read from Sandisk 8Gb SD

Sander van Grieken wrote: >>> That may be, but despite that I need a daily package for kernel I can point >>> people to. >>> Actually blocking current stable kernel from users by not packaging it, >>> which seems to >>> be the case, is completely backwards. >> That may be the case, and you defint

Re: unable to read from Sandisk 8Gb SD

>That may be, but despite that I need a daily package for kernel I can point >people to. Actually blocking current stable kernel from users by not >packaging it, which seems to be the case, is completely backwards. That may be the case, and you defintely should be able to point experienced alp

Re: unable to read from Sandisk 8Gb SD

Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Andy Green wrote: > |> It used to be that our kernel packages followed our stable kernel git > daily. > |> > |> But the hash on that one tells it is stuck at Aug 23 patchlevel...

Re: unable to read from Sandisk 8Gb SD

Andy Green wrote: > It used to be that our kernel packages followed our stable kernel git daily. > > But the hash on that one tells it is stuck at Aug 23 patchlevel... Yet another reason why the openmoko autobuilder configuration should be documented and published somewhere. As an example, the p

Re: ANN: downloads.freesmartphone.org

Fredrik Wendt wrote: > lör 2008-09-20 klockan 13:55 +0200 skrev Michael 'Mickey' Lauer: >> Please see the readme on the frontpage of downloads.freesmartphone.org for >> more information (e.g. which sources make up these images). > > The timestamps on the images produced varies a lot: > > 19-Sep-

Re: MonoMakefile: how to build navit-svn instead of navit-0.0.4 ?

Harald Koenig wrote: > On Sep 12, Nicola Mfb wrote: > >> In my oe tree i have navit_cvs and not navit_svn, > > and can you start a build for navit_cvs (I'd guess for you > it's "make build-package-navit-cvs" then?) Everything after the '_' in the bitbake recipe name is part of the version num

Re: How to restore environment after cross-compiling.

The setup-env does not make any permanent changes to you machine. It's effect is limited to the shell in which it is run and any ancestors of that shell. -- Rod -Original Message- From: SCarlson <[EMAIL PROTECTED]> Date: Thursday, Sep 11, 2008 8:55 am Subject: How to restore environment

Re: Testing repository and Openmoko-base-image

Holger Freyther wrote: > On Monday 08 September 2008 00:55:04 Rod Whitby wrote: >> Is there a plan for an upgrade path from org.openmoko.asu.stable to >> org.openmoko.dev (or something branched off of it)? > > Well, it shall be supported. John filed a ticket to veri

Re: Testing repository and Openmoko-base-image

Holger Freyther wrote: > On Sunday 07 September 2008 13:54:47 Rod Whitby wrote: > >> This configuration not only fails to build, but fails to even parse: >>> ERROR: '['/home/moko/openembedded/packages/dbus/dbus-native_1.2.1.bb']' >>> RDEPENDS/RR

Re: Testing repository and Openmoko-base-image

ed/packages/xorg-xserver/xserver-kdrive_1.3.0.0.bb). > This usually means one provides something the other doesn't and should. Even if this build completes, it won't match the configuration for the openmoko-base-image that you stated in y

Rumoured death of projects.openmoko.org

Carsten Haitzler (The Rasterman) rumoured: > as such - projects.om.org is desired to go as its gforge base is a bit > abandoned, and the solutions bandied about have been "use google code or > sourceforge etc."... so as the solution is to use someone elses infra. i know > i'll use my own :) Looks

Re: bitbake fso-image: git://git.freesmartphone.org/usaged.git hung up unexpectedly

Russell Sears wrote: > Thanks for producing the feeds for FSO, and FsoMakefile! There was a > great need for such a thing. Thanks for the kind words. > However, I think FsoMakefile would be a poor solution for me. I'd like > to make sure I'm not too far off base, since there's little > docum

Re: OpenMoko Neo 1973

, you should >> get signals after a while. Please see how it's used in the Zhone UI. >> That reminds me that we need to add more examples. Daniel? > > no, sorry that will not work yet. See > http://trac.freesmartphone.org/ticket/49 for progress. Thanks to Rod > Whitb

Re: bitbake fso-image: git://git.freesmartphone.org/usaged.git hung up unexpectedly

Russell Sears wrote: > Do I want to do this: > > wget http://www.openembedded.org/snapshots/OE.mtn.bz2 ... > bitbake fso-image > > or this: > > git init > git pull git://git.openembedded.net/org.openembedded.dev.git > bitbake fso-image The latter, but see below for an (IMHO) easier way to set i

Re: Testing and Unstable feeds for the FSO distribution are now available

Cédric Berger wrote: > What is different from what was on buildhost.openmoko ? (and 2008.8 feeds ?) Dunno. No-one has ever precisely specified what buildhost.openmoko.org actually builds, so we have no way of knowing what is different ... I have heard from various people on IRC that buildhost.op

Testing and Unstable feeds for the FSO distribution are now available

is server, you should use a Debian Lenny host operating system, with the host package configuration as specified in the sources.list and dpkg-list.txt files in the server-config directory. Then copy the Makefile and 'common' directory to your build area. Read the Makefile for furt

Re: openmoko-terminal2 & FSO

Sébastien BRICE wrote: > hello > I can't compile the reimplemented in vala code of the openmoko-terminal2 > as attempting to build FSO, always the same log (take a glance below pliz) > i use mokomakefile set with: > OM_GIT_SITE := git.openembedded.net > OM_GIT_REPO := org.openembedded.dev > OM_GIT

Re: mokomakefile && org.openmoko.asu.dev => libcairo.so: undefined reference to `pixman_format_supported_destination'

Timo Juhani Lindfors wrote: > Rod Whitby <[EMAIL PROTECTED]> writes: >> You probably need moko-autorev and fso-autorev in local.conf - it >> looks like sane-srcrevs is not being kept up to date by the OM >> developers. Actually, I get the same error with those files i

Re: BT headset on Qtopia how?

Jim Morris wrote: > Without full schematics showing how the BT chip is connected to the Codec, > and without the BT chips > docs, I cannot proceed. Depending on whether the BT chip puts out PCM or I2S > it may or may not work > according to Wolfson, unless external circuitry has been added. Do

Re: mokomakefile && org.openmoko.asu.dev => libcairo.so: undefined reference to `pixman_format_supported_destination'

Timo Juhani Lindfors wrote: > I tried to build org.openmoko.asu.dev using the following steps in a > 64-bit debian unstable chroot: > > sudo aptitude install subversion build-essential help2man diffstat texi2html > texinfo cvs gawk zip unzip cogito libncurses5-dev zlib1g-dev libssl-dev > libgtk2

Re: glibc build fails

Graeme Gregory wrote: > On Tue, 05 Aug 2008 12:12:53 +0930 > Rod Whitby <[EMAIL PROTECTED]> wrote: > >> Yaroslav Halchenko wrote: >>> Dear Dev'ers, >>> >>> trying to build up-to-date image using MokoMakefile >>> >>> fails to

Re: glibc build fails

TED]> Date: Thursday, Aug 7, 2008 5:44 am Subject: Re: glibc build fails To: Graeme Gregory <[EMAIL PROTECTED]> CC: Rod Whitby <[EMAIL PROTECTED]>, devel@lists.openmoko.org so the problem might be in some detection being incorrect -- it seems >that -lgcc_eh is not needed (at least t

Re: glibc build fails

Yaroslav Halchenko wrote: > Dear Dev'ers, > > trying to build up-to-date image using MokoMakefile > > fails to build glibc with problem listed below. apparently is missing > -L/home/yoh/nobackup_openmoko/sdk/build/tmp/work/armv4t-angstrom-linux-gnueabi/gcc-cross-intermediate-4.1.2-r18/gcc-4.1.2/b

Re: Kernel package and modules

Andy Green wrote: > Somebody in the thread at some point said: > > | |> I would like to propose we radically simplify how we deal with > | |> modules, simply by pushing all the ones we create into the main > | |> kernel package. This has one disadvantage, size on storage, but > > | |> What do the

Re: [ Test Report : 2008.08.01 ]

Yorick Moko wrote: > On Fri, Aug 1, 2008 at 1:55 PM, Wendy <[EMAIL PROTECTED]> wrote: >> The images: >> Kernel: >> - 20080723-asu.stable-uImage.bin >> Root file system: >> - 20080729-asu.stable-rootfs.jffs2 >> - 20080730-asu.stable-rootfs.jffs2 >> - 20080731-asu.stable-rootfs.jffs2 >> - 200808

Re: daily-feed vs. SRCREV

Holger Freyther wrote: > On Wednesday 30 July 2008 16:27:17 Rod Whitby wrote: >> Julian Chu wrote: > >>>Actually, the buildhost didn't build ASU branch at all. >>> We did that work on another machine in Taipei. >> Hmm - so you *don't* want the pub

Re: daily-feed vs. SRCREV

Julian Chu wrote: > On Wed, Jul 30, 2008 at 10:46:34PM +0930, Rod Whitby wrote: >> Thanks for the explanation. I would humbly suggest that buildhost only >> build the asu branches then, so that you focus user testing by the >> public on the development that is intended to

Re: daily-feed vs. SRCREV

Holger Freyther wrote: > On Wednesday 30 July 2008 02:23:04 Rod Whitby wrote: > >> Why they do that, which is effectively pushing completely untested >> builds onto thousands of end-users, is beyond my understanding. > > For the ASU branch we do the following: >

Re: daily-feed vs. SRCREV

Joachim Breitner wrote: > Why does the build host at > http://buildhost.openmoko.org/daily-feed/armv4t/ > not contain packages from webkit r35062 when this is, according to > http://git.openmoko.org/?p=openmoko.git;a=blobdiff;f=conf/distro/include/sane-srcrevs.inc;h=05538c244f6397f1a272deabbb7c6c19

Re: mokomakefile local.conf setting?

Jim Morris wrote: > Rod Whitby wrote: >> MokoMakefile (MM) is simply a convenience wrapper around the Openmoko >> (OM) fork of OpenEmbedded (OE) which sets up your OE environment in a >> standard reproducible manner and runs Bitbake (BB) with specific >> arguments

Re: mokomakefile local.conf setting?

ns Bitbake (BB) with specific arguments matching commonly requested build actions. So if MM is able to complete the build of an OM image for you, then you've already used OE to BB thousands of recipes. -- Rod Whitby -- MokoMakefile Author __

Re: mokomakefile local.conf setting?

Jim Morris wrote: > Unfortunately I have not had much success getting OE to build either and so > far have been unable to > contribute to development. > > I'll try to report the bug, but there are several bugs I have run into that > have been reported > several months ago and have not been fix

Re: mokomakefile local.conf setting?

Jim Morris wrote: > Thanks Guys. > I added it to two places in the Wiki, just after where it tells you to do > make setup, and in the > useful make targets sections. Thanks Jim. > Now I just need it to get through a build on my Ubunto Hardy system, seems to > crap out building the > compiler,

Re: mokomakefile local.conf setting?

Alessandro Sappia wrote: > if you read MokoMakefile > you'll find a "setup-machine-freerunner" make target > > simply apply > $ make setup > $ make setup-machine-freerunner > ... go on ... > > I noticed that docs is a Work in Progress ^^ Indeed. How are you going to help that situation? The ma

Re: mokomakefile local.conf setting?

Jim Morris wrote: > Just getting started using Mokomakefile after failing to get OE to build > following their instructions. > > One thing I notice is the default make setup sets > > MACHINE = "om-gta01" > > I am building for freerunner gta02, so should this be set to > > MACHINE = "om-gta02"