From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] EOVERFLOW fstat() error on cortex-A9 android when trying to load shared library
Date: Tue, 8 Sep 2015 11:07:19 +0200 [thread overview]
Message-ID: <20150908090719.GA14056@waldemar-brodkorb.de> (raw)
In-Reply-To: <55EDF64F.7020707@mind.be>
Hi,
Arnout Vandecappelle wrote,
> And the kernel ABI is compatible of course.
>
> Hm, you're running 2.6.36 headers against a 3.0 kernel... Normally that
> shouldn't be an issue, but maybe there are some LARGEFILE related changes that
> are not entirely ABI-compatible - or perhaps it's a uClibc bug to not do this in
> an ABI-compatible way. I see in fs/compat.c that cp_compat_stat() can return
> -EOVERFLOW if the inode is 64 bit while the syscall is 32 bit. But since the
> toolchain is LFS I don't see how this could happen...
I would like to know if your nano configure says something like
this:
checking for _FILE_OFFSET_BITS value needed for large files... 64
Is your filesystem on the Android device bigger than 2 GB?
(where /opt and nano + libraries lives in)
best regards
Waldemar
next prev parent reply other threads:[~2015-09-08 9:07 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
2015-09-07 17:49 ` Alex Potapenko
2015-09-07 20:40 ` Arnout Vandecappelle
2015-09-08 9:07 ` Waldemar Brodkorb [this message]
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=20150908090719.GA14056@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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