From: Alexey Smishlayev <alexey@xtech2.lv>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling fw_printenv tool
Date: Tue, 14 Jan 2014 13:25:23 +0200 [thread overview]
Message-ID: <52D51EA3.4060702@xtech2.lv> (raw)
In-Reply-To: <m24n56q1ew.fsf@lamuella.denx.de>
Hello Detlev,
On 2014.01.14. 12:54, Detlev Zundel wrote:
> Hi Alexey,
>
>> Dear Detlev,
>>
>> I ran
>> $ make HOSTCC=arm-none-linux-gnueabi-gcc env
>> and got the tools/env/fw_printenv executable. But the Make command
>> returned error:
>> strip: Unable to recognise the format of the input file `fw_printenv'
>> make[1]: *** [fw_printenv] Error 1
>>
>> I guess, HOSTSTRIP variable also has to be set.
>>
>> However, I uploaded the unstripped executable to my embedded device,
>> and ran:
>> $ chmod a+x fw_printenv
>> $ ./fw_printenv
>> -sh: ./fw_printenv: not found
>>
>> I tried also manually stripping the executable.
>> What could be this error related to?
> Oops, I really missed that mail, sorry.
>
> This error message means that your cross-compiled binary does not run on
> the embedded device (maybe the device uses different libraries than your
> cross toolchain links agains). To troubleshoot that, start with a
> regular "hello-world.c" and continue to fw_printenv only if you have
> this working.
>
> Cheers
> Detlev
>
I've googled it and sorted it out. The problem was that executable was
dynamically linked and the *.so was not found on the embedded system. I
compiled it with -static and it runs.
Best regards,
Alexey
next prev parent reply other threads:[~2014-01-14 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 10:53 [U-Boot] Compiling fw_printenv tool Alexey Smishlayev
2013-11-29 11:17 ` Detlev Zundel
2013-11-29 12:50 ` Alexey Smishlayev
2014-01-14 10:54 ` Detlev Zundel
2014-01-14 11:25 ` Alexey Smishlayev [this message]
2014-01-17 14:30 ` Detlev Zundel
2014-01-17 14:41 ` Alexey Smishlayev
2014-01-17 16:02 ` Detlev Zundel
2014-01-14 11:47 ` Masahiro Yamada
2014-01-15 14:50 ` Gerhard Sittig
2014-01-17 14:38 ` Detlev Zundel
2014-01-17 14:28 ` Detlev Zundel
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=52D51EA3.4060702@xtech2.lv \
--to=alexey@xtech2.lv \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.