Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
Hi Alan, > On a related point freesmartphone.org seems to be using the old hackish > 3gpp ts07.10 user space code. Correct, for systems which don't use premultiplexed drivers, we're resorting to a userland muxer (not the gsm0710muxd though, but rather a clean implementation based on other code). I'd love to see a kernel muxer, really. While I don't think it makes a difference on GPRS, it might improve system performance on EDGE or UMTS a lot. > I've got almost all of a kernel driver only > my AT+CMUX capable device has expired. Dunno if anyone is interested in > finishing the job (its basically written but not at all debugged and I > know the tx queueing needs work either to make it do all the priorities > right or just forget the the whole priority nightmare) I think it'd be great if you could upload your code somewhere. > Alternatively does anyone know what cheaper EU devices support AT+CMUX, > it seems quite rare this side of the pond Do you no longer have an Openmoko device? If not, I could arrange to ship you one -- it may have problems, but at least the GSM would work. Best regards, Mickey. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
On Tue, Oct 6, 2009 at 5:08 PM, Rod Whitby wrote: > 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. > So long and thanks for all the fish.. MokoMakefile was a neat script. :) Regards Sudharshan S Blog : http://sudharsh.wordpress.com IRC : Sup3rkiddo @ Freenode, Gimpnet ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
2009/10/6 Rod Whitby : > 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 all know the rest of the > story on the software side of things. > > I've now started a new community (webos-internals.org) which does open > source Linux-based development for the Palm Pre. > > My hope is that freesmartphone.org may one day be the bridge between > the OpenMoko community I am now leaving, and the WebOS Internals > community which has recently started. > > I wish everyone continuing down the OpenMoko path the best of success > in the future. > > -- Rod Hi Rod, thanks for your all your work on lower the barrier of OE hell for a newbee like me, and thanks for your private lessons about GPL licencing and nettiquete I have learned a lot thanks to you, I will follow your work whit the Pre close, I like to see little devices with a free hackable penguin inside :) David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable & embedded solutions Openmoko, Openpandora, Arduino Hey, watch out!!! There's a linux in your pocket!!! > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
Thank you anyway. Traitor! :) And ROFL about the northern hemisphere chauvinism issue with your GPS. *g* I hope that is not a omen... See you back ;) Rod Whitby wrote: > 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. > -- MFG Tilman Baumann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
Rod, thanks for all the work you did to bring Openmoko forward! Even though it took all so long due to all our detours, I'm quite satisfied with what the Openmoko community has created throughout the years, especially since Openmoko Inc. stopped guiding the project. A hardware family often is the initial trigger to establish a community, however it's important to embrace and extend, especially when the days of the hardware family are counted. As other solution come around, it gets important for the Openmoko community to widen the focus and grow into something larger. I created the freesmartphone.org project to cover a much wider scope than Openmoko -- as such, we are looking forward to continue our work on FSO covering both anti-vendor-ports and forthcoming semiopen devices such as the Palm Pre and the Nokia N900. So... good bye and hello again! See you soon, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
Rod, wow, sad to see you go indeed. You are one of the true old-timers of Openmoko :-) Since hacking the Palm Pre is not that far from an 'open phone' perspective, maybe you can add a feed to the Openmoko planet and we can that way stay in touch with what you are doing? I will regularly check what's going on at webos-internals.org All the best! Good luck! Wolfgang On Tue, Oct 06, 2009 at 10:08:23PM +1030, Rod Whitby wrote: > 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 all know the rest of the > story on the software side of things. > > I've now started a new community (webos-internals.org) which does open > source Linux-based development for the Palm Pre. > > My hope is that freesmartphone.org may one day be the bridge between > the OpenMoko community I am now leaving, and the WebOS Internals > community which has recently started. > > I wish everyone continuing down the OpenMoko path the best of success > in the future. > > -- Rod > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rod Whitby (MokoMakefile author) moves on to start WebOS Internals
Hello. On Tue, 2009-10-06 at 22:08, Rod Whitby wrote: > > My hope is that freesmartphone.org may one day be the bridge between > the OpenMoko community I am now leaving, and the WebOS Internals > community which has recently started. Work for such a bridge is already ongoing. Hardware should be here around 2009-10-12. http://www.freesmartphone.org/index.php/Palm_Pre_Challenge Hope to see you on the other side. :) regards Stefan Schmidt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
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 all know the rest of the story on the software side of things. I've now started a new community (webos-internals.org) which does open source Linux-based development for the Palm Pre. My hope is that freesmartphone.org may one day be the bridge between the OpenMoko community I am now leaving, and the WebOS Internals community which has recently started. I wish everyone continuing down the OpenMoko path the best of success in the future. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QEMU MokoMakefile updates?
regarding the wiki page at http://wiki.openmoko.org/wiki/Using_QEMU_with_MokoMakefile, section Compilation and use, does anyone have updated filenames/urls for the env file? the current svn file refers to invalid urls and filenames. http://wiki.openmoko.org/wiki/Qemu also appears to be significantly outdated. thank you, -david ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MokoMakefile
Hello, When I try to build the openmoko toolchain with the MokoMakefile I have encountered this error : NOTE: make make: GNUmakefile: Too many levels of symbolic links make: stat: GNUmakefile: Too many levels of symbolic links make: *** No rule to make target `GNUmakefile'. Stop. FATAL: oe_runmake failed in the following package NOTE: package coreutils-native-7.1-r0: task do_compile: started ERROR: function do_compile failed My procedure to build the openmoko toolchain was the following : $ wget http://downloads.freesmartphone.org/Makefile $ make setup $ make fso-gta02-testing-image Nowadays is it possible to build the openmoko toolchain with a MokoMakefile or is it broken. Best Regards, hadroneo. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
mokomakefile
Trying to build testing (2008.x) with mokomakefile but it crashes out with an error making me think its not. Just to confirm that I am building what I think I am: OE Build Configuration: BB_VERSION= "1.8.11" METADATA_BRANCH = "org.openmoko.dev " METADATA_REVISION = "bad4ab8693c8309c48f282688344b1f266368e84" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "om-gta02" DISTRO= "openmoko" DISTRO_VERSION= "-20081223" TARGET_FPU= "soft" In mokomakefile: # OM_GIT_BRANCH := org.openmoko.asu.stable # OM_IMAGE_NAME := openmoko-asu-image OM_GIT_BRANCH := org.openmoko.dev OM_IMAGE_NAME := openmoko-base-image should give me 2008.testing ??? and the two commented lines 2008.12 ??? right? BillK -- William Kenworthy Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
Joan.doe wrote: > > On Tue, 25 Nov 2008 17:56:18 -0800 (PST) > lostdays <[EMAIL PROTECTED]> wrote: > > Hi > I could not boot openmoko too. But with replacing and flashing u-boot with > the u-boot image of the pre buid windows image > (http://yorick.keymeulen.com/openmoko-emulator-bin-20070625.rar) i was > able to start. So replace /openmoko/build/qemu/openmoko/gta01bv4 with the > uboot.bin from above and run openmoko/flash.sh from directory > /openmoko/build/qemu/ After that you should be able to boot. > > But i didnot manage to get usb networking work because of a missing > terminal in OM 2008.9 .. > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > Hi, Thanks. I have followed your mail to try it, it works. I have replaced the kernel and roof fs file but don't replaced the uboot image. I guess there is some bug in the new uboot image. -- View this message in context: http://n2.nabble.com/help%7EAfter-using-the-MokoMakefile-to-build-the-qemu%2C-the-qemu-neo1973-restart-at-once-when-it-boot-the-kernel-tp1574858p1585315.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
On Tue, 25 Nov 2008 17:56:18 -0800 (PST) lostdays <[EMAIL PROTECTED]> wrote: Hi I could not boot openmoko too. But with replacing and flashing u-boot with the u-boot image of the pre buid windows image (http://yorick.keymeulen.com/openmoko-emulator-bin-20070625.rar) i was able to start. So replace /openmoko/build/qemu/openmoko/gta01bv4 with the uboot.bin from above and run openmoko/flash.sh from directory /openmoko/build/qemu/ After that you should be able to boot. But i didnot manage to get usb networking work because of a missing terminal in OM 2008.9 .. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
uweba wrote: > > > > mailing wrote: >> >> On Tue, 25 Nov 2008 08:53:17 +0100, Oscar <[EMAIL PROTECTED]> wrote: >>> I'm having the same problem, also with ubuntu 8.04. >>> Saludoss >>> >>> >>> >>> On Tue, Nov 25, 2008 at 3:59 AM, lostdays <[EMAIL PROTECTED]> wrote: >>>> >>>> the image i used are "testing-om-gta01-20081124.uImage.bin", >>>> "testing-om-gta01-20081124.rootfs.jffs2" >>>> "gta01bv4-u-boot.bin". >>>> I followed the Wiki.openmoko.org, firstly installed required software, >>> then >>>> download the mokomakefile, "make qemu","make run-qemu". the qemu >>>> lauched >>>> with the menu. But when I choose the boot menu, it failed without any >>> error >>>> message out when loading the kernel and return the boot menu. Any idea >>> for >>>> it? >>>> My OS version is ubuntu 8.04. >>>> Thanks >> >> I'm having this problem too, with both mandriva 2009 and cooker (2009.1), >> with mokomakefile and the manual setup >> (http://wiki.openmoko.org/wiki/Openmoko_under_QEMU) >> >> > > Same problem here. Suse 10.3. > > I had qemu installed and it worked fine. Then I reinstalled qemu (with the > makefile and manually) and it showed the same behaviour as above > described. > > Uwe > Are there solution for that? It seems not my single issue. -- View this message in context: http://n2.nabble.com/help%7EAfter-using-the-MokoMakefile-to-build-the-qemu%2C-the-qemu-neo1973-restart-at-once-when-it-boot-the-kernel-tp1574858p1579207.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
mailing wrote: > > On Tue, 25 Nov 2008 08:53:17 +0100, Oscar <[EMAIL PROTECTED]> wrote: >> I'm having the same problem, also with ubuntu 8.04. >> Saludoss >> >> >> >> On Tue, Nov 25, 2008 at 3:59 AM, lostdays <[EMAIL PROTECTED]> wrote: >>> >>> the image i used are "testing-om-gta01-20081124.uImage.bin", >>> "testing-om-gta01-20081124.rootfs.jffs2" >>> "gta01bv4-u-boot.bin". >>> I followed the Wiki.openmoko.org, firstly installed required software, >> then >>> download the mokomakefile, "make qemu","make run-qemu". the qemu lauched >>> with the menu. But when I choose the boot menu, it failed without any >> error >>> message out when loading the kernel and return the boot menu. Any idea >> for >>> it? >>> My OS version is ubuntu 8.04. >>> Thanks > > I'm having this problem too, with both mandriva 2009 and cooker (2009.1), > with mokomakefile and the manual setup > (http://wiki.openmoko.org/wiki/Openmoko_under_QEMU) > > Same problem here. Suse 10.3. I had qemu installed and it worked fine. Then I reinstalled qemu (with the makefile and manually) and it showed the same behaviour as above described. Uwe -- View this message in context: http://n2.nabble.com/help%7EAfter-using-the-MokoMakefile-to-build-the-qemu%2C-the-qemu-neo1973-restart-at-once-when-it-boot-the-kernel-tp1574858p1577880.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
On Tue, 25 Nov 2008 08:53:17 +0100, Oscar <[EMAIL PROTECTED]> wrote: > I'm having the same problem, also with ubuntu 8.04. > Saludoss > > > > On Tue, Nov 25, 2008 at 3:59 AM, lostdays <[EMAIL PROTECTED]> wrote: >> >> the image i used are "testing-om-gta01-20081124.uImage.bin", >> "testing-om-gta01-20081124.rootfs.jffs2" >> "gta01bv4-u-boot.bin". >> I followed the Wiki.openmoko.org, firstly installed required software, > then >> download the mokomakefile, "make qemu","make run-qemu". the qemu lauched >> with the menu. But when I choose the boot menu, it failed without any > error >> message out when loading the kernel and return the boot menu. Any idea > for >> it? >> My OS version is ubuntu 8.04. >> Thanks I'm having this problem too, with both mandriva 2009 and cooker (2009.1), with mokomakefile and the manual setup (http://wiki.openmoko.org/wiki/Openmoko_under_QEMU) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
I'm having the same problem, also with ubuntu 8.04. Saludoss On Tue, Nov 25, 2008 at 3:59 AM, lostdays <[EMAIL PROTECTED]> wrote: > > the image i used are "testing-om-gta01-20081124.uImage.bin", > "testing-om-gta01-20081124.rootfs.jffs2" > "gta01bv4-u-boot.bin". > I followed the Wiki.openmoko.org, firstly installed required software, then > download the mokomakefile, "make qemu","make run-qemu". the qemu lauched > with the menu. But when I choose the boot menu, it failed without any error > message out when loading the kernel and return the boot menu. Any idea for > it? > My OS version is ubuntu 8.04. > Thanks > -- Oscar Morante GPG: CA7417FF "La nostalgia ya no es lo que era" - Anónimo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
help~After using the MokoMakefile to build the qemu, the qemu-neo1973 restart at once when it boot the kernel
the image i used are "testing-om-gta01-20081124.uImage.bin",
"testing-om-gta01-20081124.rootfs.jffs2"
"gta01bv4-u-boot.bin".
I followed the Wiki.openmoko.org, firstly installed required software, then
download the mokomakefile, "make qemu","make run-qemu". the qemu lauched
with the menu. But when I choose the boot menu, it failed without any error
message out when loading the kernel and return the boot menu. Any idea for
it?
My OS version is ubuntu 8.04.
Thanks
Make qemu log is following:
[ -e build/qemu ] || \
( mkdir -p build/qemu )
[ -e build/qemu/Makefile ] || \
( . ./setup-env && cd build/qemu && \
${OMDIR}/openmoko/trunk/src/host/qemu-neo1973/configure \
--target-list=arm-softmmu )
[ -e build/qemu/openmoko ] || \
( . ./setup-env && cd build/qemu && mkdir openmoko && \
for f in ${OMDIR}/openmoko/trunk/src/host/qemu-neo1973/openmoko/* ; do
\
ln -s $f openmoko/`basename $f` ; \
done )
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env
build/qemu/openmoko/env
[ -d stamps ] || mkdir stamps
touch stamps/qemu
( cd build/qemu && make )
make[1]: Entering directory `/home/flyingcloud/openmoko/build/qemu'
make -C arm-softmmu all
make[2]: Entering directory
`/home/flyingcloud/openmoko/build/qemu/arm-softmmu'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/flyingcloud/openmoko/build/qemu/arm-softmmu'
make[1]: Leaving directory `/home/flyingcloud/openmoko/build/qemu'
[ -e images/openmoko ] || mkdir -p images/openmoko
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env
images/openmoko/env
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh
)
Retrieving available builds list...
Kernel is... testing-om-gta01-20081124.uImage.bin
Root filesystem is... testing-om-gta01-20081124.rootfs.jffs2
U-boot is... gta01bv4-u-boot.bin
Retrieving position
Now use openmoko/flash.sh to install OpenMoko to NAND Flash.
rm -f images/openmoko/env
[ -d stamps ] || mkdir stamps
touch stamps/images
( cd build/qemu && openmoko/flash.sh ../../images/openmoko )
/usr/bin/pngtopnm
/usr/bin/ppmtorgb3
make[1]: Entering directory `/home/flyingcloud/openmoko/build/qemu/openmoko'
make[1]: `splash.gz' is up to date.
make[1]: Leaving directory `/home/flyingcloud/openmoko/build/qemu/openmoko'
Using 'testing-om-gta01-20081124.uImage.bin' as the kernel image.
Using 'testing-om-gta01-20081124.rootfs.jffs2' as the root filesystem image.
Using 'gta01bv4-u-boot.bin' as bootloader.
make[1]: Entering directory `/home/flyingcloud/openmoko/build/qemu/openmoko'
# Making an empty/erased flash image. Need a correct echo behavior.
echo -en \\0377\\0377\\0377\\0377\\0377\\0377\\0377\\0377 > .8b
cat .8b .8b > .16b # OOB is 16 bytes
cat .16b .16b .16b .16b .16b .16b .16b .16b > .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .512b .16b > .sec # A sector is 512 bytes of data + OOB
cat .sec .sec .sec .sec .sec .sec .sec .sec > .8sec
cat .8sec .8sec .8sec .8sec .8sec .8sec .8sec .8sec > .64sec
cat .64sec .64sec .64sec .64sec .64sec .64sec .64sec .64sec > .512sec
cat .512sec .512sec .512sec .512sec > .2ksec
cat .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec > .16ksec
# Neo NAND is 128k sectors big
cat .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec >
openmoko-flash.base
rm -rf .8b .16b .512b .sec .8sec .64sec .512sec .2ksec .16ksec
make[1]: Leaving directory `/home/flyingcloud/openmoko/build/qemu/openmoko'
Please wait, programming the NAND flash...
neo_gsm_switch: GSM disabled.
U-Boot 1.3.2-moko12 (Nov 24 2008 - 18:46:05)
I2C: ready
DRAM: 128 MB
NAND: Bad block table not found for chip 0
Bad block table not found for chip 0
64 MiB
Video: 640x480x8 31kHz 59Hz
USB: S3C2410 USB Deviced
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
pcf_write: charging in Qualification Mode.
pcf_write: charge voltage 4.20V.
neo_lcd_rst_switch: LCD reset.
jbt6k74_command: Display on.
neo_vib_switch: Buzz, buzz.
neo_vib_switch: Vibrator stopped.
neo_bl_switch: LCD Backlight now on.
GTA01Bv4 #
GTA01Bv4 #
GTA01Bv4 # setenv dontask y
GTA01Bv4 # nand createbbt
Create BBT and erase everything ?
Erasing at 0x0 -- 0% complete. Erasing at 0xa -- 1% complete.
Erasing at 0x144000 -- 2% complete. Erasing at 0x1e8000 -- 3% complete.
Erasing at 0x28c000 -- 4% complete. Erasing at 0x33
MokoMakefile make toolchain error
I'm trying to use MokoMafile to build a toolchain ("make toolchain"),
and I'm getting the error below. I can do other operation (e.g. "make
image") without errors. Thanks in advance for any help!
Jim
NOTE: package meta-toolchain-openmoko-1.0: started
NOTE: package meta-toolchain-openmoko-1.0-r1: task do_populate_sdk: started
ERROR: function do_populate_sdk failed
ERROR: log data follows
(/media/disk/jim/projects/moko/build/tmp/work/i686-armv4t-sdk-angstrom-linux-gnueabi/meta-toolchain-openmoko-1.0-r1/temp/log.do_populate_sdk.12909)
|
/media/disk/jim/projects/moko/build/tmp/work/i686-armv4t-sdk-angstrom-linux-gnueabi/meta-toolchain-openmoko-1.0-r1/temp/run.do_populate_sdk.12909:
line 175: package_update_index_ipk: command not found
NOTE: Task failed:
/media/disk/jim/projects/moko/build/tmp/work/i686-armv4t-sdk-angstrom-linux-gnueabi/meta-toolchain-openmoko-1.0-r1/temp/log.do_populate_sdk.12909
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Porting MokoMakefile, odd errors
Lally Singh wrote: > I'm getting an openmoko build environment set up on OpenSolaris > (which, btw, is great). A build error is difficult for me to > interpret. I was hoping for some help. I've included the full output > below. At this point, you have left the realm of MokoMakefile, and entered deep into OpenEmbedded and Bitbake. Though you might be lucky and find someone on the openmoko lists who has ported OpenEmbedded to OpenSolaris, I expect you will have better fortune on the openembedded-devel mailing list. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Porting MokoMakefile, odd errors
Hey folks,
I'm getting an openmoko build environment set up on OpenSolaris
(which, btw, is great). A build error is difficult for me to
interpret. I was hoping for some help. I've included the full output
below.
I'm getting this problem, though:
ERROR: iterable argument required while parsing
/research/moko/openembedded/packages/openssl/openssl-native_0.9.XY.bb
for X in 7,8 and Y in m,g.
Also:
ERROR: Information not available for target 'i86pc-sunos'
Which is understandable.
How would I go about fixing these problems? Any suggestions or
pointers to documentation would be well appreciated.
Thank you!
-ls
[EMAIL PROTECTED] moko]$ time gmake image
( cd build && . ../setup-env && \
( bitbake openmoko-asu-image u-boot-openmoko ) )
NOTE: Removed the following variables from the
environment:SSH_CLIENT,PS1,LD_LIBRARY_PATH,MAKEFLAGS,TZ,SHLVL,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,VISUAL,LD_OPTIONS,SSH_TTY,OLDPWD,MAKELEVEL,MAIL,SSH_CONNECTION,PAGER
NOTE: Out of date cache found, rebuilding...
NOTE: Handling BitBake files: - (0899/5436) [16 %]ERROR: Information
not available for target 'i86pc-sunos'
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED](d)}
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED]('SITEINFO_ENDIANESS', 'le', '-DL_ENDIAN',
'-DB_ENDIAN', d)} -DTERMIO -fexpensive-optimizations
-frename-registers -fomit-frame-pointer -Os -Wall
NOTE: exceptions.TypeError:iterable argument required while evaluating:
${@'${CFLAG}'.replace('-O2', '')}
ERROR: iterable argument required while parsing
/research/moko/openembedded/packages/openssl/openssl-native_0.9.7m.bb
NOTE: Handling BitBake files: \ (0902/5436) [16 %]ERROR: Information
not available for target 'i86pc-sunos'
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED](d)}
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED]('SITEINFO_ENDIANESS', 'le', '-DL_ENDIAN',
'-DB_ENDIAN', d)} -DTERMIO -fexpensive-optimizations
-frename-registers -fomit-frame-pointer -Os -Wall
NOTE: exceptions.TypeError:iterable argument required while evaluating:
${@'${CFLAG}'.replace('-O2', '')}
ERROR: iterable argument required while parsing
/research/moko/openembedded/packages/openssl/openssl-native_0.9.7g.bb
NOTE: Handling BitBake files: | (0904/5436) [16 %]ERROR: Information
not available for target 'i86pc-sunos'
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED](d)}
NOTE: exceptions.TypeError:iterable argument required while evaluating:
[EMAIL PROTECTED]('SITEINFO_ENDIANESS', 'le', '-DL_ENDIAN',
'-DB_ENDIAN', d)} -DTERMIO -fexpensive-optimizations
-frename-registers -fomit-frame-pointer -Os -Wall
NOTE: exceptions.TypeError:iterable argument required while evaluating:
${@'${CFLAG}'.replace('-O2', '')}
ERROR: iterable argument required while parsing
/research/moko/openembedded/packages/openssl/openssl-native_0.9.8g.bb
NOTE: Handling BitBake files: | (5436/5436) [100 %]
NOTE: Parsing finished. 0 cached, 5196 parsed, 237 skipped, 0 masked.
ERROR: Parsing errors found, exiting...
gmake: *** [openmoko-asu-image] Error 1
real2m15.427s
user1m57.723s
sys 0m6.409s
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Building and testing asu with MokoMakeFile and qemu
Ok, i changed target machine in freerunner, build succesfull the image and flashed the phone. It worked, now i have my freerunner with a fresh builded asu. So it seems a problem with qemu, or gta01. Finally i tryed to run official updated images and they have the same problem. So is it qemu suppport now broken? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Building and testing asu with MokoMakeFile and qemu
I rebuilded all from scratch and now i found uImage-2.6.24., so make flash-qemu-local run successfull, howewer when i finally run make run-qemu, u-boot loads the kernel and returns to it's main menu. I'm not expert on u-boot, howewer i added -serial stdio to qemu, it gives: U-Boot 1.3.2-moko12 (Sep 4 2008 - 17:27:20) I2C: ready DRAM: 128 MB NAND: 64 MiB Found Environment offset in OOB.. Video: 640x480x8 31kHz 59Hz NAND read: device 0 offset 0x244000, size 0x5000 Reading data from 0x248e00 -- 100% complete. 20480 bytes read: OK USB: S3C2410 USB Deviced In:serial Out: serial Err: serial neo_lcd_rst_switch: LCD reset. jbt6k74_command: Display on. neo_vib_switch: Buzz, buzz. neo_vib_switch: Vibrator stopped. neo_bl_switch: LCD Backlight now on. GTA01Bv4 # boot ## Booting kernel from Legacy Image at 3010 ... Image Name: Openmoko/2.6.24+git1+a1e97c61125 Created: 2008-09-04 13:37:58 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1894664 Bytes = 1.8 MB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK ERROR: image overwritten - must RESET the board to recover. neo_gsm_switch: GSM disabled. wath can i do now? Nicola On 9/3/08, Nicola Mfb <[EMAIL PROTECTED]> wrote: > I'm working an ubuntu hh to build and test asu. > I downloaded > http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile > changed OM_GIT_BRANCH in org.openmoko.asu.stable > > after that i did make setup, make setup-machine-neo and make > openmoko-qtopia-x11-image. > The image was build successfull after several hours, but when i try to do > make flash-qemu-local i get an error saying > that is not possible to ls files in > build/tmp/deploy/glibc/images/neo1973/uImage-2.6.*-om-gta01.bin > > What do i miss? > > thanks > >Nicola > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Building and testing asu with MokoMakeFile and qemu
I'm working an ubuntu hh to build and test asu. I downloaded http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile changed OM_GIT_BRANCH in org.openmoko.asu.stable after that i did make setup, make setup-machine-neo and make openmoko-qtopia-x11-image. The image was build successfull after several hours, but when i try to do make flash-qemu-local i get an error saying that is not possible to ls files in build/tmp/deploy/glibc/images/neo1973/uImage-2.6.*-om-gta01.bin What do i miss? thanks Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
>> Yes. Compiling pixman breaks with an unresolved symbol >> "pixman...something". There was a message about this on devel on Aug. >> 13 and the answer was like "please wait 1 or 2 weeks, sources will be >> fixed until then". >> > If I remember well - I am an old man ... - . This happened only if you tried > to build FSO in the openmoko environment. Do not do that. > No . That's not what I want. I am on the 2008.08 path. > I looked into the different builds. The last time pixmap was build in a > "testing" on my machine was the 14.8. (Aug.14). It was not different from > earlier builds in stable or dev. Same source, same result. > OK. Then I will wipe out my sources und try everything from scratch. Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem in building image using MokoMakefile
Hello all, I tried many times to build the openmoko devel image using mokomakefile, but everytime the package named "cairo" is failing to build. I cleaned it and again tried to build, but everytime the same problem exists. The error message is like this (last few lines): *** NOTE: package perl-native-5.8.8-r13: task do_compile: completed NOTE: package perl-native-5.8.8: completed NOTE: Tasks Summary: Attempted 1101 tasks of which 1100 didn't need to be rerun and 1 failed. ERROR: '/home/saurabhg/moko/openembedded/packages/cairo/cairo_1.6.4.bb' failed NOTE: build 200808311700: completed make: *** [openmoko-devel-image] Error 1 Can anyone suggest to fix this. Thanks.. On Sun, Aug 24, 2008 at 1:01 AM, Luke Duncan <[EMAIL PROTECTED]> wrote: > I saw the same error and fixed it by doing this: > > su root > echo 0 > /proc/sys/vm/mmap_min_addr > exit > > then try make again. > > Luke. > > > On Sat, Aug 23, 2008 at 11:26 AM, saurabh gupta < > [EMAIL PROTECTED]> wrote: > >> Hello everyone, >> >> Previously I was using toolchain to compile the programs, but now i need >> the openmoko setup and bitbake in my PC. I used the Mokomakefile to build >> the devel image and followed the instructions in the wiki. But the >> following command fails with the error: >> >> *** >> >>make openmoko-devel-image >> >> ( cd build && . ../setup-env && \ >> ( bitbake openmoko-devel-image u-boot-openmoko ) ) >> ERROR: Openembedded's config sanity checker detected a potential >> misconfiguration. >> Either fix the cause of this error or at your own risk disable the >> checker (see sanity.conf). >> Following is the list of potential problems / advisories: >> >> /proc/sys/vm/mmap_min_addr is not 0. This will cause problems with >> qemu so please fix the value (as root). >> >> make: *** [openmoko-devel-image] Error 1 >> ** >> >> Can anyone suggest me the way for fixing this . >> >> Thanks.. >> >> >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> >> > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- Saurabh Gupta Senior, Electronics and Communication Engg. NSIT,New Delhi, India ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
On Sunday 31 August 2008, Michael Kluge wrote: > Yes. Compiling pixman breaks with an unresolved symbol > "pixman...something". There was a message about this on devel on Aug. > 13 and the answer was like "please wait 1 or 2 weeks, sources will be > fixed until then". If I remember well - I am an old man ... - . This happened only if you tried to build FSO in the openmoko environment. Do not do that. I looked into the different builds. The last time pixmap was build in a "testing" on my machine was the 14.8. (Aug.14). It was not different from earlier builds in stable or dev. Same source, same result. If you want to build FSO / SHR: http://shr.bearstech.com/README I copied the Makefiles and scripts from that machine and build FSO successfully, too. There were only minor problems with svn predicates. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
> > Which branch from asu? dev? stable? > All 3: stable, testing and dev > ( org.openmoko.asu.stable, org.openmoko.asu.testing, > org.openmoko.asu.dev) OK. Cool. Then there is hope for me. > Did you try again?: Not a completely fresh setup. I'll give this a try. > make setup && make update && make openmoko-qtopia-x11-image > Did you look through the error messages? Yes. Compiling pixman breaks with an unresolved symbol "pixman...something". There was a message about this on devel on Aug. 13 and the answer was like "please wait 1 or 2 weeks, sources will be fixed until then". > Did you try to fix the problems? Not yet. Still try to figure out if this is a general or just my own problem. > Did you follow the "Build issues" part of the page? Yes. make clean-package-pixman and rebuilding it does not solve the problem. Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
On Sunday 31 August 2008, Michael Kluge wrote: > Which branch from asu? dev? stable? All 3: stable, testing and dev ( org.openmoko.asu.stable, org.openmoko.asu.testing, org.openmoko.asu.dev) > I is not a question how long it takes. For me a couple of packages are > broken in asu.stable. At least pixman and xtrans (or something like > this) do not compile. Did you try again?: make setup && make update && make openmoko-qtopia-x11-image Did you look through the error messages? Did you try to fix the problems? Did you follow the "Build issues" part of the page? Be aware that you overwrite your changes in Makefile, when making make update-makefile . What are the error messages? > It worked well for me for the 2007.04 stack. If you miss a source (i.e not able to connect) copy it from 2007.04, Load it from one of the source repositories on openmoko or oe. MfG ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
> > At the risk ob beeing called a parrot I want to ask the same question again: > > Is anyone able to build a 2008.08 image with Mokomakefile? >Yes, I am building all of the images. Which branch from asu? dev? stable? > It is slow. The first time you have to start the make over and over again until your are done... > But thats all in the wiki page. So you might need a day or two. I is not a question how long it takes. For me a couple of packages are broken in asu.stable. At least pixman and xtrans (or something like this) do not compile. > Do not use the parallel modus. It only breaks the make earlier. It worked well for me for the 2007.04 stack. Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
On Saturday 30 August 2008, Michael Kluge wrote: > At the risk ob beeing called a parrot I want to ask the same question > again: > > Is anyone able to build a 2008.08 image with Mokomakefile? Yes, I am building all of the images. It is slow. The first time you have to start the make over and over again until your are done... But thats all in the wiki page. So you might need a day or two. Do not use the parallel modus. It only breaks the make earlier. Some times you simply have to wait until sources get available. If you got your build(s). The daily update is simple and rather fast. The "meaning" of the different images is obviously a moving target. Dietmar Friede ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
On Saturday, 30. August 2008 15:17:35 Rod Whitby wrote: > OK, can you describe *exactly* how you built that released image and how > you build those updates/fixes, so that others can replicate. > 1) Git repo site > 2) Git repo URL > 3) Git repo branch > 4) DISTRO setting (assume openmoko, but please confirm) > 5) MACHINE setting (assume om-gta02, but please confirm) > 6) whether moko-autorev and/or fso-autorev is included > 7) The OS on which the image and updates are built > 8) The set of host OS packages installed on the machine on which the > image and updates are built. This should be answered by Julian or Graeme. Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
Marek Lindner wrote: > On Saturday, 30. August 2008 14:08:48 Rod Whitby wrote: >> I'm still waiting for Openmoko to decide which branch they are using, so >> I can advise people how to build Om2008.8 properly using MokoMakefile. > > The decision is made. Julian tried to explain it before but I can try it > again: > > >> It used to be org.openmoko.asu.stable, but then someone from openmoko >> said they were going to concentrate on org.openmoko.dev instead. > > org.openmoko.asu.stable is the current stable branch on which we base our > releases. We will continue to provide updates/fixes to make it work more > reliably. OK, can you describe *exactly* how you built that released image and how you build those updates/fixes, so that others can replicate. The level of detail found in http://shr.bearstech.com/README is appropriate: 1) Git repo site 2) Git repo URL 3) Git repo branch 4) DISTRO setting (assume openmoko, but please confirm) 5) MACHINE setting (assume om-gta02, but please confirm) 6) whether moko-autorev and/or fso-autorev is included 7) The OS on which the image and updates are built 8) The set of host OS packages installed on the machine on which the image and updates are built. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
On Saturday, 30. August 2008 14:08:48 Rod Whitby wrote: > I'm still waiting for Openmoko to decide which branch they are using, so > I can advise people how to build Om2008.8 properly using MokoMakefile. The decision is made. Julian tried to explain it before but I can try it again: > It used to be org.openmoko.asu.stable, but then someone from openmoko > said they were going to concentrate on org.openmoko.dev instead. org.openmoko.asu.stable is the current stable branch on which we base our releases. We will continue to provide updates/fixes to make it work more reliably. This way of releasing is too static and too hard to tweak. Therefore we started a new way of releasing - the "base / empty" image style that is coming out of org.openmoko.dev. It wont have other aplications preinstalled other than settings and installer. Everyone can create his "dream phone". Many things have to be merged and reorganized, so that it is work in progress. Once it proves to be stablized it will become our new stable. Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile
Michael Kluge wrote: > At the risk ob beeing called a parrot I want to ask the same question again: > > Is anyone able to build a 2008.08 image with Mokomakefile? > > This is the third time I am asking this. I really noone interested in this? > Did I miss anything and do we now build images a different way? I'm still waiting for Openmoko to decide which branch they are using, so I can advise people how to build Om2008.8 properly using MokoMakefile. It used to be org.openmoko.asu.stable, but then someone from openmoko said they were going to concentrate on org.openmoko.dev instead. I wish they would create a document like http://shr.bearstech.com/README so that *everyone* would know how they build their images and can replicate them outside of Openmoko. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Mokomakefile
At the risk ob beeing called a parrot I want to ask the same question again: Is anyone able to build a 2008.08 image with Mokomakefile? This is the third time I am asking this. I really noone interested in this? Did I miss anything and do we now build images a different way? Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem in building image using MokoMakefile
On Sun, Aug 24, 2008 at 1:01 AM, Luke Duncan <[EMAIL PROTECTED]> wrote: > I saw the same error and fixed it by doing this: > > su root > echo 0 > /proc/sys/vm/mmap_min_addr > exit > Thanks, the build has been started successfully. > > then try make again. > > Luke. > > > On Sat, Aug 23, 2008 at 11:26 AM, saurabh gupta < > [EMAIL PROTECTED]> wrote: > >> Hello everyone, >> >> Previously I was using toolchain to compile the programs, but now i need >> the openmoko setup and bitbake in my PC. I used the Mokomakefile to build >> the devel image and followed the instructions in the wiki. But the >> following command fails with the error: >> >> *** >> >>make openmoko-devel-image >> >> ( cd build && . ../setup-env && \ >> ( bitbake openmoko-devel-image u-boot-openmoko ) ) >> ERROR: Openembedded's config sanity checker detected a potential >> misconfiguration. >> Either fix the cause of this error or at your own risk disable the >> checker (see sanity.conf). >> Following is the list of potential problems / advisories: >> >> /proc/sys/vm/mmap_min_addr is not 0. This will cause problems with >> qemu so please fix the value (as root). >> >> make: *** [openmoko-devel-image] Error 1 >> ** >> >> Can anyone suggest me the way for fixing this . >> >> Thanks.. >> >> >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> >> > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- Saurabh Gupta Senior, Electronics and Communication Engg. NSIT,New Delhi, India ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem in building image using MokoMakefile
I saw the same error and fixed it by doing this: su root echo 0 > /proc/sys/vm/mmap_min_addr exit then try make again. Luke. On Sat, Aug 23, 2008 at 11:26 AM, saurabh gupta <[EMAIL PROTECTED]>wrote: > Hello everyone, > > Previously I was using toolchain to compile the programs, but now i need > the openmoko setup and bitbake in my PC. I used the Mokomakefile to build > the devel image and followed the instructions in the wiki. But the > following command fails with the error: > > *** > >>make openmoko-devel-image > > ( cd build && . ../setup-env && \ > ( bitbake openmoko-devel-image u-boot-openmoko ) ) > ERROR: Openembedded's config sanity checker detected a potential > misconfiguration. > Either fix the cause of this error or at your own risk disable the > checker (see sanity.conf). > Following is the list of potential problems / advisories: > > /proc/sys/vm/mmap_min_addr is not 0. This will cause problems with > qemu so please fix the value (as root). > > make: *** [openmoko-devel-image] Error 1 > ** > > Can anyone suggest me the way for fixing this . > > Thanks.. > > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Problem in building image using MokoMakefile
Hello everyone, Previously I was using toolchain to compile the programs, but now i need the openmoko setup and bitbake in my PC. I used the Mokomakefile to build the devel image and followed the instructions in the wiki. But the following command fails with the error: *** >>make openmoko-devel-image ( cd build && . ../setup-env && \ ( bitbake openmoko-devel-image u-boot-openmoko ) ) ERROR: Openembedded's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: /proc/sys/vm/mmap_min_addr is not 0. This will cause problems with qemu so please fix the value (as root). make: *** [openmoko-devel-image] Error 1 ** Can anyone suggest me the way for fixing this . Thanks.. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MokoMakeFile
Alasal wrote: > Is the MokoMakeFile still under development? It is, but it's difficult at the moment to get things to build correctly. > Is there any chance for flashing Om2008.8 on the qemu emulator? You can do this now by setting the branch correctly. See the MokoMakefile wiki page for details of how to build asu.testing -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MokoMakeFile
Hey, Is the MokoMakeFile still under development? Is there any chance for flashing Om2008.8 on the qemu emulator? -- View this message in context: http://n2.nabble.com/MokoMakeFile-tp724232p724232.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile on Debian on PowerPC64/G5
On Thu, Jul 31, 2008 at 10:56:23AM +0200, Robert Schuster wrote:
> Hi,
> I am building OpenEmbedded stuff (OpenMoko for FreeRunner, Angstrom for
> BeagleBoard) on my Fedora G4 iBook all day and it works.
Like the OP, I am attempting to build OM with MokoMakefile on debian
powerpc (a PowerMac G5).
> Please paste your error message to a pastebin service and provide the
> URL here.
The output from my attempted build is at http://pastebin.com/m19248e62
I did:
make clean
rm -rf build/conf/
make setup
make setup-machine-freerunner
make openmoko-devel-image
(Download of stuff isn't in this output because I've run this several
times before.)
setup-env contains:
export OMDIR="/home/russells/omdir"
export BBPATH="${OMDIR}/build:${OMDIR}/openembedded"
export PYTHONPATH="${OMDIR}/bitbake/libbitbake"
export PATH="${OMDIR}/bitbake/bin:${PATH}"
build/conf/local.conf contains:
MACHINE = "om-gta02"
DISTRO = "openmoko"
BUILD_ARCH = "ppc64"
INHERIT += "rm_work"
The third NOTE in the output at http://pastebin.com/m19248e62 is
Information not available for target 'ppc64-linux'
which I think is partly gathered from `uname -m`. On my system:
[EMAIL PROTECTED]:~$ uname -m
ppc64
Is this different from what uname -m says on Fedora? I notice that
there is a powerpc* target in some of the .bb files.
I don't know anything about bitbake, and its output seems unconducive
to casual debugging in that there is not a lot of context for the
messages.
Any ideas?
--
Russell Steicke
-- Fortune says:
By nature, men are nearly alike; by practice, they get to be wide apart.
-- Confucius
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Mokomakefile on Debian on PowerPC64/G5
Hi, I am building OpenEmbedded stuff (OpenMoko for FreeRunner, Angstrom for BeagleBoard) on my Fedora G4 iBook all day and it works. Please paste your error message to a pastebin service and provide the URL here. Regards Robert Christ van Willegen schrieb: > Hi, > > I guess I'm the first one to try this... > > Because there is no (native) support for building OpenMoko software on > an iMac (G5, rev c with iSight), I decided to see if installing Debian > would work. > > Following the instructions on [1] I was able to install Debian 'just > fine'. In short, you don't get X and gdm... > > Then, I followed the usual instructions about Mokomakefile and its > prerequisites. > > Building the OE environment gave me an error - powerpc64 architecture > not supported (or something close to that). If this doesn't ring any > bells, I'll check and get the exact wording later. > > Is that something that can be fixed by me, or is it simply impossible > to do this on a powerPC64 architecture? I don't need Qemu, I'll have > my Freerunner soon, but probably no working ways to build software for > it... > > Regards, > > Christ van Willegen > > [1] <http://www.justlinux.com/forum/archive/index.php/t-150809.html> signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
Al Johnson wrote: > > That's frustrating. I had imagined the gadget functions could coexist so we > could provide both network and storage. > Even if the gadget ether is built as module, it does not give necessarily the possibility to load another gadget. AIUI, only one gadget device can be installed at any time. Gilles ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
On Monday 28 July 2008, Jay Vaughan wrote: > >> You can't use other Gadget devices currently, because Gadget-Ethernet > >> is compiled into the kernel (not as a module) and this precludes any > >> other gadget drivers from loading. As I am currently working on > >> Gadget Audio for the Freerunner, I too would like to see this > >> situation resolved properly at the distribution level. > > > > That's frustrating. I had imagined the gadget functions could > > coexist so we > > could provide both network and storage. > > It sure is frustrating, and imho is a bit of an oversight on the part > of whoever-it-is that is responsible for making command decisions > about the configuration of the OpenMoko distro. Personally I think > for sure we need to pile on as many g_* drivers as possible, and that > means reconfiguring the current distros to make g_ethernet a module, > not compiled -in .. I had the naive hope that modprobing multiple gadget drivers would give you a composite device, but a little searching shows it doesn't work that way. It seems there is work under way for a composite gadget framework that may allow something close to that, subject to controller limitations such as the number of available endpoints. http://blog.felipebalbi.com/?p=44 http://www.linux-usb.org/gadget/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
>> You can't use other Gadget devices currently, because Gadget-Ethernet >> is compiled into the kernel (not as a module) and this precludes any >> other gadget drivers from loading. As I am currently working on >> Gadget Audio for the Freerunner, I too would like to see this >> situation resolved properly at the distribution level. > > That's frustrating. I had imagined the gadget functions could > coexist so we > could provide both network and storage. > It sure is frustrating, and imho is a bit of an oversight on the part of whoever-it-is that is responsible for making command decisions about the configuration of the OpenMoko distro. Personally I think for sure we need to pile on as many g_* drivers as possible, and that means reconfiguring the current distros to make g_ethernet a module, not compiled -in .. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
On Monday 28 July 2008, Jay Vaughan wrote: > > I want to compile the USB GADGED STORAGE module for the kernel how I > > have to > > do this? > > You can't use other Gadget devices currently, because Gadget-Ethernet > is compiled into the kernel (not as a module) and this precludes any > other gadget drivers from loading. As I am currently working on > Gadget Audio for the Freerunner, I too would like to see this > situation resolved properly at the distribution level. That's frustrating. I had imagined the gadget functions could coexist so we could provide both network and storage. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
> I want to compile the USB GADGED STORAGE module for the kernel how I > have to > do this? You can't use other Gadget devices currently, because Gadget-Ethernet is compiled into the kernel (not as a module) and this precludes any other gadget drivers from loading. As I am currently working on Gadget Audio for the Freerunner, I too would like to see this situation resolved properly at the distribution level. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Howto compile more kernel modules with MokoMakefile?
Alexander Check the modules tarball. It's released with firmware images. I used it for the modules I needed for a few usb devices. Brad On Sat, Jul 26, 2008 at 5:39 AM, Alexander Syring <[EMAIL PROTECTED]> wrote: > Hi > I want to compile the USB GADGED STORAGE module for the kernel how I have to > do this? -- Brad ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Howto compile more kernel modules with MokoMakefile?
Hi I want to compile the USB GADGED STORAGE module for the kernel how I have to do this? Which files I have to change or to create? Can I have an "make menuconfig" for kernel? And if yes how do I start it right? with make ARCH=arm4 menuconfig ? thx & regards Alex ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Mokomakefile on Debian on PowerPC64/G5
Hi, I guess I'm the first one to try this... Because there is no (native) support for building OpenMoko software on an iMac (G5, rev c with iSight), I decided to see if installing Debian would work. Following the instructions on [1] I was able to install Debian 'just fine'. In short, you don't get X and gdm... Then, I followed the usual instructions about Mokomakefile and its prerequisites. Building the OE environment gave me an error - powerpc64 architecture not supported (or something close to that). If this doesn't ring any bells, I'll check and get the exact wording later. Is that something that can be fixed by me, or is it simply impossible to do this on a powerPC64 architecture? I don't need Qemu, I'll have my Freerunner soon, but probably no working ways to build software for it... Regards, Christ van Willegen [1] <http://www.justlinux.com/forum/archive/index.php/t-150809.html> -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
How could I add packages to mokomakefile Image?
Hi How could I add packages to the flash image? Because I build an image with Mokomakefile and after flashing it to my Freerunner i have to add so much packages with opgk. And if I could add the default to the image it would be great. regards Alex ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Does this MokoMakefile build error matter?
On Friday 18 July 2008, Vijay Vaidyanathan wrote: > I'm trying to create an amazon EC2 image that will have a pre-built > ASU (including the .o files yes, I realize this might be a 12G+ image!) > > I'm using MokoMakefile, and I've fixed a few minor problems along the > way on Ubuntu 8.04 (and will update the wiki) but I dont know if this > is an issue I need to worry about since it seems to keep going in > spite of the error message > > ERROR: Multiple .bb files are due to be built which each provide > virtual/xserver (/home/openmoko/work/om/asu/openembedded/packages/ > xorg-xserver/xserver-kdrive-glamo_1.3.0.0+git.bb /home/openmoko/work/ > om/asu/openembedded/packages/xorg-xserver/xserver-kdrive_1.3.0.0.bb). > This usually means one provides something the other doesn't and should. I've seen that error and my images have worked so far, so I don't think it's a showstopper. > > If I am ever able to get the build to work, I'll post the amazon EC2 > Image and mark it public. > > - VV > > > PS: The machine is a Amazon EC2 High-CPU Medium Instance (c1.medium) > at 0.20 cents per hour :-) and after a few hours of compilation I'm > wondering if I should have created a High-Cpu Extra Large instance > instead :-) > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Does this MokoMakefile build error matter?
I'm trying to create an amazon EC2 image that will have a pre-built ASU (including the .o files yes, I realize this might be a 12G+ image!) I'm using MokoMakefile, and I've fixed a few minor problems along the way on Ubuntu 8.04 (and will update the wiki) but I dont know if this is an issue I need to worry about since it seems to keep going in spite of the error message ERROR: Multiple .bb files are due to be built which each provide virtual/xserver (/home/openmoko/work/om/asu/openembedded/packages/ xorg-xserver/xserver-kdrive-glamo_1.3.0.0+git.bb /home/openmoko/work/ om/asu/openembedded/packages/xorg-xserver/xserver-kdrive_1.3.0.0.bb). This usually means one provides something the other doesn't and should. If I am ever able to get the build to work, I'll post the amazon EC2 Image and mark it public. - VV PS: The machine is a Amazon EC2 High-CPU Medium Instance (c1.medium) at 0.20 cents per hour :-) and after a few hours of compilation I'm wondering if I should have created a High-Cpu Extra Large instance instead :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
On Wed, Jul 16, 2008 at 5:18 PM, arne anka <[EMAIL PROTECTED]> wrote: > > Why is makefile still downloading the previous buggy images of gta01. > > afaik is qemu unable to handle the gta02 images, only gta01. Ok thanks... But has anyone tried the patch for emulating the gta02 under qemu as given in wiki. > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- Saurabh Gupta Electronics and Communication Engg. NSIT,New Delhi, India ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
> Why is makefile still downloading the previous buggy images of gta01. afaik is qemu unable to handle the gta02 images, only gta01. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
On Fri, Jul 11, 2008 at 12:09 AM, Søren Kristiansen <[EMAIL PROTECTED]> wrote: > Just download the newest images from the buildhost and place them in > images/openmoko/ and do: > make flash-qemu-official > make run-qemu I downloaded the latest images of gta02 in the directory and then run make flash-qemu-official, but it is showing an error. It is searching the gta01 images in the images/openmoko directory and thus exits with an error that basename: missing operator. I even did the make update-makefile, but no improvement. Any suggestions. Why is makefile still downloading the previous buggy images of gta01. Regards. > > I dont know why but it downloads an old bugged image (bugged in the > emulator at least... dunno if it works on any of the neos) > > 2008/7/10 <[EMAIL PROTECTED]>: > > > I've been wanting to test out the UI that is shown on the wiki and >> > software reviews around the net. Upon building (make qemu) and letting >> it >> > complete I got a very different UI that what I expected. Here's a couple >> of >> > screenshots: http://projektenterprises.com/mokoshots/ >> >> I think is a Qtopia image. >> >> looks like monomakefile is downloading the qtopia jffs2 from >> buildhost.automated.it to de NAND of qemu >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> > > > > -- > Med venlig hilsen / Best regards > > Søren H. Kristiansen > > Stud. polyt., Software Engineering, University of Aalborg, Denmark > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- Saurabh Gupta Electronics and Communication Engg. NSIT,New Delhi, India ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
Thanks again so much! I couldn't hold back. I was able to get the daily build to run on QEMU, will have to play with it more at work. -Shawn On Thu, Jul 10, 2008 at 11:39 AM, Søren Kristiansen <[EMAIL PROTECTED]> wrote: > Just download the newest images from the buildhost and place them in > images/openmoko/ and do: > make flash-qemu-official > make run-qemu > > I dont know why but it downloads an old bugged image (bugged in the > emulator at least... dunno if it works on any of the neos) > > 2008/7/10 <[EMAIL PROTECTED]>: > > > I've been wanting to test out the UI that is shown on the wiki and >> > software reviews around the net. Upon building (make qemu) and letting >> it >> > complete I got a very different UI that what I expected. Here's a couple >> of >> > screenshots: http://projektenterprises.com/mokoshots/ >> >> I think is a Qtopia image. >> >> looks like monomakefile is downloading the qtopia jffs2 from >> buildhost.automated.it to de NAND of qemu >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> > > > > -- > Med venlig hilsen / Best regards > > Søren H. Kristiansen > > Stud. polyt., Software Engineering, University of Aalborg, Denmark > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
Thank you Søren. I will give that a try tonight while I'm bored at work after-hours. -Shawn On Thu, Jul 10, 2008 at 11:39 AM, Søren Kristiansen <[EMAIL PROTECTED]> wrote: > Just download the newest images from the buildhost and place them in > images/openmoko/ and do: > make flash-qemu-official > make run-qemu > > I dont know why but it downloads an old bugged image (bugged in the > emulator at least... dunno if it works on any of the neos) > > 2008/7/10 <[EMAIL PROTECTED]>: > > > I've been wanting to test out the UI that is shown on the wiki and >> > software reviews around the net. Upon building (make qemu) and letting >> it >> > complete I got a very different UI that what I expected. Here's a couple >> of >> > screenshots: http://projektenterprises.com/mokoshots/ >> >> I think is a Qtopia image. >> >> looks like monomakefile is downloading the qtopia jffs2 from >> buildhost.automated.it to de NAND of qemu >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> > > > > -- > Med venlig hilsen / Best regards > > Søren H. Kristiansen > > Stud. polyt., Software Engineering, University of Aalborg, Denmark > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
Just download the newest images from the buildhost and place them in images/openmoko/ and do: make flash-qemu-official make run-qemu I dont know why but it downloads an old bugged image (bugged in the emulator at least... dunno if it works on any of the neos) 2008/7/10 <[EMAIL PROTECTED]>: > > I've been wanting to test out the UI that is shown on the wiki and > > software reviews around the net. Upon building (make qemu) and letting it > > complete I got a very different UI that what I expected. Here's a couple > of > > screenshots: http://projektenterprises.com/mokoshots/ > > I think is a Qtopia image. > > looks like monomakefile is downloading the qtopia jffs2 from > buildhost.automated.it to de NAND of qemu > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- Med venlig hilsen / Best regards Søren H. Kristiansen Stud. polyt., Software Engineering, University of Aalborg, Denmark ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
> I've been wanting to test out the UI that is shown on the wiki and > software reviews around the net. Upon building (make qemu) and letting it > complete I got a very different UI that what I expected. Here's a couple of > screenshots: http://projektenterprises.com/mokoshots/ I think is a Qtopia image. looks like monomakefile is downloading the qtopia jffs2 from buildhost.automated.it to de NAND of qemu ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
make build-package-claws-mail with mokomakefile fails
Hi all,
there is a problem building claws-mail which is included as version 3.3 in the
openembedded path. I have the latest copy of the Mokomakefile development
environment as well as the toolchain
(http://wiki.openmoko.org/wiki/Toolchain) installed.
Running "make build-package-claws-mail" fails during the compile stage at a
point where it looks like the arm-gcc tries to compile some C++ code and
fails finding libstdc++.6.so. Adding 'CC="${CXX} LD="${CXX}"' to EXTRA_OECONF
(seen in other packages) ends with an error during the configure stage that
says:
...
autoreconf: running:
automake --foreign --add-missing --copy --force-missing --warnings=cross
automake: unknown warning category `cross'
autoreconf: running: gnu-configize
autoreconf: Leaving directory `.'
arm-angstrom-linux-gnueabi-g++: arm-angstrom-linux-gnueabi-g++: No such file
or directory
arm-angstrom-linux-gnueabi-g++: no input files
I think the dependency to libstdc++ comes from an external library used by
claws-mail.
Did I handle this C vs. C++ problem in the BB files correctly or is there an
other preferred way to tackle this?
The error message:
"arm-angstrom-linux-gnueabi-g++: arm-angstrom-linux-gnueabi-g++: No such file
or directory"
does not tell me so much. If anyone want to have fun looking into the logs I
can send them around as well.
Regards, Michael
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
On Thu, Jul 10, 2008 at 7:02 PM, Shawn Thompson < [EMAIL PROTECTED]> wrote: > I've been wanting to test out the UI that is shown on the wiki and software > reviews around the net. Upon building (make qemu) and letting it complete I > got a very different UI that what I expected. Here's a couple of > screenshots: http://projektenterprises.com/mokoshots/ > I too got exactly the same UI in qemu when I build it using "make qemu" command using the MokoMakefile. > > Any ideas as to why I am getting this UI instead of the one I've seen > across the web, I'm sure I had to have messed up along the way somewhere. > > -Shawn T. > > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
make qemu On Thu, Jul 10, 2008 at 6:44 AM, David Samblas Martinez <[EMAIL PROTECTED]> wrote: > what make instruction did you use? > > It begins like the ASU image file but as you notice I have no seen this > initial screen before. > > > --- El jue, 10/7/08, Shawn Thompson <[EMAIL PROTECTED]> > escribió: > > > De: Shawn Thompson <[EMAIL PROTECTED]> > > Asunto: Problem with QEMU and MokoMakefile > > Para: "OM-Community" > > Fecha: jueves, 10 julio, 2008 3:32 > > I've been wanting to test out the UI that is shown on > > the wiki and software > > reviews around the net. Upon building (make qemu) and > > letting it complete I > > got a very different UI that what I expected. Here's a > > couple of > > screenshots: http://projektenterprises.com/mokoshots/ > > > > Any ideas as to why I am getting this UI instead of the one > > I've seen across > > the web, I'm sure I had to have messed up along the way > > somewhere. > > > > -Shawn T.___ > > Openmoko community mailing list > > community@lists.openmoko.org > > http://lists.openmoko.org/mailman/listinfo/community > > > __ > Enviado desde Correo Yahoo! La bandeja de entrada más inteligente. > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
what make instruction did you use? It begins like the ASU image file but as you notice I have no seen this initial screen before. --- El jue, 10/7/08, Shawn Thompson <[EMAIL PROTECTED]> escribió: > De: Shawn Thompson <[EMAIL PROTECTED]> > Asunto: Problem with QEMU and MokoMakefile > Para: "OM-Community" > Fecha: jueves, 10 julio, 2008 3:32 > I've been wanting to test out the UI that is shown on > the wiki and software > reviews around the net. Upon building (make qemu) and > letting it complete I > got a very different UI that what I expected. Here's a > couple of > screenshots: http://projektenterprises.com/mokoshots/ > > Any ideas as to why I am getting this UI instead of the one > I've seen across > the web, I'm sure I had to have messed up along the way > somewhere. > > -Shawn T.___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community __ Enviado desde Correo Yahoo! La bandeja de entrada más inteligente. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with QEMU and MokoMakefile
> got a very different UI that what I expected. Here's a couple of
> screenshots: http://projektenterprises.com/mokoshots/
that would be asu, i think.
> Any ideas as to why I am getting this UI instead of the one I've seen
> across
> the web, I'm sure I had to have messed up along the way somewhere.
i think asu is the default image to build. probably to change somwhere, try
find . -type f -exec grep -iH asu '{}' \;
when in the directory mokomakefile lives in.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Problem with QEMU and MokoMakefile
I've been wanting to test out the UI that is shown on the wiki and software reviews around the net. Upon building (make qemu) and letting it complete I got a very different UI that what I expected. Here's a couple of screenshots: http://projektenterprises.com/mokoshots/ Any ideas as to why I am getting this UI instead of the one I've seen across the web, I'm sure I had to have messed up along the way somewhere. -Shawn T. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: mokomakefile, eclipse
arne anka <[EMAIL PROTECTED]> writes: > firstly, debian/sid does not know cogito and g++-3.4 anymore. while cogito cogito is abandoned > g++-3.4 is not avaliable at all. > is it needed for anything else but qemu? qemu need its. a good guide for getting gcc-3.4 is here http://www.tellurian.com.au/whitepapers/multiplegcc.php > secondly: i fail to see, where the often mentioned build/ directory comes > from. is it created by a target of mokomakefile? yes ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
mokomakefile, eclipse
hi, right now i am trying to set up a build environment w/ mokomakefile on debian/unstable following > http://wiki.openmoko.org/wiki/MokoMakefile firstly, debian/sid does not know cogito and g++-3.4 anymore. while cogito uis replaced with several *git* packages ( Package cogito is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: gitk git-svn git-email git-cvs git-core git-arch ), g++-3.4 is not avaliable at all. is it needed for anything else but qemu? secondly: i fail to see, where the often mentioned build/ directory comes from. is it created by a target of mokomakefile? thirdly: does anyone use eclipse to develop and could share a few hints about how to set up eclipse for openmoko? regards ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MokoMakefile Build Issues
I'm attempting to build an ASU image from the asu.stable branch on a Debian Etch system (AMD64 arch) using MokoMakefile. I've edited the makefile to echo gta02 to local.conf instead of 01 and changed GIT_BRANCH to asu.stable. I've also followed the wiki instructions for building an image but there is the first error for me. Running make update gives me the following error: [EMAIL PROTECTED]:~/moko$ make update ( cd bitbake && \ ( git branch | egrep -e ' bitbake-om$' > /dev/null || \ git checkout -b bitbake-om --track origin/bitbake-om )) ( cd bitbake && \ git checkout bitbake-om && \ git fetch && \ git rebase origin/bitbake-om ) fatal: Needed a single revision invalid upstream origin/bitbake-om make: *** [update-bitbake] Error 1 When building openmoko-qtopia-x11-image it seems to work properly up until it attempts to build qtopia-phone-x11 which throws the errors found at http://pastebin.com/m362d7e90 I've followed the wiki instructions, including cleaning the failed package and trying thrice before complaining. :) I'd really like to build my own images, since it appears the images on the official buildhost are constantly out of date. Any help in resolving these issues would be greatly appreciated! -Kevin Dean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
Mo Abrahams wrote: On Wed, 2008-05-21 at 17:49 +0930, Rod Whitby wrote: MokoMakefile has been updated, tested by a couple of people, and now published. You will need to run "make clobber update-makefile" before proceeding in the usual way ... > > What does the "clobber" bit do? It removes the openembedded and bitbake monotone checkout directories, to allow git to recreate them from the openmoko git repositories. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
Tom Cooksey wrote: On Wednesday 21 May 2008 10:19:49 Rod Whitby wrote: Holger Freyther wrote: To unify our tools we have reduced the number of SCMs to learn from three to two. This means we only use subversion and git for now. I have moved the Openembedded metadata from monotone to git. ... An updated MokoMakefile will, thanks to Rod, follow shortly. MokoMakefile has been updated, tested by a couple of people, and now published. I'm trying to build from scratch and get the following: "( cd openembedded && git checkout org.openmoko.april-update ) error: pathspec 'org.openmoko.april-update' did not match any file(s) known to git. Did you forget to 'git add'?" I think you need an extra step in there between git clone & git checkout, to create a local git branch which tracks the origin's branch, something like this: This has now been added. Thanks. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
> Ahhh... Much better. :) > > Now let's see if I can run a "make update all"... And thanks a lot. signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
Ahhh... Much better. :) Now let's see if I can run a "make update all"... -- (GNU) PGP ID: 0x4D385570 Weblog: http://blog.mxchange.org signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
On Wednesday 21 May 2008 13:13:33 Roland Häder wrote:
> On Wednesday, 21. May 2008, Tom Cooksey wrote:
> > On Wednesday 21 May 2008 10:19:49 Rod Whitby wrote:
> > > Holger Freyther wrote:
> > > > To unify our tools we have reduced the number of SCMs to learn from
> > > > three to two. This means we only use subversion and git for now. I have
> > > > moved the Openembedded metadata from monotone to git.
> > >
> > > ...
> > >
> > > > An updated MokoMakefile will, thanks to Rod, follow shortly.
> > >
> > > MokoMakefile has been updated, tested by a couple of people, and now
> > > published.
> >
> > I'm trying to build from scratch and get the following:
> >
> > "( cd openembedded && git checkout org.openmoko.april-update )
> > error: pathspec 'org.openmoko.april-update' did not match any file(s) known
> > to git. Did you forget to 'git add'?"
> I got the same error message here. Something seems to be missing (I'm not
> familar with git).
>
> Roland
>
Edit the Makefile and around line ~83, make it look like this:
setup-openembedded stamps/openembedded:
( [ -e stamps/openembedded ] && \
[ -e openembedded/.git ] ) || \
( git clone -n git://${OM_GIT_SITE}/git/openmoko.git openembedded )
( cd openembedded && git branch --track ${OM_GIT_BRANCH}
origin/${OM_GIT_BRANCH} )
( cd openembedded && git checkout ${OM_GIT_BRANCH} )
[ -d stamps ] || mkdir stamps
touch stamps/openembedded
The only difference is the "git branch" line, so you can just add that in the
right place.
My build's still going, but hasn't messed up yet. Certainly all the git related
stuff has
worked.
PS: Thanks to switching to git... at least I can figure out failures by myself
now!
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
What does the "clobber" bit do? On Wed, 2008-05-21 at 17:49 +0930, Rod Whitby wrote: > Holger Freyther wrote: > > To unify our tools we have reduced the number of SCMs to learn from three > > to > > two. This means we only use subversion and git for now. I have moved the > > Openembedded metadata from monotone to git. > ... > > An updated MokoMakefile will, thanks to Rod, follow shortly. > > MokoMakefile has been updated, tested by a couple of people, and now > published. > > You will need to run "make clobber update-makefile" before proceeding in > the usual way ... > > The good thing is that even though Openmoko has completely changed > configuration management systems, the commands you use with MokoMakefile > to build images don't change at all :-) > > So only read http://wiki.openmoko.org/wiki/MokoMakefile if you haven't > read it before. The only change I made was to remove all monotone > references ... > > -- Rod > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
On Wednesday, 21. May 2008, Tom Cooksey wrote: > On Wednesday 21 May 2008 10:19:49 Rod Whitby wrote: > > Holger Freyther wrote: > > > To unify our tools we have reduced the number of SCMs to learn from > > > three to two. This means we only use subversion and git for now. I have > > > moved the Openembedded metadata from monotone to git. > > > > ... > > > > > An updated MokoMakefile will, thanks to Rod, follow shortly. > > > > MokoMakefile has been updated, tested by a couple of people, and now > > published. > > I'm trying to build from scratch and get the following: > > "( cd openembedded && git checkout org.openmoko.april-update ) > error: pathspec 'org.openmoko.april-update' did not match any file(s) known > to git. Did you forget to 'git add'?" I got the same error message here. Something seems to be missing (I'm not familar with git). Roland signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Announcement] MokoMakefile updated for switch to git
On Wednesday 21 May 2008 10:19:49 Rod Whitby wrote:
> Holger Freyther wrote:
> > To unify our tools we have reduced the number of SCMs to learn from three
> > to
> > two. This means we only use subversion and git for now. I have moved the
> > Openembedded metadata from monotone to git.
> ...
> > An updated MokoMakefile will, thanks to Rod, follow shortly.
>
> MokoMakefile has been updated, tested by a couple of people, and now
> published.
I'm trying to build from scratch and get the following:
"( cd openembedded && git checkout org.openmoko.april-update )
error: pathspec 'org.openmoko.april-update' did not match any file(s) known to
git.
Did you forget to 'git add'?"
I think you need an extra step in there between git clone & git checkout, to
create a
local git branch which tracks the origin's branch, something like this:
git branch --track ${OM_GIT_BRANCH} origin/${OM_GIT_BRANCH}
Then the git checkout will refer to a local branch. I think you'll probably
need something
similar for bitbake - it works at the moment by fluke. :-)
This is working for me anyway (so far!).
Cheers,
Tom
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
[Announcement] MokoMakefile updated for switch to git
Holger Freyther wrote: To unify our tools we have reduced the number of SCMs to learn from three to two. This means we only use subversion and git for now. I have moved the Openembedded metadata from monotone to git. ... An updated MokoMakefile will, thanks to Rod, follow shortly. MokoMakefile has been updated, tested by a couple of people, and now published. You will need to run "make clobber update-makefile" before proceeding in the usual way ... The good thing is that even though Openmoko has completely changed configuration management systems, the commands you use with MokoMakefile to build images don't change at all :-) So only read http://wiki.openmoko.org/wiki/MokoMakefile if you haven't read it before. The only change I made was to remove all monotone references ... -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
help:Neo1973 emulation using mokomakefile
Dear sir,
i am using ubuntu-7.10 in my PC.when i am trying to install using
mokomakefile i got this error,please help me.here i give what i
done,what error i got.
Step 1:
i installed all required packages to my machine
.including gcc-3.4
step 2:
$ sudo dpkg-reconfigure dash
choosed NO upon question about installing /bin/sh
step 3:
$mkdir openmoko
$cd openmoko
$wget http://www.rwhitby.net/files/openmoko/Makefile
$make qemu
=
when using this command it downloads all but finally
gives error message some thing like this
svn: REPORT request failed on '/!svn/vcc/default'
svn: REPORT of '/!svn/vcc/default': 200 OK
(http://svn.openmoko.org)
make: *** [stamps/openmoko] Error 1
when i run $make qemu i got the following error
[EMAIL PROTECTED]:~/openmoko$ make qemu
[ -e setup-env ] || \
echo 'export OMDIR="'`pwd`'"' > setup-env
echo \
'export BBPATH="${OMDIR}/build:${OMDIR}/openembedded"' \
>> setup-env
echo \
'export PYTHONPATH="${OMDIR}/bitbake/libbitbake"' \
>> setup-env
echo \
'export PATH="${OMDIR}/bitbake/bin:${PATH}"' \
>> setup-env
[ -e stamps/patches ] || \
( svn co
http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/patches
patches )
Apatches/bitbake-HEAD
Apatches/openmoko-HEAD
Apatches/openembedded-HEAD
Checked out revision 14.
[ -d stamps ] || mkdir stamps
touch stamps/patches
[ -e openmoko ] || ( mkdir openmoko )
[ -e stamps/openmoko ] || [ -e openmoko/trunk/.svn/entries ] || \
( cd openmoko && svn co -r HEAD http://svn.openmoko.org/trunk )
Atrunk/doc
Atrunk/doc/hardware
Atrunk/doc/hardware/HXD8v011
Atrunk/doc/hardware/HXD8v011/gpio.txt
Atrunk/doc/hardware/HXD8v011/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v1
Atrunk/doc/hardware/GTA02v1/gpio.txt
Atrunk/doc/hardware/GTA01v3
Atrunk/doc/hardware/GTA01v3/lcm-init-regs.txt
Atrunk/doc/hardware/GTA01v3/gpio.txt
Atrunk/doc/hardware/GTA01v3/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v2
Atrunk/doc/hardware/GTA02v2/gpio.txt
Atrunk/doc/hardware/GTA01Bv2
Atrunk/doc/hardware/GTA01Bv2/gpio.txt
Atrunk/doc/hardware/GTA01Bv2/pmu-voltage.txt
Atrunk/doc/hardware/GTA01v4
Atrunk/doc/hardware/GTA01v4/gpio.txt
Atrunk/doc/hardware/GTA01v4/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v3
Atrunk/doc/hardware/GTA02v3/gpio.txt
Atrunk/doc/hardware/GTA01Bv3
Atrunk/doc/hardware/GTA01Bv3/gpio.txt
Atrunk/doc/hardware/GTA01Bv3/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v4
Atrunk/doc/hardware/GTA02v4/gpio.txt
Atrunk/doc/hardware/GTA01Bv4
Atrunk/doc/hardware/GTA01Bv4/gpio.txt
Atrunk/doc/hardware/GTA01Bv4/pmu-voltage.txt
Atrunk/doc/hardware/SMDK2440
Atrunk/doc/hardware/SMDK2440/gpio.txt
Atrunk/src
Atrunk/src/target
Atrunk/src/target/kernel
Atrunk/src/target/kernel/config
Atrunk/src/target/kernel/config/defconfig-2.6.22.5
Atrunk/src/target/kernel/patches
Atrunk/src/target/kernel/patches/s3c24xx-nand-largepage.patch
Atrunk/src/target/kernel/patches/s3c2410_fb-truecolor.patch
Atrunk/src/target/kernel/patches/s3c_mci_platform.patch
Atrunk/src/target/kernel/patches/asoc-kconfig-fix.patch
Atrunk/src/target/kernel/patches/s3cmci-unfinished-write-fix.patch
Atrunk/src/target/kernel/patches/s3cmci-stop-fix.patch
Atrunk/src/target/kernel/patches/gta01-inputdevice.patch
Atrunk/src/target/kernel/patches/lis302dl.patch
Atrunk/src/target/kernel/patches/s3c2410_fb-line_length.patch
Atrunk/src/target/kernel/patches/series
Atrunk/src/target/kernel/patches/s3c2410_udc_from_upstream.patch
Atrunk/src/target/kernel/patches/s3cmci_dbg.patch
Atrunk/src/target/kernel/patches/i2c-permit_invalid_addrs.patch
Atrunk/src/target/kernel/patches/ts0710.patch
Atrunk/src/target/kernel/patches/s3cmci-dma-free.patch
Atrunk/src/target/kernel/patches/smedia-glamo.patch
Atrunk/src/target/kernel/patches/hxd8-tsl256x.patch
Atrunk/src/target/kernel/patches/qt2410-s3c_mci-pdata.patch
Atrunk/src/target/kernel/patches/s3c2410-pwm.patch
Atrunk/src/target/kernel/patches/fix-hwecc-2410.patch
Atrunk/src/target/kernel/patches/gta01-vibrator.patch
Atrunk/src/target/kernel/patches/gta02-core.patch
Atrunk/src/target/kernel/patches/qt2410-base.patch
Atrunk/src/target/kernel/patches/s3c2410-bbt.patch
Atrunk/src/target/kernel/patches/gta01-jbt6k74.patch
Atrunk/src/target/kernel/patches/gta01-power_control.patch
A
t
Re: Problem trying to build qemu-local using MokoMakefile
François TOURDE wrote: Hi, Trying to run "make qemu-local", I got the following message, some lines after "Please wait, programming the NAND flash..." -8<---8<---8<---8<---8<-- neo_vib_switch: Vibrator stopped. neo_bl_switch: LCD Backlight now on. qemu: fatal: Trying to execute code outside RAM or ROM at 0x -8<---8<---8<---8<---8<-- (More detailed trace can be found here: http://pastebin.com/m239ade67) Got the same error on Debian sid ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Problem trying to build qemu-local using MokoMakefile
Hi, Trying to run "make qemu-local", I got the following message, some lines after "Please wait, programming the NAND flash..." -8<---8<---8<---8<---8<-- neo_vib_switch: Vibrator stopped. neo_bl_switch: LCD Backlight now on. qemu: fatal: Trying to execute code outside RAM or ROM at 0x -8<---8<---8<---8<---8<-- (More detailed trace can be found here: http://pastebin.com/m239ade67) Any idea? Thanks in advance. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Qtopia and MokoMakeFile
Anyone using MokoMakeFile to build Qtopia yet? I used it Sunday but it looked like a very old image. Just wondering if it's not being updated yet or if the latest snapshot just looks old. Richard ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko OE repository not quite ready for MokoMakefile production usage
On Fri, Nov 30, 2007 at 01:05:11PM +0100, Jay Vaughan wrote: >> I've now updated MokoMakefile to use these official OpenMoko sites. > > > Great! Do we just 'make update-makefile update all' to get rolling with > the new schema? > > ; > -- > Jay Vaughan > I would do a nearly clean build : make update-makefile make clobber-openembedded # using the new Makefile now rm OE.mtn stamps/OE.mtn make setup update all It will take a lot of time, so I would do this before I go to sleep. - John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko OE repository not quite ready for MokoMakefile production usage
I've now updated MokoMakefile to use these official OpenMoko sites. Great! Do we just 'make update-makefile update all' to get rolling with the new schema? ; -- Jay Vaughan ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko OE repository not quite ready for MokoMakefile production usage
John Lee wrote: > The oe snapshots site: > > http://downloads.openmoko.org/OE/snapshots/ > > The monotone repository: > > monotone.openmoko.org > > I have done various tests on them such as run different versions of > monotone againest the database files, build from scratch with these > settings, etc. There might still be subtle problems in different > usage scenarios, so please give feedback and I'll fix them asap. I've now updated MokoMakefile to use these official OpenMoko sites. Now all default MokoMakefile builds will be building the "known-good" tested revision that the OpenMoko build manager releases each week. Just use "make update" as usual to get the latest known-good version. For those people who wish to continue using the "bleeding-edge" versions from the OpenEmbedded monotone server directly, you can do: make OM_MONOTONE_SITE=monotone.openembedded.org update to get the very latest changes contributed by the community which have not been tested by OpenMoko yet. You must do this every time you update, or else it will automatically revert to the official server. -- Rod ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: OpenMoko OE repository not quite ready for MokoMakefile production usage
Hi Rod, The oe snapshots site: http://downloads.openmoko.org/OE/snapshots/ The monotone repository: monotone.openmoko.org I have done various tests on them such as run different versions of monotone againest the database files, build from scratch with these settings, etc. There might still be subtle problems in different usage scenarios, so please give feedback and I'll fix them asap. - John On Thu, Nov 29, 2007 at 09:14:15PM +1030, Rod Whitby wrote: > > There is one issue which means that MokoMakefile cannot change over to > using the new area yet. I have discussed this with John, but am > reporting here so people don't continually ask me why MokoMakefile > hasn't changed yet. > > The issue is that new OpenMoko mtn database snapshot area at > http://downloads.openmoko.org/OE/snapshots/ > only contains a single unversioned mtn database. > > MokoMakefile currently identifies the user's monotone version, and > downloads the correctly versioned mtn database from > http://www.openembedded.org/snapshots/ > (look there to see the naming convention and list of 6 different mtn > versions that are supported). Only if it cannot match the exact version > does it fall-back to using the unversioned snapshot. > > Unless OpenMoko is going to require a specific Linux distribution and > monotone version for building the OpenMoko distribution, I would prefer > to wait until OpenMoko replicates this facility for their developers > before I change the MokoMakefile, otherwise we will have *many* new > users having problems with monotone database migrations, and negating > the ease of setup that MokoMakefile currently provides. > > I have given John details on how to do this - I'm sure Graeme or Mickey > can get the older mtn binaries from Koen to implement it. > > I've asked John to let me know as soon as there are correctly labelled > versions in http://downloads.openmoko.org/OE/snapshots/, and I will > immediately update MokoMakefile to use the new area when that happens. > > -- Rod Whitby > -- MokoMakefile author > ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
OpenMoko OE repository not quite ready for MokoMakefile production usage
John Lee wrote: > The official OpenEmbedded repository to build the OpenMoko > distribution can be found at monotone.openmoko.org. If you're using > MokoMakefile, please refer to > > http://wiki.openmoko.org/wiki/MonotoneServer#Using_MokoMakefile > > for instructions about how to switch. There is one issue which means that MokoMakefile cannot change over to using the new area yet. I have discussed this with John, but am reporting here so people don't continually ask me why MokoMakefile hasn't changed yet. The issue is that new OpenMoko mtn database snapshot area at http://downloads.openmoko.org/OE/snapshots/ only contains a single unversioned mtn database. MokoMakefile currently identifies the user's monotone version, and downloads the correctly versioned mtn database from http://www.openembedded.org/snapshots/ (look there to see the naming convention and list of 6 different mtn versions that are supported). Only if it cannot match the exact version does it fall-back to using the unversioned snapshot. Unless OpenMoko is going to require a specific Linux distribution and monotone version for building the OpenMoko distribution, I would prefer to wait until OpenMoko replicates this facility for their developers before I change the MokoMakefile, otherwise we will have *many* new users having problems with monotone database migrations, and negating the ease of setup that MokoMakefile currently provides. I have given John details on how to do this - I'm sure Graeme or Mickey can get the older mtn binaries from Koen to implement it. I've asked John to let me know as soon as there are correctly labelled versions in http://downloads.openmoko.org/OE/snapshots/, and I will immediately update MokoMakefile to use the new area when that happens. -- Rod Whitby -- MokoMakefile author ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MokoMakefile now builds OM-2007.2 (Was: Balancing simplicity with complexity)
Sean Moss-Pultz wrote: > The introduction of OM-2007.2 goes hand in hand with merging the > OpenMoko OpenEmbedded overlay into the upstream repository > org.openembedded.dev. We are now based directly on the upstream metadata > found in OpenEmbedded and synchronized with the most recent developments. The MokoMakefile (<http://wiki.openmoko.org/wiki/MokoMakefile>) has been updated to build OM-2007.2 images. If you're starting from scratch, just follow the instructions on that wiki page. Pay careful attention to the host software package requirements for the OpenEmbedded build system. If you're migrating from a previous version of the MokoMakefile, then just type: make update-makefile ; make setup update openmoko-devel-image and after a number of hours and lots of building you should have new OM-2007.2 images built. By changing the OPENMOKO_GENERATION variable at the top of the Makefile you can alternately (but not concurrently) build both OM-2007.1 and OM-2007.2 images. The ability to build OM-2007.1 images will be removed after a couple of weeks (you will still be able to get it from the MokoMakefile svn repository if you really need it). There was a 24 hour period up to earlier today where there was a bug in the MokoMakefile. If you experience the following problem: Patch bitbake-1.6.6-om3.patch does not apply (enforce with -f) then type "make clobber-patches" and rebuild to fix it. -- Rod ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MokoMakefile failure while building openmoko-rssreader
I had the same issue and for me it helped just to update mokomakefile. Check this and try again. 2007/8/4, Giles Jones <[EMAIL PROTECTED]>: > > > On 4 Aug 2007, at 11:20, Krzysztof Kajkowski wrote: > > > OK, I admit - it's bad habit to anwer to yourself ;) but I found how > > to make way around this problem: > > > > edit: oe/packages/task/task-openmoko.bb and comment out > > openmoko-rssreader in it. Now you can compile OM (without rssreader) > > and compilation does not brake. > > > > I also found that others hve the same problem: > > > > http://zecke.blogspot.com/2007/07/webkitgtk.html > > > > So maybe it helps someone. > > > > Although I responded myself, the question in my first post remains - > > how to fix building process of OM because apparently it is broken. > > > > regards > > > > cayco > > There's a bug logged for this issue already. > > http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=648 > > > > ___ > OpenMoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MokoMakefile failure while building openmoko-rssreader
On 4 Aug 2007, at 11:20, Krzysztof Kajkowski wrote: OK, I admit - it's bad habit to anwer to yourself ;) but I found how to make way around this problem: edit: oe/packages/task/task-openmoko.bb and comment out openmoko-rssreader in it. Now you can compile OM (without rssreader) and compilation does not brake. I also found that others hve the same problem: http://zecke.blogspot.com/2007/07/webkitgtk.html So maybe it helps someone. Although I responded myself, the question in my first post remains - how to fix building process of OM because apparently it is broken. regards cayco There's a bug logged for this issue already. http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=648 ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MokoMakefile under Ubuntu Feisty
Deepank Gupta wrote: Running Mokomakefile is slow, because bitbake is a bit slow right now and it build lots and lots of packages. Gcc internal error must have come when you were installing qemu. Try sudo apt-get install gcc-3.4 More instructions on installing openMoko development environment for Ubuntu Feisty at : http://wiki.openmoko.org/wiki/User_talk:Michaelshiloh ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Deepank... Thanks a bunch for that posting! I'm running Ubuntu 7.04, and your post will be a great help. I'll try it out tonight after work. Cheers...Cassj ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MokoMakefile under Ubuntu Feisty
Running Mokomakefile is slow, because bitbake is a bit slow right now and it build lots and lots of packages. Gcc internal error must have come when you were installing qemu. Try sudo apt-get install gcc-3.4 More instructions on installing openMoko development environment for Ubuntu Feisty at : http://wiki.openmoko.org/wiki/User_talk:Michaelshiloh ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MokoMakefile under Ubuntu Feisty
Hello, Here a PC with 512 MB of RAM faced extreme slowliness when running MokoMakefile and finally failed with a gcc internal error :/ MokoMakefile requires more than 512 MB of RAM + Swap space (about 1GB ???). And the swap partition under Feisty was not mounted. Bug #105490 describes this issue and gives a workaround (23 Jul 07): https://bugs.launchpad.net/ubuntu/+bug/105490 Gilles -- Oralux.org http://association.oralux.org ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
Hello again, On 7/19/07, Krzysztof Kajkowski <[EMAIL PROTECTED]> wrote: Yes, later I found this and even I found MacOS X specific HOWTO (not related with problem) which he mentioned. I look over whole SVN there and did not find anything interesting. Hmm, I did a search on Google for "libbb features.h" and found this: http://xanana.ucsc.edu/fink_10.4/dists/unstable/main/finkinfo/utils/ipkg.info I implemented the patches from there (one after another, to see which was needed) using #ifndef __FreeBSD__ instead of __APPLE__ adn that seems to have helped. Perhaps that will help for you as well? The 'gmake openmoko-devel-image' now stops at another point, but that's another story. -- Regards, Torfinn ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
2007/7/19, Torfinn Ingolfsen <[EMAIL PROTECTED]>: > http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-July/002520.html Aha. Well, the viewcvs he's talking about is here: http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/ But the only thing I found (after a brief search) related to libbb is this: http://handhelds.org/cgi-bin/cvsweb.cgi/ipkg.unused/libbb/ and libbb.h in that directory is still at its first version there. It would be much easier if he just told you which patch he means. :-/ Yes, later I found this and even I found MacOS X specific HOWTO (not related with problem) which he mentioned. I look over whole SVN there and did not find anything interesting. I tried to search OE site using his nickname, his mail, his name etc but I found nothing useful. I wrote him personnaly but he did not respond. I'm starting to lose hope now. I though of how to get qemu compiled under MacOS X - I try to patch it using Q[:kju] patches but I cannot get to point of compiling qemu. Can anybody help us? cayco ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
On 7/19/07, Krzysztof Kajkowski <[EMAIL PROTECTED]> wrote: > > I asked for help on OE mailing lists. Someone responded that he has a > > patch for this but I could not find it. > > Interesting. > Do you have a reference to that thread in mailinglist archives? > http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-July/002520.html Aha. Well, the viewcvs he's talking about is here: http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/ But the only thing I found (after a brief search) related to libbb is this: http://handhelds.org/cgi-bin/cvsweb.cgi/ipkg.unused/libbb/ and libbb.h in that directory is still at its first version there. It would be much easier if he just told you which patch he means. :-/ -- Regards, Torfinn ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
On Thursday 19 July 2007 12:11, Rod Whitby wrote: > Al Johnson wrote: > > On Thursday 19 July 2007 11:18, Mario Wewer wrote: > >> So - does anyone of you already has a running VMWARE image with all > >> openmoko-relevant applications running?! > > > > If anyone had a suggestion for a distro where mokomakefile 'just works' > > I'll try to make a qemu or xen image over the weekend. > > I usually make sure MokoMakefile builds on Debian Etch and CentOS 4. > > A long term support version of Ubuntu would also be suitable I expect > (i.e. *don't* choose an _unstable_ version of Debian or Ubuntu or Gentoo). I should have CentOS and Ubuntu available. One motivation for this is that I can't get the Neo qemu to build on either of my (mostly) stable Gentoo boxes, one x86 and one amd64. I suppose making a qemu-neo ebuild is an alternative. The build of the neo binaries seems to work fine, but without the qemu I can't test it. > In previous discussion with some members of the OpenMoko core team about > this issue, there was a clear direction from them that OpenMoko would > not be officially releasing or supporting a VMware image because you > needed proprietary software to run it. So a qemu or xen image would be > in keeping with that spirit. Agreed. Especially as I have both Xen and qemu, but not VMware :-) > -- Rod (who run's VMware, but also agrees with the core team :-)) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
Al Johnson wrote: > On Thursday 19 July 2007 11:18, Mario Wewer wrote: >> So - does anyone of you already has a running VMWARE image with all >> openmoko-relevant applications running?! > > If anyone had a suggestion for a distro where mokomakefile 'just works' I'll > try to make a qemu or xen image over the weekend. I usually make sure MokoMakefile builds on Debian Etch and CentOS 4. A long term support version of Ubuntu would also be suitable I expect (i.e. *don't* choose an _unstable_ version of Debian or Ubuntu or Gentoo). In previous discussion with some members of the OpenMoko core team about this issue, there was a clear direction from them that OpenMoko would not be officially releasing or supporting a VMware image because you needed proprietary software to run it. So a qemu or xen image would be in keeping with that spirit. -- Rod (who run's VMware, but also agrees with the core team :-)) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build environment with MokoMakefile on FreeBSD / amd64?
2007/7/19, Al Johnson <[EMAIL PROTECTED]>: On Thursday 19 July 2007 11:18, Mario Wewer wrote: > So - does anyone of you already has a running VMWARE image with all > openmoko-relevant applications running?! If anyone had a suggestion for a distro where mokomakefile 'just works' I'll try to make a qemu or xen image over the weekend. Ubuntu works well. cayco ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
