Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <00d001c18313$a7784960$f7ef85ce@amr.corp.intel.com>
From: "Tim Prince" <tprince AT computer DOT org>
To: "Dennis Weber" <toshi AT studcs DOT uni-sb DOT de>, <cygwin AT cygwin DOT com>
References: <001701c18308$20bbcc40$c2e26086 AT sattoshi>
Subject: Re: make install fail with gcc 3.0.2
Date: Wed, 12 Dec 2001 05:48:15 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200


----- Original Message -----
From: "Dennis Weber" <toshi AT studcs DOT uni-sb DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Wednesday, December 12, 2001 4:25 AM
Subject: make install fail with gcc 3.0.2


> Hi
>
> I am trying to get the 3.0.2 version of gcc to run in the Cygwin 1.3.5
> environment on Win 2k
> pro. ./configure and make seem to do what they're supposed to do, but make
> install fails
> to copy the headers and libs to the right dirs...
> Maybe that's not all that's wrong but at least that's what I noticed.
> gcc 3.0.2 has its own directory on the root level and I did not set and
> options.
> I simply used the plain files that came with the sources, without changes
or
> options.
>
> Thanks a lot in advance,
>
> Dennis
> toshi AT studcs DOT uni-sb DOT de
If you plan to install the new compiler in a different directory from the
ones used by the cygwin compiler, you should copy /usr/include to your new
directory before running configure.  For example, if intending to install in
/usr/local (the default), you copy /usr/include to /usr/local/include.
Otherwise, the new compiler uses (and may modify) /usr/include.
If you wish to use a separate copy of binutils, you configure and install it
in a separate location from the original, and use the --with-as=<full path
to new as> option when configuring to build the new compiler.  I usually
rebuild and install over the original binutils, and use the same copy with
the original and new compilers.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/