OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: alexei on April 06, 2005, 11:52:55 pm
-
Hi, I'm trying to natively compile mutt on the Z (with different options and patches from the one in the feeds)
I've mounted zgcc-3.3.2.img in /opt/arm/3.3.2-vfp and exported:
export PATH=$PATH:/opt/arm/3.3.2-vfp/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/arm/3.3.2-vfp/lib
./configure -enable-pop -enable-immap -with-homespool=~/INBOX --includedir=/opt/arm/3.3.2-vfp/armv5tel-cacko-linux/include
It configures OK but make dies with:
...
mutt.h:46:24: posix1_lim.h: No such file or directory
although the file is at:
/opt/arm/3.3.2-vfp/armv5tel-cacko-linux/include/bits/posix1_lim.h
How to I get it to find this file?
Sorry if this is a silly question, I'm not very experienced at compiling.
-
Do you use RC9 native sdk?
This sdk should be mounted in /opt/native/arm/3.3.2-xscale-softvfp.
other than that you could try to add /opt/arm/3.3.2-vfp/armv5tel-cacko-linux/include/bits/ (with bits) in your include path
-
I'm still using RC8 ... I've successfully compiled a couple of small programs, so my paths seem set up OK.
If I include /opt/arm/3.3.2-vfp/armv5tel-cacko-linux/include/bits/ directly I get lots of errors saying things like "never include <bits/stdio.h> directly: use <stdio> instead" and the whole thing goes pear-shaped very quickly.
-
hmm, I'll try to cross-compile it (when I find some time) to see if I run into the same problems (or perhaps bruno van reports its finding )
I just had quick look at mutt.h maybe you can define _POSIX_PATH_MAX
manually replacing
#ifndef _POSIX_PATH_MAX
#include
#endif
by
#define _POSIX_PATH_MAX 256
and hope that this problem doesn't appears because something more important is missing
-
OK success!
the trick was to copy posix1_lim.h to the local directory. (and to kill every running app .... gcc was dying unexpectedly - running out of memory?)
I'll provide an ipk soon.