From: "Corey" <corey@bitworthy.net>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] cross compiling libperl
Date: Sun, 19 Nov 2006 20:13:19 -0700 [thread overview]
Message-ID: <200611192013.20330.corey@bitworthy.net> (raw)
Are there any patches for cross compiling libperl available?
I'm running into (so far, at least one) issue where configure goes and attempts
to test things by creating a simple c program ('try.c'), which fails to run because
it compiled it using (in my particular case) i686-pc-linux-uclibc-gcc.
Here's the output from the configure, as run through my crossdev:
"I've tried to compile and run the following simple program:
#include <stdio.h>
int main() { printf("Ok\n"); return(0); }
I used the command:
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
./try
and I got the following output:
/bin/sh: ./try: No such file or directory
The program compiled OK, but exited with status 127."
Here's the relevant portion from ./configure:
: coherency check
echo " "
echo "Checking your choice of C compiler and flags for coherency..." >&4
$cat > try.c <<'EOF'
#include <stdio.h>
int main() { printf("Ok\n"); return(0); }
EOF
set X $cc -o try $optimize $ccflags $ldflags try.c $libs
shift
$cat >try.msg <<'EOM'
I've tried to compile and run the following simple program:
EOM
$cat try.c >> try.msg
$cat >> try.msg <<EOM
I used the command:
$*
$run ./try
and I got the following output:
EOM
I'm wondering if this is a know issue and/or what's the best way of getting around it?
--
gentoo-embedded@gentoo.org mailing list
next reply other threads:[~2006-11-20 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 3:13 Corey [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-12 17:07 [gentoo-embedded] Cross compiling libperl Petric Frank
2007-11-12 16:50 ` Karl Hiramoto
2007-11-14 8:01 ` Christopher Friedt
2007-11-19 4:08 ` Mike Frysinger
2007-11-19 4:08 ` Mike Frysinger
2007-11-19 17:59 ` Petric Frank
2007-11-20 5:26 ` Mike Frysinger
2007-11-20 18:34 ` Petric Frank
2007-11-21 17:40 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611192013.20330.corey@bitworthy.net \
--to=corey@bitworthy.net \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox