public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: david.abrahams@rcn.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
Date: Sat, 21 Jul 2001 10:46:00 -0000	[thread overview]
Message-ID: <20010721174446.13555.qmail@sourceware.cygnus.com> (raw)

>Number:         3758
>Category:       bootstrap
>Synopsis:       GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 21 10:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     David Abrahams
>Release:        GCC-3.0
>Organization:
>Environment:
Cygwin
>Description:
GCC-3.0 doesn't build under Cygwin out of the box. After running configure, you must patch line 224 of install.sh to add the .exe extension as follows:

 dsttmp=$dstdir/#inst.$$#.exe
                         ^^^^

A better patch could probably be made which detects Cygwin and automatically makes this adjustment, but I don't know how to do that.

One other fact, which probably has no specific relevance to Cygwin: if you install gcc using --with-prefix=... (so that you don't disturb your existing 2.95.x installation), you get an advisory about the requirements for linking. This advisory is generated by a section of ltmain.sh starting at
line 4892. Unfortunately, it comes in the middle of a huge amount of other make output which is probably best ignored. I installed GCC-3.0 twice before I noticed the advisory, and by the time installation was finished it had scrolled out of my buffer and was lost forever. I noticed enough to see that I could add "-L/usr/lib" to get things to link. If anyone knows how I can recover the complete information I'd love to know it. In any case I think it should be considered a bug that important advisories don't come at the end of the make process.

-Dave
>How-To-Repeat:
Download gcc-3.0
configure using --with-prefix=/usr/local/gcc-3.0
make bootstrap
make install
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-21 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 10:46 david.abrahams [this message]
2002-11-27  8:54 bangerth
2002-11-27  9:46 bangerth
2002-11-27 12:26 David Abrahams
2002-11-27 13:56 Wolfgang Bangerth

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=20010721174446.13555.qmail@sourceware.cygnus.com \
    --to=david.abrahams@rcn.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /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).