Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 30 Aug 2004 07:23:25 +0200
From: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Reply-To: "Gerrit @ cygwin" <cygwin AT cygwin DOT com>
Organization: Esse keine toten Tiere
Message-ID: <1513742401.20040830072325@familiehaase.de>
To: cygwin AT cygwin DOT com
Subject: Re: BUG gcc-mingw 20040810-1 library search path
In-Reply-To: <20040830002353.53818.qmail@web40414.mail.yahoo.com>
References: <1008963871 DOT 20040830011922 AT familiehaase DOT de> <20040830002353 DOT 53818 DOT qmail AT web40414 DOT mail DOT yahoo DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hello Noname,

>> Maybe the definition of tooldir for binutlis builds
>> has changed?

> You tell me.

Hey, I'm not the binutils maintainer, I maintain gcc.



> At least, document it, make it *clearly visible* that
> this is the new policy: *No implicit support for
> w32api libraries*.

I didn't was aware that it changed, I stumbled myself when I tried to
build another package where libuuid was not found.

> Other developers and project managers will know what
> to expect, don't you think? And no,
> /usr/share/doc/Cygwin/blah.txt is not a good place for
> such an important change. If people actually *read*
> the documentation there, wouldn't the volume of this
> list reduce in half? Most people don't even know such
> documentation resource exists.


I changed nothing and as far as I can see, there was also nothing
changed in gcc which could lead to such annoyances.


Gerrit
-- 
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/