Very Computer

I am trying to play a little with the pilot-link libs in C and am
compiling with gcc. The libs I need (I think) are libpisock. I compile
with the command

gcc prog.c -L/usr/lib -llibpisock -o prog

but I get the error

/usr/bin/ld: cannot find -llibpisock.so
collect2: ld returned 1 exit status

I have checked the /usr/lib directory and both the .so and .a file are
there. Also, /usr/lib are in my LD_LIBRARY_PATH, so I have tried to
compile without the -L option. Same results.Now this may in fact not
be the library I need to get the methods I want in the program, but
I'll worry about that later. Does anyone have any idea why the linker
can't find these libraries?

Thanks
Jeff

You want to say "-lpisock".  The linker adds the "lib" and the ".so"
(or ".a") automagically.

Quote:> I have checked the /usr/lib directory and both the .so and .a file are
> there. Also, /usr/lib are in my LD_LIBRARY_PATH, so I have tried to
> compile without the -L option.

LD_LIBRARY_PATH affects the runtime dynamic loader, not the search path
used by the build-time linker.  Besides, both the linker and the dynamic
loader will search /usr/lib by default.

--
Paul Kimoto
This message was originally posted on Usenet in plain text.  Any images,
hyperlinks, or the like shown here have been added without my consent,
and may be a violation of international copyright law.