Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3B6D740E.6080608@ece.gatech.edu>
Date: Sun, 05 Aug 2001 12:27:58 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: Some words for binutils announcement?
References: <20010804213233 DOT A6332 AT redhat DOT com>	<3B6CE974 DOT 7040302 AT ece DOT gatech DOT edu> <9173-Sun05Aug2001093959+0100-starksb AT ebi DOT ac DOT uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Package doc.  If people STILL keep asking these questions, then we can 
move the answers to a more noticeable location, like the main FAQ.

--Chuck


David Starks-Browning wrote:

> These can go in the package doc file, right?  Or should they go in
> the main FAQ?
> 
> Thanks,
> David
> 
> 
>>Expected FAQs:
>>
>>Q: "I can't link to -lfoo.  I get "symbol _nm_* undefined"  
>>A: "you need to recompile libfoo, or change your source code 
>>to use __declspec(dllimport). (You're trying to "auto-import"
>>from a library that was built by an old ld.  Either fix your
>>source code so you don't need to "auto-import", or recompile
>>the library with a new ld).  BTW, the original porter of 
>>libfoo probably fixed the libfoo include headers to do the
>>__declspec() definitions correctly for you; did you forget 
>>to -Ddefine something?  Read the porter's notes for libfoo."
>>
>>Q: Now that we don't need to worry about compile-time
>>flags to indicate static linking or dllexport or dllimport,
>>doesn't that mean that we can use libtool to build
>>shared libraries (DLLs) just like every other Unixish 
>>platform?
>>A: Theoretically, yes. But this requires a lot of updates to
>>the autotools (automake, autoconf, libtool) and then each
>>package should be "re-tooled" to use these updated scripts.
>>That's a long term process, but is beginning.  In fact,
>>one of the prerequisites is to update autoconf to version
>>2.52; Cygwin's autotools was updated to that version just
>>a week before this binutils was released.  Be patient.