Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8596335
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T00:39:07+00:00 2026-06-12T00:39:07+00:00

I have one shared library ,Which written in c build using arm-linux-androideabi-gcc compiler now

  • 0

I have one shared library ,Which written in c build using arm-linux-androideabi-gcc compiler now i want to test my shared library so i written one sample c which call that shared library(.so) and i want to make .exe , so when i compile i got the error like this
this is my make file

      TARG_OS       = WIN32
BUILDTYPE     = Debug
OS_BITS = 32    

SRC     := TestLSBioCore.c 



OBJS = $(SRC:.c=.o)

OUT         = ./Test.exe

OUTLIB      = 

INCLUDE     = -I../../../../../../../android-ndk-r8b/platforms/android-8/arch-arm/usr/include -I../../include

LIBS        = libLSBioCore.so



# C++ compiler flags (-g -O2 -Wall)
#CCFLAGS    = -O2 -w -ansi -D_POSIX_SOURCE

CCFLAGS     = -O2 -w -D_POSIX_SOURCE

DEFS        =  "-D __MSYS__" "-D__NBISLE__"

#LDFLAGS 
CFLAGS = -nostdlib 
LDFLAGS =-Wl,-rpath-link=../../../../../../../android-ndk-r8b/platforms/android-8/arch-arm/usr/lib/ -L../../../../../../../android-ndk-r8b/platforms/android-8/arch-arm/usr/lib/
LIB = -lc -lm

OBJECT = ../../../../../../../android-ndk-r8b/platforms/android-8/arch-arm/usr/lib/crtbegin_dynamic.o \
../../../../../../../android-ndk-r8b/platforms/android-8/arch-arm/usr/lib/crtend_android.o




#compiler
#CCC        = mingw32-gcc

CCC         = arm-linux-androideabi-gcc

#Archive
#AR = ar
#AR = /cygdrive/f/android-ndk-r8b/toolchains/arm-linux-androideabi-4.6/prebuilt/windows/bin/arm-linux-androideabi-ar

AR = arm-linux-androideabi-ar
.SUFFIXES: .c

default: dep $(OUT)

.c.o:
    $(CCC) -c $(CCFLAGS) $(INCLUDE) $(DEFS)  $< -o $@

$(OUT): $(OBJS) 
    $(CCC) -o $(OUT) $(OBJECT) $(OBJS) $(LIBS) $(CFLAGS) $(LDFLAGS) $(LIB)
    #$(AR) rcs $(OUTLIB) $(OBJS)
    rm -f $(OBJS)

depend: dep

dep:
#   makedepend -- $(CFLAGS) -- $(INCLUDES) $(SRC)

clean:
    del  $(OBJS) $(OUT)

i got the following error

        libLSBioCore.so: undefined reference to `__aeabi_dcmple'
        libLSBioCore.so: undefined reference to `__aeabi_fadd'
        libLSBioCore.so: undefined reference to `__aeabi_fcmpgt'
        libLSBioCore.so: undefined reference to `__aeabi_i2f'
        libLSBioCore.so: undefined reference to `__aeabi_dcmplt'
        libLSBioCore.so: undefined reference to `__aeabi_ddiv'
        libLSBioCore.so: undefined reference to `__aeabi_dmul'
        libLSBioCore.so: undefined reference to `__aeabi_d2f'
        libLSBioCore.so: undefined reference to `__aeabi_fsub'
        libLSBioCore.so: undefined reference to `__aeabi_fcmpge'
        libLSBioCore.so: undefined reference to `__aeabi_dadd'
        libLSBioCore.so: undefined reference to `__aeabi_idiv'
        libLSBioCore.so: undefined reference to `__aeabi_dcmpgt'
        libLSBioCore.so: undefined reference to `__aeabi_dcmpge'
        libLSBioCore.so: undefined reference to `__aeabi_dsub'
        libLSBioCore.so: undefined reference to `__aeabi_f2iz'
        libLSBioCore.so: undefined reference to `__aeabi_fdiv'
        libLSBioCore.so: undefined reference to `__aeabi_i2d'
        libLSBioCore.so: undefined reference to `__aeabi_fcmpeq'
        libLSBioCore.so: undefined reference to `__aeabi_fmul'
        libLSBioCore.so: undefined reference to `__aeabi_fcmplt'
        libLSBioCore.so: undefined reference to `__aeabi_dcmpeq'
        libLSBioCore.so: undefined reference to `__aeabi_f2uiz'
        libLSBioCore.so: undefined reference to `__aeabi_d2iz'
        libLSBioCore.so: undefined reference to `__aeabi_f2d'
        libLSBioCore.so: undefined reference to `__aeabi_idivmod'
        collect2: ld returned 1 exit status
        Makefile:57: recipe for target `Test.exe' failed

i hope i gave the proper link in my make ,i can;t get what the error behind this,do anyone have idea about how to make exe using arm-linux-androideabi-gcc.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T00:39:08+00:00Added an answer on June 12, 2026 at 12:39 am

    You have chosen a complicated way; note that with ndk-build you can build an executable much easier. For example, look at the test-libstdc++ NDK sample.

    But using the bare make is also possible. You need more libraries though, when you set -nostdlib on your command line.

    Add -lgcc. You may need more libs from toolchains/arm-linux-androideabi-4.6/prebuilt/windows/lib/gcc/arm-linux-androideabi/4.6.x-google to satisfy more references.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have one basic doubt. I have a process which uses a shared library.
I have a shared library which is supposed to export only one function which
I have a core project which I'm building as a shared library. In one
Suppose we have a shared library named libtest.so, there is one function foo in
I need to verify something for which I have doubts. If a shared library
I have a Class Library project which houses some shared code between other projects
Is it good practice to have one shared SqlConnection object in a .NET application
I have one XML request which I need to modify (to XML) and then
Does a C++ shared library have its own memory space? Or does it share
Here's the situation, I've got a C++ codebase which is using a recent GCC

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.