Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 8 Sep 2015 17:24:17 +0200	[thread overview]
Message-ID: <55EEFDA1.6070104@mind.be> (raw)
In-Reply-To: <CAF5aO=+gjgRuocbAvLicJWPkEkiiuUMFtTG6mDV-roq0cz-_fQ@mail.gmail.com>



On 08-09-15 16:59, Alex Potapenko wrote:
[snip]
>     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)
> 
> 
> Yes, looking at nano config.log reveals this:
> 
>     configure:5147: checking for _FILE_OFFSET_BITS value needed for large files
>     ...
>     configure:5204: result: 64
> 
> 
> And /data partition that contains /opt is exactly 2 GB. Does this mean that it
> is a 32 bit file system, while the toolchain uses 64 bit file system interface?

 The -EOVERFLOW suggests the reverse: it's a large filesystem and we're making a
32-bit syscall.

 However, since we're building with LARGEFILE (which is forced in current
buildroot), all syscalls should be largefile syscalls so this issue should not
occur...

 However, in your 2015.08 config, I see you're using a custom uClibc config.
You're not turning off any largefile options there, are you?


 Regards,
 Arnout


> Will it work if I create an ext2 partition larger than 2 GB on my memory card
> and mount it as /opt?
> 
>      It would help if you would have your phone's kernel config. Do you have it?
> 
> 
> Unfortunately, no, I don't have the exact config used to build the kernel. I
> know it was compiled from this source:
> https://github.com/CyanogenMod/android_kernel_samsung_smdk4412 
> 
> I ran `make exynos4_defconfig`, then manually selected arch (exynos4) and mach
> (not sure I selected right, but that probably doesn't matter here). See the
> result attached.
> 
> Thanks a lot!
> 
> -- 
> Best regards,
> Alex Potapenko

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . 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

  reply	other threads:[~2015-09-08 15:24 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
2015-09-08 14:59               ` Alex Potapenko
2015-09-08 15:24                 ` Arnout Vandecappelle [this message]
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=55EEFDA1.6070104@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