Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

[Wolfgang Bangerth]

The following reply was made to PR bootstrap/3758; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: David Abrahams <dave@boost-consulting.com>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
   <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic
 reporting
Date: Tue, 19 Nov 2002 20:15:19 -0600 (CST)

 > > Synopsis: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
 > >
 > > State-Changed-From-To: open->feedback
 > > State-Changed-Why:
 > >     This is a rather old bootstrap failure report, and gcc3.0
 > >     is no longer supported. 
 > 
 > Don't look at me! I reported this Sat Jul 21 10:46:00 PDT 2001!
 
 Don't look at me neither, I am just checking old old reports of which I 
 think 90% can be closed since they no longer apply. I am just pinging 
 people to see what the present state is :-)
 
 
 > >      Can you please check whether you can build a newer version of
 > >     gcc on your platform and let us know about your findings?
 > 
 > Of course I have built many more recent GCCs on my platform since
 > then. Who could wait 18 months just to get going with GCC 3.x?
 
 Thanks for your quick reply!
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 

Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

[David Abrahams]

The following reply was made to PR bootstrap/3758; it has been noted by GNATS.

From: David Abrahams <dave@boost-consulting.com>
To: bangerth@dealii.org
Cc: gcc-bugs@gcc.gnu.org,  gcc-prs@gcc.gnu.org,  nobody@gcc.gnu.org,
	  gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad
 diagnostic reporting
Date: Tue, 19 Nov 2002 20:59:10 -0500

 bangerth@dealii.org writes:
 
 > Synopsis: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Tue Nov 19 18:02:02 2002
 > State-Changed-Why:
 >     This is a rather old bootstrap failure report, and gcc3.0
 >     is no longer supported. 
 
 Don't look at me! I reported this Sat Jul 21 10:46:00 PDT 2001!
 
 >      Can you please check whether you can build a newer version of
 >     gcc on your platform and let us know about your findings?
 
 Of course I have built many more recent GCCs on my platform since
 then. Who could wait 18 months just to get going with GCC 3.x?
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3758
 
 -- 
                        David Abrahams
    dave@boost-consulting.com * http://www.boost-consulting.com
 Boost support, enhancements, training, and commercial distribution
 

Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

[bangerth]

Synopsis: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Tue Nov 19 18:08:21 2002
State-Changed-Why:
    Reportedly works in the meantime.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3758

Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

[bangerth]

Synopsis: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Nov 19 18:02:02 2002
State-Changed-Why:
    This is a rather old bootstrap failure report, and gcc3.0
    is no longer supported. Can you please check whether you
    can build a newer version of gcc on your platform and let
    us know about your findings?
    
    Thanks
      W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3758

bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting

[david.abrahams]

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