1 |
Are there any patches for cross compiling libperl available? |
2 |
|
3 |
I'm running into (so far, at least one) issue where configure goes and attempts |
4 |
to test things by creating a simple c program ('try.c'), which fails to run because |
5 |
it compiled it using (in my particular case) i686-pc-linux-uclibc-gcc. |
6 |
|
7 |
|
8 |
Here's the output from the configure, as run through my crossdev: |
9 |
|
10 |
"I've tried to compile and run the following simple program: |
11 |
|
12 |
#include <stdio.h> |
13 |
int main() { printf("Ok\n"); return(0); } |
14 |
|
15 |
I used the command: |
16 |
|
17 |
i686-pc-linux-uclibc-gcc -o try -O2 -DOVR_DBL_DIG=14 -I/usr/local/include -L/usr/local/lib try.c -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc |
18 |
./try |
19 |
|
20 |
and I got the following output: |
21 |
|
22 |
/bin/sh: ./try: No such file or directory |
23 |
The program compiled OK, but exited with status 127." |
24 |
|
25 |
|
26 |
Here's the relevant portion from ./configure: |
27 |
|
28 |
: coherency check |
29 |
echo " " |
30 |
echo "Checking your choice of C compiler and flags for coherency..." >&4 |
31 |
$cat > try.c <<'EOF' |
32 |
#include <stdio.h> |
33 |
int main() { printf("Ok\n"); return(0); } |
34 |
EOF |
35 |
set X $cc -o try $optimize $ccflags $ldflags try.c $libs |
36 |
shift |
37 |
$cat >try.msg <<'EOM' |
38 |
I've tried to compile and run the following simple program: |
39 |
|
40 |
EOM |
41 |
$cat try.c >> try.msg |
42 |
|
43 |
$cat >> try.msg <<EOM |
44 |
|
45 |
I used the command: |
46 |
|
47 |
$* |
48 |
$run ./try |
49 |
|
50 |
and I got the following output: |
51 |
|
52 |
EOM |
53 |
|
54 |
|
55 |
|
56 |
I'm wondering if this is a know issue and/or what's the best way of getting around it? |
57 |
|
58 |
-- |
59 |
gentoo-embedded@g.o mailing list |