Re: cygwin:g++linker problems

2008-10-17 Thread jayshankar nair
>Shared libraries have the extension .dll on Windows, not .so. >Specifying -lf will find your library if you named it cygf.dll or >libf.dll, or if you created an import library libf.dll.a. (It will find >other variants as well, like f.lib. Read the linker manual for the full >list.) compilation

Re: cygwin:g++linker problems

2008-10-17 Thread Brian Dessent
jayshankar nair wrote: > The libraries is build with gcc(in cygwin environment). Something to do with > flags or packages. Shared libraries have the extension .dll on Windows, not .so. Specifying -lf will find your library if you named it cygf.dll or libf.dll, or if you created an import librar

Re: cygwin:g++linker problems

2008-10-17 Thread jayshankar nair
> $ g++ -L. f1.cpp -lf > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot > find > -lf > collect2: ld returned 1 exit status. >>Assuming those .so are linux shared libraries, they have no chance of >>working under cygwin. You must rebuild the libraries with your cy

Re: cygwin:g++linker problems

2008-10-17 Thread Tim Prince
jayshankar nair wrote: > Hi, > > I am getting compilation problems while linking the test shared libraries in > cygwin1.7. gcc,g++ and bin-utils are installed in the system. Works fine in > linux. > > Files in test directory > /test > $ ls > f.c f.cpp f.o f1.c f1.cpp libf.so libfun.so >