Author Topic: Compiling Natively on PDAXROM (Read 9796 times)

omega · « **on:** November 05, 2004, 08:53:29 am »

Hi, I started another thread months ago about compiling stuff under Cacko but here we go for pdaxrom (current version RC5)

I have compiling some things easily with the dev img... However other stuff seems to want an endless stream of depends that always want something else as well!

My first tip to us all that want to compile but just need some tips is from one of lardmans posts:

Quote

Octave is actually very easy to compile (no configure switches required other than --host=arm-linux; needs GCC 3.xx though), so assuming you have a pdaXrom toolchain setup go for it. The OZ version won't work for you as it uses a later version of libc.

I was not aware of the --host=arm-linux requirement.

I think that anyone else with tips / problems should post together making it easier for us all to become familiar with the problems that arise and their template solutions thus creating a wider availability of compiled programs for all. If a body of information develops here, i suggest that it then be turned into a FAQ. If such a faq exists, i apologise and could i humbly be pointed in the direction of such!

philo · « **Reply #1 on:** November 05, 2004, 09:49:21 am »

i'd like to have that info as well. i've never tried to compile anything for the zaurus before, and i'd really like to get evolution compiled to see if it's feasible to be running it on the z. so please give us any tips and pointers you have.

philo

lardman · « **Reply #2 on:** November 05, 2004, 09:57:12 am »

Actually the --host=arm-linux is only needed to cross-compile (perhaps I misread the thread where I originally replied).

Octave should compile natively without any configure switches.

Si

omega · « **Reply #3 on:** November 05, 2004, 10:00:41 am »

Ah. I'm having problems with no mkoctfile.... where do i get? I found it before somewhere.

Another tip to people: i used to use my sd card for compiling stuff (vfat)... today i'm using a samba share to my windows 2000 machine. Let's me keep a load of stuff there...

lardman · « **Reply #4 on:** November 05, 2004, 10:23:28 am »

Quote

Ah. I'm having problems with no mkoctfile.... where do i get? I found it before somewhere.

It comes in the tarball (or is created by the configure script or main Makefile).

Si

Edit: I just read that you're using a Windows machine to hold the files - I wonder if you're actually having a permissions problem, mkoctfile should be in the same directory as the configure script.

omega · « **Reply #5 on:** November 05, 2004, 11:43:31 am »

Lardman - sorry i was using an older version of octave. got 2.1.57.... it configures without a problem. says found f2c but not libf77.a?

when i type make then it craps out immediately.. What options can i pass to make??

got readline installed...

I went to make bison for it, that wants m4, when i go to compile m4 it wants autoconf, when i go to compile autoconf it wants m4.... yawn -please help.

pgas · « **Reply #6 on:** November 05, 2004, 12:08:19 pm »

bison is in the stable feed ... (m4 also)

omega · « **Reply #7 on:** November 05, 2004, 12:14:41 pm »

pgas - i thought that too...

but neither are listed under www.pdaxrom.org/feed
/unstable

or in the website list....

pgas · « **Reply #8 on:** November 05, 2004, 12:23:17 pm »

they are on the stable feed:
here
http://zaurus.spy.org/feeds/cacko/pdaXrom/1.1.0/rc5/feed/
and here
http://mirror1.pdaxrom.org/rc5/feed/

omega · « **Reply #9 on:** November 05, 2004, 12:28:52 pm »

thanks pgas

offroadgeek · « **Reply #10 on:** November 05, 2004, 01:13:16 pm »

I've also been trying to get the this to work.. so I downloaded the octave source (same version as omega used) so that I can compare apples to apples.

I thought I had gcc and gcc-headers installed (the package manager said they were), but I kept getting errors on no gcc. So I reinstalled them, and now I'm getting this error:

Code: [Select]

checking for C compilor default output file name... configure: error: C compiler cannot create executables
am I missing any other packages that need to be installed?

Laze · « **Reply #11 on:** November 05, 2004, 03:41:38 pm »

I applogize for the feed confusion - hopefully we soon can make the final 1.1.0 and get "rid" of the old version. And at the same time i will hopefully get my own server setup with much better developer stuff.

blakeyez · « **Reply #12 on:** November 05, 2004, 03:44:21 pm »

Quote

used to use my sd card for compiling stuff (vfat)... today i'm using a samba share to my windows 2000 machine.

Using a fat-based file system (including a samba share) is bound to cause you no end of headache when compiling. Many build scripts, etc, depend on the ability to use symbolic links, unix file permissions, etc, which will often break on FAT filesystems. Your best bet if you want to do a network-mounted drive is NFS...

You may not have had any problems yet, but I can almost guarantee that you will if you start trying to build more packages.

Dave

gretchen · « **Reply #13 on:** November 05, 2004, 06:45:03 pm »

Is it better to install gcc make etc from the feed or to download the sdk? What's the difference?

lardman · « **Reply #14 on:** November 07, 2004, 07:19:15 am »

Quote

Lardman - sorry i was using an older version of octave. got 2.1.57.... it configures without a problem. says found f2c but not libf77.a?

If you use f2c, you require the run-time libs which are provided (iirc) by libf77.a/so.

That said, the Octave compile used to fall over when I tried it with f2c; I'd use f77 if I were you.

Si

P.S. Why not use the cross toolchain (it's very simple)? This compile takes quite a while...

News:

Author Topic: Compiling Natively on PDAXROM (Read 9796 times)