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
Message-ID: <010501c48e95$30a55770$78d96f83@robinson.cam.ac.uk>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <sengtsongpa-cygwin001 AT yahoo DOT com>
Cc: <cygwin AT cygwin DOT com>
References: <20040829212630 DOT 32357 DOT qmail AT web40414 DOT mail DOT yahoo DOT com>
Subject: Re: BUG gcc-mingw 20040810-1 library search path
Date: Mon, 30 Aug 2004 14:28:03 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
X-Cam-AntiVirus: No virus found
X-Cam-SpamDetails: Not scanned
X-IsSubscribed: yes
Note-from-DJ: This may be spam

sengtsongpa-cygwin001 AT yahoo DOT com wrote:
> --- "Gerrit P. Haase" <gp AT familiehaase DOT de> escribió:
>> Hallo sengtsongpa-cygwin001,
>>
>> Am Sonntag, 29. August 2004 um 17:20 schriebst du:
>>
>>> In previous versions of the mingw backend
>> distributed
>>> with Cygwin's gcc port, the frontend drivers would
>>> append both /usr/include/lib/mingw *and*
>>> /usr/lib/w32api to the linker's path. This happens
>> no
>>> more with the latter.
>>
>> Simple testcase please.  What is the actual search
>> path?
>> What was the link command?  More details, please.
>>
>
> Here is a compelling case on practical grounds:
>
> 1. Grab a copy of Cygwin Setup sources from CVS (the
> stable source bundle idstributed with the net
> installer will do equally well). You need a copy of
> libgetopt++ from a parallel directory.
>
> 2. Bootstrap and configure:
>
> bash-2.05b-$ ./configure CC="gcc -mno-cygwin" CXX="g++
> -mno-cygwin" --target=mingw32 --build=mingw32
>
> 3. Watch the build belly up at the linking stage:
...

I wonder if you have perhaps installed the 20040810 mingw additional files 
for 3.4.1, but are still using the main 3.3.3 release?

If not, your system is bizarre, because when I attempt to reproduce what you 
say above, the build never reaches the linking stage - having hit numerous 
errors first due to stricter behaviours in gcc 3.4.

Sidenote to Gerrit:
Perhaps the gcc-mingw-* version numbers should look like 3.4.1_20040810-1 - 
it might avoid some confusion. Or is there a reason not to use just 3.4.1-1 
?

Max.




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