From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] EOVERFLOW fstat() error on cortex-A9 android when trying to load shared library
Date: Mon, 7 Sep 2015 17:17:29 +0200 [thread overview]
Message-ID: <55EDAA89.20809@mind.be> (raw)
In-Reply-To: <CAF5aO=LiY_3XBn+HgA8-nwJk51GQkgGQqbnpmdQoyS64zxDTWA@mail.gmail.com>
On 07-09-15 16:53, Alex Potapenko wrote:
> Thank you for your response, Arnout!
> Unfortunately, that is not the reason here. I use Buildroot to build the
> toolchain only. And then use modified Optware build system to cross-compile the
> packages. armeabi feed is built with '
> -Wl,--dynamic-linker=/opt/lib/ld-uClibc.so.0' ld flag, so they know where the
> linker resides.
Weird, since strace shows that it is looking inside /system and lc-uClibc.so
would never do that...
Your kernel does have CONFIG_AEABI I hope?
Could you try to build without the --dynamic-linker and install in / ? Just to
exclude that potential issue.
Regards,
Arnout
PS Please don't top-post.
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-07 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 13:24 [Buildroot] EOVERFLOW fstat() error on cortex-A9 android when trying to load shared library Alex Potapenko
2015-09-07 14:33 ` Arnout Vandecappelle
[not found] ` <CAF5aO=LYm6GYVXv0gJW9fS3A8JXMAeZwnEokG0Htpac4SZuJVQ@mail.gmail.com>
2015-09-07 14:53 ` Alex Potapenko
2015-09-07 15:17 ` Arnout Vandecappelle [this message]
2015-09-07 17:49 ` Alex Potapenko
2015-09-07 20:40 ` Arnout Vandecappelle
2015-09-08 9:07 ` Waldemar Brodkorb
2015-09-08 14:59 ` Alex Potapenko
2015-09-08 15:24 ` Arnout Vandecappelle
2015-09-08 15:29 ` Alex Potapenko
2015-09-08 15:58 ` Alex Potapenko
2015-09-08 19:41 ` Waldemar Brodkorb
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=55EDAA89.20809@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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