Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3D6E599D.2040808@netcom.es> Date: Thu, 29 Aug 2002 17:27:57 +0000 From: Ignasi Villagrasa Organization: gri User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: es-es MIME-Version: 1.0 To: Cygwin Subject: dll versus so Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi everyone, I'm migrating a dll file from Windows operative system (cygwin compiled) to Linux RH 7.2 (GCC). I implemented the corresponding makefile to get the .so file working properly. After some time testing it and solving some problems, I got the library running. But I detect a problem now I'm not able to solve. I call A.so from an executable B. B and A.so have several routines duplicated. Obviously, the reason for having them is differnet compiler options for B and A.so. So, if I have the routine C duplicated in A.so and B, the internal code is different for C in A.so and C in B. Under Cygwin I don't have any problem because the executable and the dll file use their own routines, but in Linux C routine in B is always mapped everywhere in the program. So, when calling C from A.so the program calls C from B and I have an undesirable behaviour. Is it possible to adapt the compiler/linker behaviour to match the Windows compilation ? How can it be done ? Any compiler/linker option ? Thanks in advance. Ignasi Villagrasa. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/