On Saturday 19 July 2008 22:46:12 Mike (mwester) wrote:
> Holger Freyther wrote:
> > Guys, please don't make up "issues" were there are none. I can't stand
> > this bikeshedding. The old thread was about looking at the software we
> > could provide and has known security issues. If you are not inte
Ok I *DID* read through the Wiki, and Googled for this error, no luck.
I get this error some way into building with mokomake...
|
/aux/Stuff/openmokodev/mokomake/build/tmp/cross/bin/arm-angstrom-linux-gnueabi-as:
unrecognized
option `-Qy'
| make[2]: *** [g++spec.o] Error 1
Trying to do make o
It appears that the u-boot images built with Openembedded and
published on buildhost.openmoko.org/daily/... are still built from a
bitbake recipe that uses the upstream (www.denx.de) git repository + a
patch series from Openmoko's svn repository (indicated by the
"+svnr4297" in the filename
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.
Now I just need it to get through a build on my Ubunto Hardy system, seems to
crap out building the
compiler, I'll investigate further and report back.
Can you guide me to remove myself from your list? I have try several ways, but
no effect was returned.
_
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
Can you guide me to remove myself from your list? I have try several ways, but
no effect was returned.
> Date: Sun, 20 Jul 2008 11:24:41 +0930> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> Subject: Re: mokomakefile local.conf setting?> CC:
> devel@lists.openmoko.org> > Alessandro Sappia wr
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
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"
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 ^^
On Sun, Jul 20, 2008 at 2:53 AM, Jim Morris <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Just getting starte
Hi,
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"
This is not mentioned anywhere I
Hi,
I have put my copy of the openmoko git repository on
http://git.nomeata.de/?p=openmoko.git;a=summary
with that patches that I have submitted and are not yet applied, or that
I wrote for personal use but that might be interesting for others as
well.
Do other people here have their repositorie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The facts are:
~ - We didn't take care about partitioning permissions by users anywhere
really, it's all root
~ - You can login as root randomly up until now anyway, dropbear I've
seen in images is happy
On Saturday 19 July 2008 22:12:49 frang (moko-devel) wrote:
> Those links are interesting, thank you. I've also been poking at things
> more. I am, admittedly new to the phone space for coding, and I freely
> admit I'm just hacking for now. I find it helps me learn about things
> quickly, if org
Holger Freyther wrote:
> Guys, please don't make up "issues" were there are none. I can't stand this
> bikeshedding. The old thread was about looking at the software we could
> provide and has known security issues. If you are not interested in that then
> don't comment and please don't hijack
#1644: openmoko-browser2: no input fields can be used as keyboard is not
activated
--+-
Reporter: olberger | Owner: openmoko-devel
Type: defect| Status: new
Priority: normal| Milest
#1607: TS misalignment when in landscape mode
+---
Reporter: kenrestivo |Owner: openmoko-devel
Type: defect | Status: closed
Priority: highest |Milestone:
Componen
#1158: Charging stops even while connected
+---
Reporter: [EMAIL PROTECTED] |Owner: openmoko-devel
Type: defect | Status: new
Priority: high|
Those links are interesting, thank you. I've also been poking at things
more. I am, admittedly new to the phone space for coding, and I freely
admit I'm just hacking for now. I find it helps me learn about things
quickly, if organically. Poking around the system, I found (sometimes after
some s
Holger Freyther wrote:
> Guys, please don't make up "issues" were there are none.
Ah, sorry. Thought that was a complaint about a real problem.
- Werner
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
On Saturday 19 July 2008 18:13:33 Werner Almesberger wrote:
> Mike (mwester) wrote:
> > Another approach would be to craft some sort of script that would
> > disable SSH logins via the wireless interface if the root password is
> > empty. That might be really tricky; I'm not sure if SSH can do tha
#1643: strip unwanted non-digits from SMS numbers
-+--
Reporter: nomeata | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: OM-2007.2
Component: unkn
#1606: Match numbers to contacts more fuzzy
-+--
Reporter: nomeata |Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal |Milestone:
Compone
Hi
I have added (seemingly) complete support for matching human-written
phone number (07032/123 456) in the phone book or when dialing, instead
of just dumb string comparison, in both openmoko-dialer2 and
openmoko-messages2. The latter required a small, non-obstrusive change
to eds and libjana. Th
> Flemming Richter Mikkelsen wrote:
>
> My best tips is:
> ssh into the phone
> $ screen
> $ opkg update && opkg upgrade
> If the ssh session terminates, just ssh in again and run
> $ screen -x
>
>
> Screen is slow. [...]
>
slow, yes: around 30s for having the first shell :-P
Using strace, this de
I tried. I have OM2007.2 building with the MokoMakefile. But I still
couldn't build my app. I guess I don't know how to merge a new app
into the MokoMakefile. And then, how do I get it back out into an
ipkg? Or would I have to make a new image that had that one extra
program and re-flash my de
I thought I had g++ installed. But I went ahead and installed cpp.
That seems to have fixed it (at least that error).
Thanks!
-Steven
On Sat, Jul 19, 2008 at 12:07 PM, mahendra panpalia
<[EMAIL PROTECTED]> wrote:
> do you have cpp package installed and which one?
>
> On Sat, Jul 19, 2008 at 6:0
I don't have slocate installed and opkg can't find it either.
I figured maybe the equivalent was this:
cd /
ls -R | grep ccl
It doesn't find anything. However, ls -R | grep cc1 does:
libgcc1.control
libgcc1.list
libgcc1.postinst
libgcc1.control
libgcc1.list
libgcc1.postinst
cc1plus
-Steven
On
i think u have wrong direction
not try to find "build-essential" ipk for neo.
using Mokomakefile to build package
bitbake is tool u need.
On Sun, Jul 20, 2008 at 12:54 AM, Steven ** <[EMAIL PROTECTED]> wrote:
___
devel mailing list
devel@lists.openmoko.
hi, i've tried some too,
install gcc on neo, and try to compile an excutable app
and, same error
i was just curious to do it...
it should be better to use cross-compile scheme
say, build the app on your host machine
just too crazy to build on neo
On Sun, Jul 20, 2008 at 12:40 AM, Steven ** <[EMA
~# opkg install build-essential
An error ocurred, return value: 2.
Which package am I supposed to install?
-Steven
On Sat, Jul 19, 2008 at 11:50 AM, mahendra panpalia
<[EMAIL PROTECTED]> wrote:
> first thing is to make sure that build essential is installed, then it will
> easy to find missing p
I'm compiling ON my FreeRunner.
I'm attempting to compile openmoko-alarm-clock from
http://projects.openmoko.org/projects/ringer/
However, I just checked and I get the same error when trying to build
my sudoku app (which is a much simpler app).
-Steven
On Sat, Jul 19, 2008 at 11:45 AM, mahendra
And which package contains ccl? You realize it's a 1 (one) not an L, right?
I did check something else:
~# opkg install libgcc1
Package libgcc1 (4.1.2-r17) installed in root is up to date.
-Steven
On Sat, Jul 19, 2008 at 11:25 AM, mahendra panpalia
<[EMAIL PROTECTED]> wrote:
> i think you are
On Saturday 19 July 2008 17:50:53 Mike (mwester) wrote:
> Holger Freyther wrote:
> > Hey,
> >
> > as it would be bad to release a distribution with publically known
> > security issues I request your help to go through the list and help to
> > identify packages with known security issues.
> >
> :
Hi,
Am Samstag, den 19.07.2008, 10:50 -0500 schrieb Mike (mwester):
> Another approach would be to craft some sort of script that would
> disable SSH logins via the wireless interface if the root password is
> empty. That might be really tricky; I'm not sure if SSH can do that,
> much less dropbe
Mike (mwester) wrote:
> Another approach would be to craft some sort of script that would
> disable SSH logins via the wireless interface if the root password is
> empty. That might be really tricky; I'm not sure if SSH can do that,
> much less dropbear.
Just don't bring up WLAN before the a root
I get the following error when I do a ./configure:
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
What I believe is the relevant portion of the config.log:
configure:2613: checki
I think these errors are generic, even though I get them when trying
to compile openmoko-panel-alarm (since I don't see an ipkg available).
When I run om-conf I get the following errors:
checking for GTK... configure: error: Package requirements
(gtkmm-2.4 >= 2.8) were not met:
Package pthread-
Holger Freyther wrote:
> Hey,
>
> as it would be bad to release a distribution with publically known security
> issues I request your help to go through the list and help to identify
> packages with known security issues.
:) Someone just noted on IRC that it's probably a poor idea to enable
wif
#1641: opkg upgrade blows away custom volume settings
-+--
Reporter: hedora |Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |Milestone:
Component
39 matches
Mail list logo
