Debian seem to be restricting this to i386 and amd64 but I can find no indication in the changelog as to why. I'm testing now to see if it builds on raspbian once I remove that restriction.MrRauch wrote:libavg
Can't find any evidence of these being in debian at allberkelium libbrowsernode
I don't see any deb files on hexxeh's mirror, just the source package (dsc/orig.tar.gz/debian.tar.gz)paulie wrote:I would like xastir (listed under hamradio on some versions of debian).
It doesn't have an installation candidate, but a search for xastir & raspbian gives a reference to a mirror in Germany ( hexxeh?) Where I can drill down to see the xastir .deb file
That's probably because libavg 1.7 does not support ARM (it won't build and work without modifications). The version in svn does support it, and work is being done on OpenGL ES support as well.plugwash wrote:MrRauch wrote:libavg
I found one case of some x86 specific assembler in what appeared to be debug code which I patched up (though i'm not sure of the correctness of the patch), are there any other issues I should be aware of before I upload a version of this?cnxsoft wrote: That's probably because libavg 1.7 does not support ARM (it won't build and work without modifications). The version in svn does support it, and work is being done on OpenGL ES support as well.
I successfully built and uploaded the sid version of spatialite, gdal is now building.plugwash wrote: I'm now looking to see if I have more luck with the version of spatialite from sid.
I also had to remove the sse part in the configure script.plugwash wrote:
Specifically I changed the debugBreak function to
__asm int 3;
//deliberately dereferencing a null pointer should break in most debuggers
*((char *)0) = 0;
gdal failed but it's a failure I know how to deal with, hopefully it should be built soon.plugwash wrote:plugwash wrote: I'm now looking to see if I have more luck with the version of spatialite from sid.
Yes, I tried it with a Cortex A8 board and it works. I don't have Raspberry Pi to try it out.plugwash wrote:debian had already done the sse fix since debian i386 is not sse.
Can you confirm that after making the sse fix and the debug code assembler fix that it worked for you?
So, I just opened up my new book and it says, that until chapter 12 (of 20) any Common LISP implemention will do, afterwards it gets a bit specific with CLISP (using the internal webserver and stuff).plugwash wrote:However there are other common lisp implementations in debian and at least ecl and gcl are available in raspbian. Are either of these usable for you?
Found similar errors mentioned on the web using gcc 4.7 trying to compile for Fedora 17 ARM. Out of curiosity: What is the "right" / supposed way to try to compile the package on the Pi to be able to provide a pkg? I may have time and motivation to give it a try but I lack experience in building stuff for repos, etc.plugwash wrote:I tried.and failed to get this one to build, I added armhf to the arhitecture lists and tried to build it. It failed with an internal compiler error. I then tried modifying the package to build with gcc-4.7. It got futher but it ultimately failed with.
./lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp /clisp-2.49/src/ -x '(and (load "/clisp-2.49/src/init.lisp") (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
make: *** [interpreted.mem] Illegal instruction