Re: how to port a scheme interpreter to om?
2009/10/28 Shawn cit...@gmail.com: Ah, the happy conjunction of my main free software interests... (I'm one of Guile's maintainers.) wowo~it's pleasure to meet you here dude~ Likewise! checking for lt_dlinit in -lltdl... no configure: error: libltdl not found. See README. OK, this just means that you're missing a prerequisite: development files (headers and libraries) for the libltdl library. On Debian these are in the libltdl-dev package; on other distros I'd look for libltdl-dev, or libtool-dev, or something like that. To save time, you may like to check the other prerequisite too, i.e. GMP, before trying to build again. You can find the details in the README file. Hope that helps! Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
thanks, Neil.I will take it try after the compiling of openWRT is finished. OK, this just means that you're missing a prerequisite: development files (headers and libraries) for the libltdl library. On Debian these are in the libltdl-dev package; on other distros I'd look for libltdl-dev, or libtool-dev, or something like that. To save time, you may like to check the other prerequisite too, i.e. GMP, before trying to build again. You can find the details in the README file. Hope that helps! Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- GNU powered it... GPL protect it... God blessing it... regards HFG--Shawn the R0ck ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
On Wed, Oct 28, 2009 at 8:57 AM, Shawn cit...@gmail.com wrote: hi guys, does anybody has try to port the scheme interpreter(guile,etc) to openMOKO? I have used Chicken on OM. You can even compile scheme to machine code right on the phone if you have gcc etc. installed. And I wrote an OE recipe for it too (which might mean there are packages being built... I haven't checked lately). http://chicken.wiki.br/cross-compilation-on-open-moko I think Chicken is way faster than Guile, and has a lot of libraries/extensions (called eggs) available. http://chicken.wiki.br/chicken-projects/egg-index-4.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
On Wed, 2009-10-28 at 23:57 +0800, Shawn wrote: hi guys, does anybody has try to port the scheme interpreter(guile,etc) to openMOKO? for what distribution? If it's for SHR try openembedded...there is a guile recipe,but verify that it's the same version than the one in org.openembedded.dev else it will fail with a libtool problem because it would require an old libtool. Denis. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
-[ Wed, Oct 28, 2009 at 11:57:13PM +0800, Shawn ] hi guys, does anybody has try to port the scheme interpreter(guile,etc) to openMOKO? Let's try : ri...@hackable1:~/leech$ sudo aptitude install guile-1.8 guile guile (version) 1.8.5 What distribution do you use, that comes without a prepackaged scheme ? :-p ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
for what distribution? I got om for a few days.Im downloading the openWRT distro right now. If it's for SHR try openembedded...there is a guile recipe,but verify that it's the same version than the one in org.openembedded.dev else it will fail with a libtool problem because it would require an old libtool. I have used the cross compiler arm-linux-gcc to compile guile but failed in libtool problem. I tried compile 2 versions of guile(1.4 and 1.8.7) but got same error about libtool.It's any way to take it out? Denis. thanks for your answer,Denis. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- GNU powered it... GPL protect it... God blessing it... regards HFG--Shawn the R0ck ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
Let's try : ri...@hackable1:~/leech$ sudo aptitude install guile-1.8 guile guile (version) 1.8.5 What distribution do you use, that comes without a prepackaged scheme ? my laptop distro is Fedora 9.om,i will try to put a openWRT into it. :-p ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- GNU powered it... GPL protect it... God blessing it... regards HFG--Shawn the R0ck ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
2009/10/28 Shawn cit...@gmail.com: I have used the cross compiler arm-linux-gcc to compile guile but failed in Ah, the happy conjunction of my main free software interests... (I'm one of Guile's maintainers.) libtool problem. I tried compile 2 versions of guile(1.4 and 1.8.7) but got same error about libtool.It's any way to take it out? If you want to send me details, I'm happy to try to help. But cross-compiling environments are tricky so it could take a few iterations. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: how to port a scheme interpreter to om?
Ah, the happy conjunction of my main free software interests... (I'm one of Guile's maintainers.) wowo~it's pleasure to meet you here dude~ If you want to send me details, I'm happy to try to help. But cross-compiling environments are tricky so it could take a few iterations. the 1.4 version of guile has been succeed compile.but got this below on board: [...@friendlyarm /shawn]# guile /bin/guile: /bin/guile: 1: Syntax error: ( unexpected and 1.8.7 failed(it's a little bit long) to compile: [st...@localhost guile-1.8.7]$ ./configure --prefix=/citypw/shawn-dev/port-guile-to-arm/guile-build --target=arm-linux-gcc --host=arm-linux configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-linux-strip... arm-linux-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... arm-unknown-linux-gnu configure: autobuild project... guile configure: autobuild revision... 1.8.7 configure: autobuild hostname... localhost.localdomain configure: autobuild timestamp... 20091028T163227Z checking for a BSD-compatible install... /usr/bin/install -c checking for arm-linux-gcc... arm-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-linux-gcc accepts -g... yes checking for arm-linux-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-linux-gcc... gcc3 checking how to run the C preprocessor... arm-linux-gcc -E checking for gawk... (cached) gawk checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for arm-linux-gcc option to accept ISO C89... (cached) none needed checking whether arm-linux-gcc and cc understand -c and -o together... yes checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by arm-linux-gcc... /usr/local/arm/3.4.1/arm-linux/bin/ld checking if the linker (/usr/local/arm/3.4.1/arm-linux/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/local/arm/3.4.1/bin/arm-linux-nm -B checking the name lister (/usr/local/arm/3.4.1/bin/arm-linux-nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1966080 checking whether the shell understands some XSI constructs... yes checking whether the shell understands +=... yes checking for /usr/local/arm/3.4.1/arm-linux/bin/ld option to reload object files... -r checking for arm-linux-objdump... objdump checking how to recognize dependent libraries... pass_all checking for arm-linux-ar... arm-linux-ar checking for arm-linux-strip... (cached) arm-linux-strip checking for arm-linux-ranlib... arm-linux-ranlib checking command to parse /usr/local/arm/3.4.1/bin/arm-linux-nm -B output from arm-linux-gcc object... ok checking for dlfcn.h... yes checking for objdir... .libs checking if arm-linux-gcc supports -fno-rtti -fno-exceptions... no checking for arm-linux-gcc option to produce PIC... -fPIC -DPIC checking if arm-linux-gcc PIC flag -fPIC -DPIC works... yes checking if arm-linux-gcc static flag -static works... yes checking if arm-linux-gcc supports -c -o file.o... yes checking if arm-linux-gcc supports -c -o file.o... (cached) yes checking whether the arm-linux-gcc linker (/usr/local/arm/3.4.1/arm-linux/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... cross checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries...
Re: how to port a scheme interpreter to om?
Hi.. 2009/10/28 Shawn cit...@gmail.com: hi guys, does anybody has try to port the scheme interpreter(guile,etc) to openMOKO? [snip] I just built Guile 1.8.5 from shr-unstable. If you like I can put the packages up somewhere. John. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
