0

I am using a program like this with math.h function "sin" and stdio.h function"printf" used 

#include <stdio.h>
#include <math.h>

int main ()
{

    int x = sin(14);
    printf("hello");
    return 0;
}

And as stated by ephemient here that libc.so and libm.so (for math functions) should have been linked with the program , though when I run otool (similar to objdump) on the object file with the option "-L" that prints the shared libraries used, None of libc.so or libm.so are printed out

otool -L com_ex1.o

so what is the reason for this ? Am I using otool wrong? or the those libraries shouldn't appear as shared libraries ?

Community
  • 1
  • 1
Jay Shenawy
  • 953
  • 1
  • 12
  • 22

2 Answers2

3

You link the finished binaries, the intermidiate object files are not linked until they are linked together in a final binary along with the libraries used.

So when you generate an object file no linking occurs, thus it's logical that there is no evidence of a link to any library in the object file, because there was none.

Iharob Al Asimi
  • 52,653
  • 6
  • 59
  • 97
1

Dynamic libraries are linked to the final executable, not to the object files, so you should run (e.g.)

otool -L com_ex1

This should show something like

com_ex1:
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

because on OS X, the math library is part of libSystem:

$ ls -l /usr/lib/libm.dylib
lrwxr-xr-x  1 root  wheel  15  3 Jun 01:39 /usr/lib/libm.dylib@ -> libSystem.dylib
Martin R
  • 529,903
  • 94
  • 1,240
  • 1,382
  • Interesting, I didn't know that about OS X, I suppose though that if one uses _glibc_ then there will be no difference with what the OP expects. – Iharob Al Asimi Jun 07 '15 at 13:49