Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Sun, 21 Apr 2002 13:52:42 -0400
From: Christopher Faylor <cgf-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Cc: cygwin@cygwin.com
Subject: Re: FW: libtool devel package still  dll crippled.
Message-ID: <20020421175242.GA1121@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin-apps@cygwin.com, cygwin@cygwin.com
References: <005e01c1e774$2dab05d0$651c440a@BRAMSCHE> <005901c1e958$207ecfa0$651c440a@BRAMSCHE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <005901c1e958$207ecfa0$651c440a@BRAMSCHE>
User-Agent: Mutt/1.3.23.1i

Forwarding to the correct mailing list.

cgf

On Sun, Apr 21, 2002 at 07:15:25PM +0200, Ralf Habacker wrote:
>>>ld checks the symbols in the shared libs during compile time to see if
>>>it can resolve all symbols and appearantly also detects duplicated
>>>symbols.  On Linux it is not necassery impossible to have two libs that
>>>define the same symbols.  E.g.  this feature can be used to override
>>>the malloc implementation of libc.  Of course when this happens
>>>inadvertently it can lead to unexpected behaviour/crashes.  ELF (The
>>>linking format used on Linux) has rather complex rules for determining
>>>which symbol should be used if it is defined multiple times.  It also
>>>distinguishes between weak and strong symbols.  It might be that it is
>>>only possible to override weak-symbols and that multiple strong-symbols
>>>result in link-errors.
>>
>>Does the cygwin ld has some similar rules ?
>>
>Is nobody on this list, who can give an answer to this question ?

--
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/

