newLISP Fan Club

Forum => newLISP and the O.S. => Topic started by: bludra84 on August 27, 2009, 08:22:44 AM

Title: Compiling on Debian Armel
Post by: bludra84 on August 27, 2009, 08:22:44 AM
This works perfect after running a ./configure-alt and then removing the "-m32" option from the compiler and linker flags. Dunno how useful that is to anyone. I'm running newlisp on a Linksys NSLU2.
Title:
Post by: TedWalther on August 27, 2009, 06:10:41 PM
Which version of newlisp did you use?  In 10.1.4, the configure-alt shouldn't put the m32 flag unless the compiler supports it.



Ted
Title:
Post by: bludra84 on August 27, 2009, 06:20:32 PM
I'm using 10.1.1



Is the development version stable enough for normal use?
Title:
Post by: Lutz on August 27, 2009, 07:14:28 PM
Yes, most development versions are and 10.1.4 is too.
Title:
Post by: newdep on August 29, 2009, 12:25:55 AM
Aaa nice work ;-) Actualy we should port newlisp to everything that is

able to compile C and has a prompt...

The Debian ARMel packages are the same that run on the Nokia 810...

It depends on your Linux environment if you can use the configure scripts,

but newlisp does run fine on the ARMel.. ;-)
Title:
Post by: TedWalther on August 29, 2009, 01:05:44 AM
Quote from: "newdep"Aaa nice work ;-) Actualy we should port newlisp to everything that is

able to compile C and has a prompt...

The Debian ARMel packages are the same that run on the Nokia 810...

It depends on your Linux environment if you can use the configure scripts,

but newlisp does run fine on the ARMel.. ;-)


As of 10.1.4, the configure scripts auto-detect whether to use the -m32 flag, and also figure out the correct link options for libreadline.  If it failed on any platform before, give it a try now, it could really use the debugging.



It looks like "make" in OS/2 now supports lines starting with a tab like in Unix, so I could actually simplify the configure-alt file a little bit now.