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: Thu, 5 Aug 2004 13:43:56 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bug in GCC Install
Message-ID: <20040805174356.GA2761@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <E1BsmDz-0004oL-00 AT avocet DOT mail DOT pas DOT earthlink DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1BsmDz-0004oL-00@avocet.mail.pas.earthlink.net>
User-Agent: Mutt/1.4.1i

On Thu, Aug 05, 2004 at 01:40:19PM -0400, Philip Brown wrote:
>There appears to be a bug in the configure scripts for GCC.  This bug
>relates to the install procedure for gcov.exe, and only appears when you
>build gcc for multiple targets.
>
>The install snippet for gcc is:
>
>if [ -f gcov.exe ]; \
>then \
>    rm -f /usr/bin/gcov.exe; \
>    /bin/sh
>/cygdrive/g/ChoiceW/Rev_3/cvs/src/developer/gcc-3.3.1-3/install-sh -c
>gcov.exe /usr/bin/`echo gcov|sed 's,x,x,'`.exe; \
>fi
>
>Note that the install-sh line changes the name of gcov via `echo gcov|sed
>'s,x,x,'`, while the rm line uses a constant name.  If the target is to a
>non i686-pc-cygwin machine, then the echo changes gcov to something like
>arm-gnu-gcov.  Yet the file which is removed is still gcov.exe (in the first
>line.)
>
>The result is that if you install gcc for the host first, it installs
>gcov.exe.  If you then install gcc for a target, it deletes the gcov built
>for the host.

This is a generic problem in gcc.

You should probably file a bug report at

http://gcc.gnu.org/bugzilla/enter_bug.cgi .

You might want to first investigate if this problem is fixed in a later
version of gcc, however.

Or, you could start a discussion at the gcc mailing list

gcc at gcc dot gnu dot org .

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