Shop OBEX P1 Docs P2 Docs Learn Events
build problems with debian arm toolchain — Parallax Forums

build problems with debian arm toolchain

rwgast_logicdesignrwgast_logicdesign Posts: 1,464
edited 2012-06-19 13:24 in Propeller 1
ok so i got mercruial installed on my phone then dl prop gcc. using the jbuild and rebuild scripts keeps failing ising the arm chain in debian. the problem is theres to many jobs to figure out whats causing the compiler to fail. in my experince when trying to port code compiling with 1 job is the way to go.

so is there an easy way to set the jobs to one with the rebuild script, maybe export a var or something?

I could just do this on the PC but I don't wanna lol

Comments

  • ersmithersmith Posts: 6,097
    edited 2012-06-19 05:21
    rwgast_logicdesign wrote: »
    ok so i got mercruial installed on my phone then dl prop gcc. using the jbuild and rebuild scripts keeps failing ising the arm chain in debian. the problem is theres to many jobs to figure out whats causing the compiler to fail. in my experince when trying to port code compiling with 1 job is the way to go.

    so is there an easy way to set the jobs to one with the rebuild script, maybe export a var or something?

    You can give the number of jobs as the first parameter to jbuild.sh (e.g. "./jbuild.sh 1").
  • pedwardpedward Posts: 1,642
    edited 2012-06-19 11:44
    I think he means that he wants to do an incremental build. The parameter to jbuild is the same as the -j parameter to Make, the number of simultaneous compilations to execute.

    I agree that the build is not done in the conventional manner. It would make sense to have a top level Makefile that does all the building, then Make can descend and handle dependencies.

    More importantly, you could specify which part you wanted built so you can debug and build over and over.

    The current build script assumes a clean before make, which wastes a lot of time in a situation where you want to figure out why the build is broken.
  • rwgast_logicdesignrwgast_logicdesign Posts: 1,464
    edited 2012-06-19 13:24
    Im going to cross compile with the NDK on my pc, this worked smoothly with homespun for someone else im hoping it will work for propcgg. Im having the same issue as you with textinfo, and I really dont want go through the process of doing a port on a 3 inch screen. I was hoping itd be a smooth build with no porting effort. Basically i have finally built a bluetooth programmer that replaces the prop plug using those 5 dollar linux bt ssp boards, even has a reset and all. I have to give a huge thanks to jazzed as he found the data sheet for these csr modules!!

    Anyways wireless android programming via BT is here the only thing left is prop loader. Im not sure if my hardware works with spintool becuase i use rts for reset not dtr but i know its compatible with proploader! So now we have spin and soon gcc which will both make binarys compatible with proploader!

    The race is on! who can port gcc/proploader faster you or I!!!! I have a feeling since i have about an hour left to play today i might loose. I dont care to much acually lol I just wanna get the software ported quick as possible.

    Anyways once the software is ported and hopefully running from android command line without the need for a debian chroot Im going to do a write up iof how to install all the software and build the hardware!!

    This is my dream come true A bluetooth KB, DroidEdit(BEST CODE EDITOR APP ON THE MARKET!!!!, thing can even tunnel ssh commands to compile your files on a pc over the network), SPIN/GCC. and a 5 dollar module connected to 3 passives and yout have a great mobile prop environment!!!
Sign In or Register to comment.