Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: 20 Oct 2000 01:35:04 -0400
Message-ID: <20001020053504.5350.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: jik AT curl DOT com
CC: cygwin AT sources DOT redhat DOT com
In-reply-to: <20001017205249.7782.qmail@lizard.curl.com> (message from
	Jonathan Kamens on 17 Oct 2000 16:52:49 -0400)
Subject: Re: [cgf: Re: rxvt SEGV (Win98, 1.1.5s/2000-10-08)]
References: <20001017120354 DOT A9810 AT cygnus DOT com> <20001017205249 DOT 7782 DOT qmail AT lizard DOT curl DOT com>

A few days ago, I wrote:

>  >  If you're really motivated, you can build cygwin yourself
>  
>  Alas, much easier said than done.  My attempt to build was failing in
>  all kinds of strange ways, apparently related to configure getting the
>  wrong answers about the questions it was asking.  The first wrong
>  answer I noticed in my build log was:
>  
>    checking whether gcc -L/scratch/jik/cygwin/build/i686-pc-cygwin/winsup -L/scratch/jik/cygwin/build/i686-pc-cygwin/winsup/cygwin -L/scratch/jik/cygwin/build/i686-pc-cygwin/winsup/w32api/lib -isystem /scratch/jik/cygwin/src/winsup/include -isystem /scratch/jik/cygwin/src/winsup/cygwin/include -isystem /scratch/jik/cygwin/src/winsup/w32api/include -isystem /scratch/jik/cygwin/src/newlib/libc/sys/cygwin -isystem /scratch/jik/cygwin/src/newlib/libc/sys/cygwin32 -B/scratch/jik/cygwin/build/i686-pc-cygwin/newlib/ -isystem /scratch/jik/cygwin/build/i686-pc-cygwin/newlib/targ-include -isystem /scratch/jik/cygwin/src/newlib/libc/include accepts -g... no
>  
>  After several hours of trying various things to debug this, I finally
>  relized that the problem is that many of the tests in the configure
>  scripts rely on empty output from gcc to indicate that there were no
>  errors, but gcc was generating the warning "file patch prefix
>  `/scratch/jik/cygwin/build/i686-pc-cygwin/newlib/' never used" to
>  stderr, thus causing all of those tests to fail.
>  
>  I worked around this problem and managed to get the build to finish by
>  moving gcc.exe to gcc.real and installing this as gcc:
>  
>    #!/bin/sh
>  
>    gcc.real "$@" 2>/tmp/err.$$
>    STATUS=$?
>    grep -v "file path prefix \`.*' never used" /tmp/err.$$ 1>&2
>    rm -f /tmp/err.$$
>    exit $STATUS
>  
>  Is this something y'all expect to fail?  If so, is it documented
>  anywhere?  If not, can it be fixed?

If anyone answered this part of my message, I didn't see it; did some
send an answer to the mailing list without CC'ing it to me?

In any case, this is still broken in the 10/18 snapshot.

Can someone from the Cygwin team either acknowledge that there is a
problem here or explain why it isn't one? :-)

Thanks,

  jik

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com