public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Tim Prince" <tprince@computer.org>
To: "Dennis Weber" <toshi@studcs.uni-sb.de>, <cygwin@cygwin.com>
Subject: Re: make install fail with gcc 3.0.2
Date: Wed, 12 Dec 2001 05:54:00 -0000	[thread overview]
Message-ID: <00d001c18313$a7784960$f7ef85ce@amr.corp.intel.com> (raw)
In-Reply-To: <001701c18308$20bbcc40$c2e26086@sattoshi>


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

      reply	other threads:[~2001-12-12 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12  4:29 Dennis Weber
2001-12-12  5:54 ` Tim Prince [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00d001c18313$a7784960$f7ef85ce@amr.corp.intel.com' \
    --to=tprince@computer.org \
    --cc=cygwin@cygwin.com \
    --cc=toshi@studcs.uni-sb.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).