Re: libstdc++/5047: stl_config.h does not install

Re: libstdc++/5047: stl_config.h does not install

[ljrittle]

Synopsis: stl_config.h does not install

State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Fri Dec  7 14:58:17 2001
State-Changed-Why:
    Not a bug.  stl_config.h is not used in the current (as
    shipped with gcc 3.0 and later) libstdc++-v3.  Users
    were never suppose to include this file anyways since
    it is not a standard file.

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

Re: libstdc++/5047: stl_config.h does not install

[ljrittle]

The following reply was made to PR libstdc++/5047; it has been noted by GNATS.

From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  hale@reboot.com, nobody@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5047: stl_config.h does not install
Date: 7 Dec 2001 22:58:17 -0000

 Synopsis: stl_config.h does not install
 
 State-Changed-From-To: open->closed
 State-Changed-By: ljrittle
 State-Changed-When: Fri Dec  7 14:58:17 2001
 State-Changed-Why:
     Not a bug.  stl_config.h is not used in the current (as
     shipped with gcc 3.0 and later) libstdc++-v3.  Users
     were never suppose to include this file anyways since
     it is not a standard file.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5047&database=gcc

Re: libstdc++/5047: stl_config.h does not install

[Phil Edwards]

The following reply was made to PR libstdc++/5047; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: Rob Hale <hale@reboot.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5047: stl_config.h does not install
Date: Fri, 7 Dec 2001 18:03:34 -0500

 > --------------49772E48A5D5B2C93303E22E
 > Content-Type: text/plain; charset=iso-8859-1
 > Content-Transfer-Encoding: base64
 
 If you would, please just send plain text email (no HTML, no funky encodings,
 no fonts, etc).  Those of us not using a web browser for mailreading only see
 weird 8-bit gibberish on the screen when base64 encodings are used.  Thanks.
 
 
 > I've tried to install the library with the compiler and separately. Neither
 > method places stl_config.h into /usr/local/include while installing gcc
 > v3.0.2.  My confusion was brought on by the fact that an earlier version of
 > the gcc compiler (2.96) installed with our Redhat distro did install
 > stl_config.h.
 
 Ah.  The library used there is a different codebase, version 2.  That library
 has been largely unmaintained for a few years, and is somewhat old now.
 The library currently shipping is version 3.
 
 Our response to bugs in libstdc++-v3 is to ask for a full bug report in
 GNATS for further analysis.  Our reponse to bugs in libstdc++-v2 is usually
 a noncommittal grunt.  :-)
 
 
 >   I'm porting legacy code to Linux.  The legacy code was written on an SGI
 > platform and includes stl_config.h directly.  I take it this is no longer the
 > standard method of working with the STL?
 
 Never was, really...  Part of the confusion here is that the most common
 and popular implementation of the code was maintained at SGI for years.
 And if you download their (old) implementation, you'll see all the old header
 files available, including stl_config.h.  Code written at SGI naturally
 assumes that their own implementation is in use, so their internal headers
 names were safe to use in their own code.
 
 The official C++ standard header names don't end in .h, so there's a warning
 sign for you in the future.  :-)  If you want a list of standard headers,
 just look in the g++-v3 include directory after installing GCC 3.x:  the
 filenames without '.' are standard (string, vector, and so forth).
 
 Files in a "bits" subdirectory, like stl_stack.h, are hands-off in
 portable code.
 
 (I'm going to get in trouble for saying this next bit, I know...)
 
 In the 3.x sources, the file libstdc++-v3/docs/doxygen/stdheader.cc
 contains an informal mapping from internal/old/SGI filenames to the most
 probable ISO-standard headers.  For example, instead of including <pair.h>
 use <utility> instead.  This file might be of use to you.
 
 
 Phil
 

Re: libstdc++/5047: stl_config.h does not install

[Phil Edwards]

The following reply was made to PR libstdc++/5047; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: hale@reboot.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5047: stl_config.h does not install
Date: Fri, 7 Dec 2001 16:52:42 -0500

 On Fri, Dec 07, 2001 at 09:10:47PM -0000, hale@reboot.com wrote:
 > >Priority:       high
 
 High priority is reserved for GCC maintainers.  You should read the bug
 reporting instructions before going further.
 
 
 > After two attempts to install the STL, I've run into the 
 > same bug.  stl_config.h does not install from the buildir
 > into /usr/local/include/g++-v3 as I would expect.
 
 
 stl_config.h was removed from the sources ten months ago.
 
 What version of the compiler are you using?  Are you installing the library
 at the same time as the compiler or separately?
 
 
 > Without
 > this file we cannot compile any of our source code which 
 > specifically include stl_config.h.  
 [...]
 > Is it no longer acceptable to call stl_config.h?
 
 stl_config.h is not a standard library header, and never was.
 
 What are you trying to accomplish exactly, i.e., why would you try to
 include an implementation-specific internal header?
 

libstdc++/5047: stl_config.h does not install

[hale]

>Number:         5047
>Category:       libstdc++
>Synopsis:       stl_config.h does not install
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 07 13:16:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     hale@reboot.com
>Release:        libstdc++-v3
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
After two attempts to install the STL, I've run into the 
same bug.  stl_config.h does not install from the buildir
into /usr/local/include/g++-v3 as I would expect.  Without
this file we cannot compile any of our source code which 
specifically include stl_config.h.  

Is this a known bug? Is there a work-around? Is it no longer
acceptable to call stl_config.h?
>How-To-Repeat:

>Fix:

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