Compiling Natively on PDAXROM

[tovarish]

is it not possible to use the cross compiler to compile octave,
sadly for me octave doesnt even compile in linux

tovarish

[lardman]

Try turning the optimisation down (to -O1, or get rid completely) then re-run that command by hand, then re-run 'make install'.

In any case, when cross compiling using the pdaXrom toolchain (which used to work BTW with the pdaXrom 1.0.0 version) you couldn't run 'make install' (obviously) so the next step had to be done by hand.

Take a look in an existing octave package (assuming you can find one since my site went down), or at a desktop install and work out the structure.


Si

[pgas]

do you need gendoc ?

if not you can edit the Makefile so that it is not build.

you could try g++ -g -O2 -o gendoc dendoc.cc in a console or to cross compile it...

[omega]

thanks all... i just saw what happened.... lack of memory. My Z just crapped out, killing bash....

going to create a swap.  What do the optimisations do? Are they for speed or for file size?

[omega]

Damnit again! ;-)

Just mounted my microdrive as swap... and wiped it. grrr! now i have to compile, and make, and make install octave all over again.

[omega]

For reference install is in the coreutils-extra package in the unstable feed.  

Also,To make a swap file for anyone else needing to:

cd /mnt/cf
dd if=/dev/zero of=swp.img bs=1k count=90000
mkswap swp.img
swapon /mnt/cf/swp.img

gives me a 90meg swap... (without erasing my microdrive!)

[pgas]

using distcc might be another option if you have ram problem
(and a linux box)

[omega]

thanks pgas... i want to bull on and use just my Z... matter of principle to get it working at this stage. Also i don't want to go to the trouble of setting up my box on linux now... don't currently have the time, even with knoppix.

[lardman]

gendoc creates the documentation iirc; you probably don't need it.

That said, the octave Makefile setup is quite complex, so you're probably better off not trying to edit it out.


Si

[ScottYelich]

man

fear omega with a root prompt!

Scott

[omega]

8-)    It's still compiling from before..............!

I've also noticed that because of the microdrive that the battery barely charges through the usb cable... (according to the datasheet, my ibm 340meg cf microdrive takes 300ma when writing).

[omega]

My memory bar applet is currently across the taskbar onto the desktop, as in the red bar extends onto the desktop! Memory usage 151%..  Perhaps this should be listed as a bug?  LOL.

Still compiling...... had some problems earlier, had to restart...

[Zumi]

Somebody who compiled octave can make an ipkg from it?
I really don't want to struggle with it if somebody already made it.

Simple steps (I use these steps to create ipk-s from natively compiled apps):

• make a directory called (for example) ipkg_tmp
• install the program with the "$ make DESTDIR=ipkg_tmp install" command
• make a control file as it is described here
• strip the debug info from the binaries: "$ strip -g -S -d --strip-debug <binary name>"
• do a "$ mkipkg ipkg_tmp"
• upload the package in the unstable feed or request account from Laze to it.

Thank you in advance,
Zumi

[omega]

Zumi - AFAIK there isn't one available for RC5, hence i'm trying to compile. I was using one of lardmans one on cacko, no bothers but i think i got a undefined symbol on RC5.

Next, can lardman (or someone else who's around and knows) what is meant by this:

lardman: In any case, when cross compiling using the pdaXrom toolchain (which used to work BTW with the pdaXrom 1.0.0 version) you couldn't run 'make install' (obviously) so the next step had to be done by hand.

What is the next step that can be done by hand.  Last night when the compile finished (without any errors) there was no octave file and the octave symlink that was there before disappeared.  Octave-2.1.57

Next, i removed all the crap i could find from octave, and unpacked octave-2.1.59. I entered the command  ./configure ; make (the one with the flags in the install.octave file to remove all the debugging symbols (to try something different)) ; make install.  

I woke up this morning to find it still looping around the liboctave directory compiling, having never gotten to make install as there were no octave files placed on the system  (/usr/local...)

Can someone please advise? It's starting to get annoying.  I would suggest that the compile system is working okay as i compiled bison, flex, m4, lbreakout2, gputils, dosbox (omg! i just tested this after i wrote it...  dosbox works?!? no image needed?)...   As i said i'm using fort77, and perl for my fortran compiler...   The tests for it work grand, and the only thing is that octave doesn't find any fort77 libraries (they are not in the source file), but the fortran files appear to be created without any warnings).

[lardman]

What is the next step that can be done by hand

Manually copying the files to the appropriate locations on the Z (or to a directory structure which can be made into an ipk). However I note that Zumi has given a method which might allow 'make install' to work (and something like this is done with OE so it must be possible somehow).

Last night when the compile finished (without any errors) there was no octave file and the octave symlink that was there before disappeared

It should be in the bin directory (in the source directory), or perhaps it's in the /src directory. Try searching by modification date.

I woke up this morning to find it still looping around the liboctave directory compiling

It takes a long time to compile; hence my suggestion to use a cross-toolchain on a fast computer (and it takes a fair while there too!).

the only thing is that octave doesn't find any fort77 libraries (they are not in the source file), but the fortran files appear to be created without any warnings).

You can specify this location by passing a flag to configure (try ./configure --help).


Si