make install fail with gcc 3.0.2

make install fail with gcc 3.0.2

[Dennis Weber]

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@studcs.uni-sb.de


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

Re: make install fail with gcc 3.0.2

[Tim Prince]

----- Original Message -----
From: "Dennis Weber" <toshi@studcs.uni-sb.de>
To: <cygwin@cygwin.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@studcs.uni-sb.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/