FSO Going Out of the Distro Business? - Questions
"Freesmartphone.org is going out of the distro business. We will focus on the framework itself and will rely on SHR for building a real distro and GUI around it." I got the above comment on a bug report I just filed and while I've heard it mentioned, I don't understand the ramifications. 1. How will FSO -test- their stuff during development prior to a distro picking up the release? Don't they need a vanilla distro for their own testing purposes? 2. If not FSO, where can I get a vanilla distro that -excludes- most of the GUI apps and let's me install just that which I want to use? I've been using the FSO distro because it lets me start with a solid kernel + basic services and build up an environment just the way I want. The other distros I've looked at bundle too much and make assumptions about the phone UI and PIM data storage that get in the way of operation. Really just the kernel, an sshd, FSO services, busybox, elementary, X11, Python and an opkg command pointing to a current set of .ipk files would be fine. Am I out of luck and things are going the way of bulky complex distros on Neo as well? -Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Seeking Extra Packages for FSO Milestone 5.5
I've successfully installed FSO Milestone 5.5 onto my GTA01 hardware and it is working fine. However I miss many of the optional tools I have installed on prior milestones. The directory: http://downloads.freesmartphone.org/fso-stable/milestone5.1/updates/ is missing and that's probably because there are no fixes out yet. Understandable, but where can I obtain the many -optional- packages for Milestone 5.5 such as emacs, libspeex, mplayer, madplay etc.? In case the answer is opkg.org, I'm puzzled by that site. It doesn't have indicators or a way to search by OM distribution, eg. SHR, FSO, DEB, etc. I'm sure every package is not OM distribution agnostic, so how are people managing this kind of compability? Is opkg.org actually the official place to obtain solid, tested packages for an FSO Milestone? Thanks, Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Hardware Recommendations - Desktop Bluetooth Module
Jonathon Suggs wrote: Does anyone have a good recommendation for a Bluetooth module/adapter for the desktop ? Features: Bluetooth 2.0, good support under Ubuntu, and also provide most all of the Bluetooth profiles. I don't mind a dongle, but would think that having an internal card would be less likely to get broken...since a dongle would always be protruding from the case. Thoughts, opinions? What does everyone else use? I too would like to find such - a nice PCMCIA/PCCARD to put into my laptop and forget about, as opposed to a USB dongle hanging out. Non-USB BT seems rare but I'm still looking and would appreciate notice if anyone gets there first. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What is the FCC ID of the neo1973?
Adam Krikstone wrote: I see no mention of it anywhere on the wiki or lists. Does anyone know the FCC ID? I'm curious of what use that information is -- does the registration point to information at the FCC that says something about the functioning of the phone? Are you worried that it is an illegal phone? -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Real Time Audio (SCHED_FIFO)
Esben Stien wrote: > "Brad Midgley" <[EMAIL PROTECTED]> writes: > >> tell us the big picture for what you want to do > > I want to be able to have real time low latency drop out free audio, > which is not possible without jack. > > This is especially crucial for a phone or anything that deals with > audio;). Actually it depends on how much mixing you're doing. At the hardware interface they are using ALSA. > I've heard now that JACK has been ported to openmoko, btw. I just hope > it's used as the default sound server in openmoko. Above ALSA, the default sound server for OpenMoko is PulseAudio, a very good audio server. It has features to support low-latency and realtime response. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Phone arrive! - Torx required?
Yay, my basic Neo1973 arrived today. It looks quite cool smaller than I expected and lightweight. But I think I'm about to fail my geek status - can't figure out how to insert the microSD card that came with it, without full disassembly of the unit. I, uh, don't own a Torx toolset and didn't order the advanced model with tools. I later decided I should have, but when I found out that changes move you to the back of the order line, I stayed with the basic unit. So, microSD installation w/o a Torx tool? And I guess a guitar pick as well, to get at the back of the PCB? -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Duplicate message troubleshooting
Nicolas Bougues wrote: > > Here is the kind of things my SMTP relay logs while talking to openmoko's > list > server : > > Jul 24 18:46:21 cassis postfix/smtp[9586]: 7E28BE0BA0: > to=, > relay=sita.openmoko.org[88.198.124.203]:25, delay=12360, > delays=12279/0.16/0.15/80, dsn=4.4.2, status=deferred ( > conversation with sita.openmoko.org[88.198.124.203] timed out while sending > end of data -- message may be sent more than once) > > There is a fair amount of those messages concerning openmoko, and just one or > two regarding other destinations (out of 25000+ mails relayed yesterday). > > I only posted once or twice to the list before, and no such behavior was > encountered. > > Unfortunatly, I don't have further SMTP traces. > > Could there be some connectivity problem, maybe firewall related, on > openmoko's side ? The problem is their SMTP server is taking its own sweet time recognizing the end-of-message sequence, so peer MUAs are starting to timeout instead. Here is a manual session: [EMAIL PROTECTED] ~ $ telnet sita.openmoko.org smtp Trying 88.198.124.203... Connected to sita.openmoko.org. Escape character is '^]'. 220 sita.openmoko.org ESMTP Exim 4.50 Wed, 25 Jul 2007 10:37:31 +0200 EHLO taupro.com 250-sita.openmoko.org Hello adsl-68-95-135-33.dsl.rcsntx.swbell.net [68.95.135.33] 250-SIZE 52428800 250-PIPELINING 250 HELP RCPT: [EMAIL PROTECTED] 500 unrecognized command MAIL FORM 500 unrecognized command MAIL FROM:<[EMAIL PROTECTED]> 250 OK RCPT TO:<[EMAIL PROTECTED]> 550 unknown user RCPT TO: 250 Accepted DATA 354 Enter message, ending with "." on a line by itself Date: 25 Jul 2007 03:34:00 From: [EMAIL PROTECTED] To: community@lists.openmoko.org Subject: Diagnostic Message This is a probe message to diagnose the SMTP problems. Please ignore. . (very long idle interval of 5 minutes or so) 250 OK id=1IDcPE-0002wr-QA It may be running off to validate the sender domain name to prevent spam, but is taking too long I think - perhaps an inefficient DNS arrangement. There are issues with their DNS, as this validator shows: http://www.dnsstuff.com/tools/dnsreport.ch?domain=openmoko.org with the biggest problem being stealth NS records with leakage, which can wreak havoc with timeouts. And yes, I copied the -owner of the community list. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: email vs forum (was Re: OK, the forum is coming..)
[EMAIL PROTECTED] wrote: > > Well, then, why not have forums for people who want them, and leave email > for people who don't want them? The thing is, it doesn't work very well in > practice. If experience is any guide, then the technically knowledgable > people will use email, and won't waste much time on the forums. But a > project at the current stage of the openmoko project will require lots of > *technical* help for everyone, so what will happen is that you will have to > follow the email lists anyway... I mean -- I could be wrong, but that's the > way things seem to go with this kind of project. I agree with you, but no amount of debate will convince anyone and it is just wasting bandwidth. We're going to find out by experimentation but I expect a repeat of the Golgafrincham civilisation from the Hitchhiker's Guide. There are already similarities, re what people expect from fire and what color the wheel should be. ;-) Those with the questions will hang out on the forum and those with the answers will use the mailing lists, and people will grumble about the unhelpful developers not coming over to the forum to help. I'm actually looking forward to the forums, to reduce that kind of traffic on this list. Sadly, I know of several people who have unsubscribed from this list because of it, and switched exclusively to the devel lists instead. Come on over to distro-devel and let's talk about builds and drivers! Let's get started working on the apps on the openmoko-devel list! -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: building openmoko devel image
Charles Lohr wrote: > To any willing to help: > > I'm a gentoo user who is considering buying one of the FIC1973 phones > for developing new software for. I figured I should be able to 'make' > the phone before buying it. Note that if this is being sent to the > wrong list, please direct me in the right direction. If we get into too many details, it might be best to move it to openmoko-devel but quick questions are hopefully ok. I run Gentoo here as well, and have it working, so there is hope. ;-) > I have been following the instructions on: > http://wiki.openmoko.org/wiki/MokoMakefile#Installation > > Every time I try building, I first get a list of errors like: > > NOTE: Handling BitBake files: | (4323/4354) [99 %]NOTE: Retrieved remote > revisions: ['0', '0', '2360', '0'] > NOTE: Handling BitBake files: / (4324/4354) [99 %]NOTE: Retrieved remote > revisions: ['0', '1828', '0'] > NOTE: Handling BitBake files: - (4325/4354) [99 %]NOTE: Retrieved remote > revisions: ['0', '0', '2360', '0'] > NOTE: Handling BitBake files: \ (4326/4354) [99 %]NOTE: Retrieved remote > revisions: ['0', '1828', '0'] > NOTE: Handling BitBake files: \ (4327/4354) [99 %]NOTE: Retrieved remote > revisions: ['0', '0', '2360', '0'] Those are not errors, just status messages, I believe. > Originally, I kept getting missing stuff for my java messages, but after > getting the JDK patched and working, I finally settled on this error > that I just can't seem to fix: [EMAIL PROTECTED] ~ $ equery list jre [ Searching for package 'jre' in all categories among: ] * installed packages [I--] [ -] dev-java/blackdown-jre-1.4.2.03-r14 (1.4.2) [I--] [ -] dev-java/sun-jre-bin-1.6.0.02 (1.6) [I--] [ ] virtual/jre-1.4.2 (1.4) [I--] [ ] virtual/jre-1.5.0 (1.5) [I--] [ ] virtual/jre-1.6.0 (1.6) [EMAIL PROTECTED] ~ $ eselect java-vm show Current system-vm sun-jdk-1.5 Current user-vm sun-jdk-1.5 Just FYI. > `/home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/gettext-0.14.1/gettext-runtime/intl-java' > | jar cf libintl.jar gnu/gettext/GettextResource*.class > | Exception in thread "main" java.lang.NoClassDefFoundError: cf > | make[4]: *** [libintl.jar] Error 1 > | make[4]: Leaving directory > `/home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/gettext-0.14.1/gettext-runtime/intl-java' > | make[3]: *** [all-recursive] Error 1 > | make[3]: Leaving directory > `/home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/gettext-0.14.1/gettext-runtime' > | make[2]: *** [all] Error 2 > | make[2]: Leaving directory > `/home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/gettext-0.14.1/gettext-runtime' > | make[1]: *** [all-recursive] Error 1 > | make[1]: Leaving directory > `/home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/gettext-0.14.1' > | FATAL: oe_runmake failed > NOTE: Task failed: > /home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/temp/log.do_compile.25316 > NOTE: package gettext-native-0.14.1-r4: task do_compile: failed > ERROR: TaskFailed event exception, aborting > NOTE: package gettext-native-0.14.1: failed > ERROR: Build of openmoko-devel-image failed > make: *** [openmoko-devel-image] Error 1 > > Is there any way to actually view what the Makefile is doing when it > just sits there and then this thing pops up, like verbose output or > something? There are logfiles, listed in your output, that might help. The one relate to the failing compile is: /home/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r4/temp/log.do_compile.25316 There are *lots* of logfiles created by the build process under the directory build/tmp/work/ directory. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko trademark issues...
Jae Stutzman wrote: > OpenMoko.Inc needs to have a clear trademark policy on the name OpenMoko > and associated logo, etc. Right now the maemo people are going through > some stuff do to recent changes. This is something that Sean and co need > to figure out. If it is already figgured out then it should be posted > somewhere on the wiki...a quick search for trademark reveals nothing. Yes a good thing to bring up, what with us all using their name and mark in volunteer stuff. As Cassj said, they have the legal work done to claim the marks but they do need a policy by which we the community can use them to promote OpenMoko. I'm sure other communities have this issue too. The Python community wants the Python trademark to be used to promote Python, in acceptable ways. The OpenMoko team can probably clip and rework the explanatory material to come up with their own policy. And if others know of good policy write-ups on other community trademarks, let's get them to Sean for his consideration. The Python trademark policy can be read at: http://www.python.org/psf/trademarks/ I think it is a pretty reasonable one. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Lars Hallberg wrote: > Daniel Robinson skrev: >> Hey Lars, >> >> Huzzah to you, sir, for getting that far. I got my ubuntu system up >> yesterday, but I haven't gotten some of the other pieces working. I >> haven't used OpenEmbedded or bitbake before. I use perforce at work. > > I have not set up a complete build env (don't have room)... Just build > the qemu according to "Manual setup" on: > > http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU > > And downloaded prebuilt kernel, rootfs and u-boot... all in the above > instructions. > > The 'extra' preparation I did was: > > install gcc 3.4 and run: > > # apt-get build-dep qemu I've not had the problems I'm seeing discussed on this list but then I used the MokoMakefile approach. One thing to note -- the OpenMoko build system comes with its own version of QEMU, with changes specific to the Neo1973. Running a stock QEMU outside the build environment will probably limit what you can do, in particular it lacks the virtual Neo1973 hardware they added. Re a few of the troubles, - Giles, I didn't have to modify any .h files to make it work, nor did I see any problems with the 8ma power you saw. - Lars, Yes, the onscreen keyboard does work, as in the GUI keyboard you click on with the mouse. I click in the upper-left box (white area, not icon) and the onscreen keyboard comes up in my QEMU image. - out of the box, it does not let you type into it using your desktop keyboard but you can add -usbdevice keyboard to make it work - I can say that the ability to 'ssh' into the QEMU does work here, but it requires a few steps in the QEMU monitor each time you use it re usb_add gadget:1 that cannot be automated. - To network into the QEMU image you must have gadget support in your host kernel. The Neo1973 docs talk about having a /dev/gadget file, for example with a gadgetfs mounted on it. I have to create it by hand each time I boot, as the udev system doesn't keep it around on my Gentoo system. I checked the source and you cannot move it elsewhere - the path is hardcoded. I hopes this helps, -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: community Digest, Vol 36, Issue 45
Eric van Horssen wrote: > > Have a look at what Harald wrote in his weblog on the 17th. > FIC is a B2B not a B2C, I don't think they ever before sold directly to > customers. > So FIC can't provide them with any knowledge about B2C, this is just > totally new for them True, I saw that as well. I was referring to why the guy hired for system software was pulled into hardware, and then into designing the B2C site and now into drawing the floorplans for office space and figuring how to route power and network to cubicles. Not quite the best use of his time, it seems, and also something that a skilled office administrator team and a commercial website design group, resources less rare than a good system programmer, would normally take care of. But I'm not trying to beat anyone up - I'm sure there are factors we're not privy to. I just hope that they'll obtain resources from FIC and perhaps ask from our community before they burn out. As several have said here on the list, as they build our dream we'd love to support them in turn - they don't have to do it all themselves. The free/opensource philosophy also means being able to call on the community. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Significant Numbers of Non-Developers?
Ortwin Regel wrote: > Order #1833 here and not a developer at all. My last Linux experience > was that I changed the screen resolution in Suse 9 to something that > didn't work and wasn't able to change it back and get back to the GUI. > :P Still, I need this phone and I need it now. It's the phone I've been > waiting for for about four years. Ortwin, with such strong feelings, "I need this phone and I need it now", you must have certain specific requirements for putting it to use. Certainly we all have our wish list with lots of far out ideas but what do you need to phone to do first, to meet these four-year-pent-up demands, from before the OpenMoko even existed? Basically you're speaking as someone frustrated with something in particular. > I hope people will help me if I'm stuck in some scary command line. ;) Certainly I'll help. I'm hoping to produce a series of screencasts about the phone. My first, just an overview for those wondering what the heck an OpenMoko is that I gave last week at the local DFW Unix Users group, can be found at: http://www.showmedo.com/videos/video?name=104&fromSeriesID=104 I'm planning a talk on the hardware, and another on the underlying software architecture. In my mind, I divide the audience into those who are system programmers (kernel/driver folks) and those who are application programmers (high-level lang + defined service interfaces). Besides being an embedded systems engineer, I'm also the advocacy coordinator for Python and hope to encourage and support those who want to build their apps using Python. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: community Digest, Vol 36, Issue 45
Mathew Davis wrote: > > And I don't understand why we can't have both. I really don't see the > problem so if someone could explain why not having a forum would be > advantageous and not just personal preferance I am all ears, because I > could list a lot of reasons why forums could be advantageous. I appreciate your viewpoint but here are a few reasons: 1. Our community is small -- spreading the discussions thinly before we have reached critical mass will dilute the synergy. We are just now starting to come together as a community, and I think we even have too many mailing lists as it is (not always clear on which one to discuss X). 2. The OpenMoko team at FIC are spread _very_ thin and lack the time/resources to research and establish a forum themselves. They were overloaded just getting a basic storefront up. I don't understand why a company the size of FIC isn't providing more logistics support to them, so they can focus on the hardware/software but that's the way it is today. 3. Because of #2 and the fact this is the world of free/open, groups are welcome to establish a forum someplace and announce it here. In fact no one can stop it. Then instead of debating it you apply the governance principle of open source, in that if you build it will they come. If so, you were right. If not, you were wrong. A very objective approach. And for those (another thread) who are looking for someone official to tell them how this or that is going to be done on the device, I think we as a community will be applying #3 above - teams will form and follow their (quite likely divergent) visions. Those who (1) produce results that (2) some significant portion of the community approve of will have their work integrated into the core as required/optional packages. And some fraction of those will be cherry-picked by FIC for delivery in the consumer distribution. And perhaps other flash images will arise targeted at "the power user" and "the gaming user" and "the multimedia user". Being open source folks and time-constrained themselves, I rather think that the OpenMoko team will be blessing running code and not managing the various teams that form. And that is good, because they cannot see the future uses of this device any better than we at this point. Not a planned economy but a chaotic marketplace of competing ideas, where decisions are made in the free/opensource tradition of "running code" and "rough concensus". Scary sure, but also refreshing and very exciting. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Significant Numbers of Non-Developers?
I've been reading the archives of the various OpenMoko lists and I've noticed a significant number of people who admit they are not programmers at all, or that this is their first exposure to Linux. I'm curious what a non-programmer is going to do with this device in the next few months. And if your first use of Linux is on the device itself, and you run Windows on your desktop, how you're going to grow your Linux skills and effectively develop applications. Just seems odd to me, but maybe I'm overlooking something. ;-) BTW, there are threads of discussion here that are answered by digging into the source code released so far. I've seen some people asking the OpenMoko team to spell how how this or that is going to be done (events from calls) -- guys, its in the source and at this stage we're expected to be developers. While waiting for our oders, we should be setting up our development environment, reading thru the source given so far, and writing test programs to run within the QEMU environment, to get ready. I doubt once the device arrives in the mail that it will come with a manual that makes all things clear or that the functionality on the device will be useful for much by itself -- you'll still have to dive into the source. As an embedded developer myself, the less than smooth way things are unfolding and the rough nature of the device itself are normal and expected when engineering a new device. Those used to a consumer device may not understand this as they rarely get a peek into the process like FIC is giving us. And I'd just like to say to the OpenMoko team "thanks" for giving us this device and opening it up so that we can participate in its shaping. That many decisions on how things are going to be done are not yet made is a -good- thing, people. The journey is the reward for geeks, not the final destination of a polished, shrink-wrap consumer gadget. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: community Digest, Vol 36, Issue 45
Steven ** wrote: > Is that searchable? Is it threaded? Will there be someone on 24/7 that > is knowledgable and helpful? > > I understand that some people love IRC and mailing lists. But users > expect to search and ask questions in a forum, not on a mailing list and > IRC. I think it's about time for some forums. I'm not sure where you get "users expect to search and ask questions in a forum" from. And how does a forum provide "24/7 someone knowledgeable" in such a way that a mailing list cannot. I'm confused. Mailing lists aren't exactly fading away, and many people dislike forums. In this case, it won't help if those with questions i.e. users flock to the forums, if those with the answers, the more core developers use mailing lists. You'll need community concensus, or a team to copy material between the two discussion arenas, similiar to how we have people who have stepped forward (thanks!) who clip useful stuff from the lists and put it on the wiki. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Unusual Bluetooth Gadgets?
I was thinking this phone has so many possibilities, and one of them is neat bluetooth gadgets we could make use of. But searching I don't see a lot of innovative bluetooth gadgets to buy. Has anyone seen a small bluetooth camera you can wear on your lapel? Even if it was the size of a bluetooth earpiece, it would work as a piece of jewelry on a collar. And is there a small bluetooth microphone suitable on a lapel as well, for recording those interviews? Instead of picking up just your voice via bone conduction or some such it picks up the audio from in front of you with a focused area. Maybe I don't hang out on the right gadget website. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: this phone, with WiFi
Doug Jones wrote: > Well, here is a single part that would make it much easier to try out > WiFi antennas, other kinds of antennas, all kinds of random hardware... > > http://wiki.openmoko.org/wiki/Wishlist:ExpansionSpacer A very cool idea - I'd love to have one or two of those, for up to US$30 each! They'd be great for research data collection devices and such where fashionable small is not a prerequisite. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gentoo qemu (was Re: Binary tarball of toolchain/build environment)
Al Johnson wrote:
On Monday 16 July 2007 11:38, Jeff Rush wrote:
Al Johnson wrote:
I was going to suggest this too. This is the approach taken for the
Neuros OSD, another linux-based device. It would give a known-working
build and test environment, rather than having potential developers
spending time trying to put such an environment together. Mokomakefile is
good, but I just can't get the qemu to build under gentoo.
A good idea re providing a VM. BTW, I run Gentoo also and QEMU using
Mokomakefile built with no problems here. Are you trying to do it with GCC
4.x? It supposedly is a known bug and you need to use GCC 3.x.
Fortunately you can have both installed at the same time and use them where
needed. I have GCC 3.x set as the default compiler.
# equery list gcc
[I--] [ -] sys-devel/gcc-3.4.6-r2 (3.4)
[I--] [ -] sys-devel/gcc-4.1.2 (4.1)
I have both too, and use gcc-config to switch when emerging qemu. If I select
3.4.6 with gcc-config then run 'make qemu' mtn complains:
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'GLIBCXX_3.4.6' not found (required by mtn)
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'CXXABI_1.3.1' not found (required by mtn)
Makefile: 28: *** Cannot determine version for monotone using "mtn -version".
Stop.
Hmm, the interesting thing there is that monotone requires a *double* dash for
long options, so manually doing "mtn -version" will indeed fail. In my
Makefile re the MokoMakefile, I have it with a double dash:
MTN_VERSION := $(shell mtn --version | awk '{ print $$2; }')
... in case this helps at all. I don't see any way to determine the version
of Makefile I have.
-Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
Al Johnson wrote: I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. A good idea re providing a VM. BTW, I run Gentoo also and QEMU using Mokomakefile built with no problems here. Are you trying to do it with GCC 4.x? It supposedly is a known bug and you need to use GCC 3.x. Fortunately you can have both installed at the same time and use them where needed. I have GCC 3.x set as the default compiler. # equery list gcc [I--] [ -] sys-devel/gcc-3.4.6-r2 (3.4) [I--] [ -] sys-devel/gcc-4.1.2 (4.1) -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for openmoko - bugsafe?
Edwin Lock wrote: My main point was if the state, well, anyone who had connections to the carriers, could turn the neo into a bug too.. And it seems that it isn't possible cause of the software mixer being off when the device is off :) Actually one may want to implement this on the OpenMoko themselves, as a phone-theft tracking system. Imagine being able to call your missing phone and enable at least GPS tracking so you can recover it. Being able to switch on audio recording to the flash storage, with periodic burst transmission to an Internet location of GPS points, audio samples and such might be useful for some applications as well. Leave it in a taxi in New York and plot the conversations and locations on a webpage, as part of a reality show... ;-) BTW, anyone have good leads on small Bluetooth camera lapel pins? It would be cool to have the OpenMoko able to record/recognize the faces of people I meet or places I visit. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
adding data services with t.mobile for neo 1973
> The one guideline you need to be aware of is that you CAN NOT get data > GPRS or EDGE on a pay as you go plan (T-Mobile to go). It has to be > on a post paid monthly account. To my knowledge and research, neither > AT&T or T-Mobile will permit a data package on a pay as you go basis. It wouldn't be the first time their webpage was wrong, but the T-mobile page for pay-as-you-go (which I have) says you can add Internet access, which they call their "SideKick" feature, for $1/day. I haven't tried it, and it certainly is more expensive than your $5.99/mo option. (just placed an order for a Neo1973 and looking forward to developing) -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
