<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks Dave,<br>
<br>
Your the champ on this list!<br>
<br>
yep, the wpa_supplicant binary is of "Intel 80386" format. Not
surprising, but the real question is why? Ive rm -rf my buildroot and
tried everything from beginning more times than i want to remember.
I've even copied over my .config file from my desktop...it still
insists of using my host gcc.<br>
<br>
-W<br>
<br>
<br>
Dave Hylands wrote:
<blockquote
cite="midc32efac40706122241x1fce9bdds1ed5cf5bb0c1274b@..."
type="cite">
<pre wrap="">Hi Wael,
</pre>
<blockquote type="cite">
<pre wrap="">I can compile wpa_supplicant fine on my desktop but when i try the exact
same procedure on my ubuntu feisty laptop i get the following errors
---------------------------
/home/wael/verdex/gumstix-buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibcgnueabi-strip:
Unable to recognise the format of the input file
`/home/wael/verdex/gumstix-buildroot/build_arm_nofpu/root/bin/wpa_cli'
</pre>
</blockquote>
<pre wrap=""><!---->
This probably means that the file was compiled with gcc rather than
arm-linux-uclibceabi-gcc
You can test this by using the file command on your host. For an arm
executable, you should see something like this:
busybox: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically
linked (uses shared libs), stripped
For an x86 executable it would look like:
sertest: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux
2.6.4, not stripped
Note that object files and executables are both ELF files, and you can
use the file command to test them.
</pre>
</blockquote>
</body>
</html>
|