I believe that if you want to statically link a file with complete
path like that, you don't use the normal linker flags with gcc. You
can just treat the file as if it were a big .o file and just supply
the path i.e.:
was
gcc -l/home/sameersbn/libs/video.a470MV
(at least this is what I understand from your email)
becomes
gcc /home/sameersbn/libs/video.a470MV
Brian
On 10/26/06, Sameer Naik <sameer@xxxxxxxxxxxxxx> wrote:
*Hello,
im creating a shared library. and trying to link it to a static
library with extentions of the form video.a470MV.
im including the whole path of the library in the LDFLAGS
(/home/sameersbn/libs/video.a470MV)
these are included in the Makefile.am file.
when the linking is done, no errors are flashed and the linking
procedure completes without complains. but if i run the nm command on
the library created, i dont see any symbols of the static library in the
symbol table.
instead if i extract the .o470MV file from the static library and rename
them to .o and archive it as .a and do the linking again, then it works
fine and the symbol table shows the new symbol entries.
i would like to know how to get my .a470MV libraries to successfully get
linked into my new library.
plz help
thanks in advance
tc
sameer
*
