Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sat, 24 Aug 2002 19:55:49 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: gcc 3.1.1 Message-ID: <20020824235549.GA15348@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <026a01c24a26$ad79ab80$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <026a01c24a26$ad79ab80$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i On Thu, Aug 22, 2002 at 10:55:46PM +0100, Conrad Scott wrote: >I've not noticed this issue reported as yet, so here goes. > >I've just installed the latest gcc 3.1.1 package and tried to >build the cygwin DLL. (I used a fresh build directory and >configured & built as usual.) In building the DLL itself I needed >to add -L/usr/lib/w32api to the command line; otherwise it failed >to find the shell32 and uuid libraries. >I was also slightly surprised that the DLL wasn't being linked >explicitly against the copies of those libraries from the current >build tree; for example, cygrun is linked in just that way. Is >this an omission or have I managed to mangle my configuration in >some way? Hmm. I don't have that problem but I really don't know why I don't or why gcc 3.1.1 should have been any different than any other version of gcc. I'll check in a fix for this. I have to tweak some things for gcc 3.2 now, in a related area, anyway. >TIA, expecting to hear that I've fscked something up, No such luck. Sorry. cgf