I had the same problem.
. /usr/local/openmoko/arm/environment-setup
. /usr/local/openmoko/arm/setup-env
Fixed it.
Kd wrote:
>
> I am not using Ubuntu 8.10, I manually installed libtool again, but it is
> again giving me the error.
> The problem is libtool is accessing "/usr/lib" for that fil
On Sun, 01 Feb 2009 06:31:10 +1100, Philip Rhoades
wrote:
> People,
>
>
> Graeme Gregory wrote:
>> Christopher Friedt wrote:
>>> Just to ensure that I am on the right track, where is most of the
>>> current work happening? org.openmoko.dev ? FSO ? A different branch ?
>>>
>>
>> Must development
#2216: Call = there is no sound
--+-
Reporter: octavsly | Owner: openmoko-devel
Type: defect| Status: new
Priority: high | Milestone: Om200
People,
Graeme Gregory wrote:
> Christopher Friedt wrote:
>> Just to ensure that I am on the right track, where is most of the
>> current work happening? org.openmoko.dev ? FSO ? A different branch ?
>>
>
> Must development is now occurring in OE upstream. AFAIK the
> org.openmoko.* branches are
I guess i should also ask whether or not it's stilll necessary to use
OpenMoko's branch of bitbake, like the wiki suggests.
Should I use bitbake-om or can I just use whatever is mainstream and stable?
C
On Sat, Jan 31, 2009 at 1:17 PM, Christopher Friedt
wrote:
> Ah - I see
>
> Originally I was
Lars-Peter Clausen wrote:
> I have a git repository with a cleaned up version of graemes xorg
> driver located at [1].
> Its quite stable(survied a 1 hour `x11perf -all`) and exa acceleration
> is working, but you'll have to apply [2] to your xserver to get it
> working.
Woah! Fantastic work.
Ah - I see
Originally I was following the Developer's Guide on the OpenMoko
Wiki... it seems to be a bit outdated because it still suggests to
synchronize with git.openmoko.org.
Apparently we're all in the same boat - who has time to update documentation !?
C
On Sat, Jan 31, 2009 at 12:40 PM, G
#2216: Call = there is no sound
--+-
Reporter: octavsly | Owner: openmoko-devel
Type: defect| Status: new
Priority: high | Milestone: Om200
Christopher Friedt wrote:
> Just to ensure that I am on the right track, where is most of the
> current work happening? org.openmoko.dev ? FSO ? A different branch ?
>
Must development is now occurring in OE upstream. AFAIK the
org.openmoko.* branches are now all legacy and not developed any more.
Thanks for the tips again guys -
I've checked out andy-tracking already so it's just a matter of syncing.
Also I had been using OE to build all of my binaries and filesystems
using the org.openmoko.stable branch. Stable was giving me
(ironically) several build errors, which i had submitted trac t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Currently we have two patchsets - one generic OpenWrt-patchset for
| 2.6.28-kernels (located here:
|
https://svn.openwrt.org/openwrt/trunk/target/linux/generic-2.6/patches-2.6.28/),
| some little s3c46xx-re
Wolfgang Spraul wrote:
> > Michael,
> >
>> >> No we take vanilla 2.6.28 and apply the diff between 2.6.28 and andy-
>> >> tracking.
>> >> We can also apply additional patches, but we don't for now.
> >
> > hmm. Andy is the expert here, maybe you ask him over on the kernel list.
> > Why pin it to
Michael,
> That's the way buildroot works.
>
>> I'd say take it to the kernel list and ask Andy.
>
> No. We're not going to change the way openwrt works.
OK understood (and I never asked for that, BTW, I was just curious to
understand why you went this route).
The good news is that the kernel i
On Saturday 31 January 2009 17:32:53 Wolfgang Spraul wrote:
> Michael,
>
> > No we take vanilla 2.6.28 and apply the diff between 2.6.28 and andy-
> > tracking.
> > We can also apply additional patches, but we don't for now.
>
> hmm. Andy is the expert here, maybe you ask him over on the kernel
Michael,
> No we take vanilla 2.6.28 and apply the diff between 2.6.28 and andy-
> tracking.
> We can also apply additional patches, but we don't for now.
hmm. Andy is the expert here, maybe you ask him over on the kernel list.
Why pin it to an old andy-tracking version, and then manually base i
#2216: Call = there is no sound
--+-
Reporter: octavsly | Owner: openmoko-devel
Type: defect| Status: new
Priority: high | Milestone: Om200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
Graeme Gregory wrote:
> Lars-Peter Clausen wrote:
>> I have a git repository with a cleaned up version of graemes xorg
>> driver located at [1]. Its quite stable(survied a 1 hour
>> `x11perf -all`) and exa acceleration is working, but you'll have
On Saturday 31 January 2009 04:41:46 Wolfgang Spraul wrote:
> Mirko and others that helped here,
> this is great stuff, congratulations!
>
> > - kernel (2.6.28) is building and booting (merging the Openmoko and
> > OpenWrt patchsets, whereof one (and that's not ours ;)) consists of
> > either
Lars-Peter Clausen wrote:
> I have a git repository with a cleaned up version of graemes xorg
> driver located at [1].
> Its quite stable(survied a 1 hour `x11perf -all`) and exa acceleration
> is working, but you'll have to apply [2] to your xserver to get it
> working.
> What still has to be done
19 matches
Mail list logo
