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
From:	"Philip Brown" <pbrown00 AT earthlink DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	Bug in GCC Install
Date:	Thu, 5 Aug 2004 13:40:19 -0400
MIME-Version:	1.0
Message-Id:	<E1BsmDz-0004oL-00@avocet.mail.pas.earthlink.net>

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.

--Phil Brown


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

- Raw text -