Emergency UNIX and Linux Support

We have a huge makefile composing of inclusion of libraries, objects and system libraries to generate a binary.

How do we find out that which of the libraries we can remove in the most efficient way? Doing hit and trial method is a waste of time and can during the linking with some post linking script can we find that it is fine to remove this / these library from makefile

Compile your binary.

Code:

ldd mybinaryfile

will list the libraries linked into the executable.

But ldd prints the shared libraries required by each program or shared library specified on the command line. We have many static libraries also mentioned in our makefile

Hello ,
Make a backup copy of the Makefile.
do one thing. remove all the libraries except the shared ones that 'ldd' mentions as reported in the previous post.
so now you are left with only the shared library in the makefile. Compile the source and you would be shown the missing dependancies . Those dependancis are likely to be the required static libraries. and you can know which ones do you need.
After that you can take care of the original Makefile and trim it for useless static libraries.
Hope this helps.
Regards.

This is what I want to avoid - hit and trial method, the problem will get worse when inclusion of one object / static library file I have another dependency. Further this will take lots of workload and days to drive it to completion

Hello,
but this is once and for all. you would have to do only one step to know everything. This is not kind of hit and trial I feel. Its the only absolute solution if you dont want hit and trial.
Otherwise you would have to check the documentation or consult the actual developers to know the exact libraries and their dependancy.
Regards.

I am curious. What are you trying to achieve and why? Does your makefile force unneeded static libs to be included in the executable?