AndroidStudio compiling native code shows "fcntl(): Bad file descriptor"

user_1943799 0
Viewed 7103

I have a legacy app that a fellow developer was seeing fcntl(): Bad file descriptor when building our native cpp code within AndroidStudio.

Our build environment supports building from the command line (for scripting and doing daily automatic builds) using locally installed NDK as well as through AndroidStudio. We set local.properties to point to the locally installed NDK.

I could not determine the cause of the fcntl error and was not seeing it myself when running NDK r17. I then updated to NDK r21d (June 2020) and immediately see the same thing within AndroidStudio.

fcntl(): Bad file descriptor
[arm64-v8a] Compile++      : vhc_jnilib <= Png.cc
fcntl(): Bad file descriptor
[arm64-v8a] Compile++      : vhc_jnilib <= Jpeg.cc
fcntl(): Bad file descriptor
[arm64-v8a] Compile++      : vhc_jnilib <= MyContainer.cc
fcntl(): Bad file descriptor
[arm64-v8a] Compile++      : vhc_jnilib <= aIdentityInfo.cc
fcntl(): Bad file descriptor
[arm64-v8a] Compile++      : vhc_jnilib <= UpdateImage.cc
fcntl(): Bad file descriptor

Android Studio 4.0, MacOS Catalina 10.15.4, Gradle 6

Questions:

  • Any idea how I can get more information on what tool is generating this warning?
  • What does this imply and can it be silenced or fixed?
android-studio android-ndk android
3 Answers

The project path cannot have spaces.

I have encountered the same problem, when I removed the spaces in the project path, the problem was solved.

user_149429570

I was having the same issue. I'm not sure what was the actual cause of it, but I got it fixed by deleting .gradle, .cxx & build directories and then rebuilding the project.

user_144756480

I have had this warning for some time, compiling the tess-two library. I have just upgraded my Android NDK version to the latest - 23.1.7779620 - and the warning has disappeared. I would therefore recommend that anyone with this problem should upgrade their NDK.

user_74679860
Related