🚀 go-pugleaf

This posting shows the changes to the g++ FAQ since the previous version.

------- g++FAQ.texi -------
*** -	Fri Mar 15 09:38:36 1996
--- g++FAQ.texi	Fri Mar  8 10:56:07 1996
***************
*** 12,18 ****
  @titlepage
  @title G++ FAQ
  @subtitle Frequently asked questions about the GNU C++ compiler
! @subtitle February 29, 1996 (leap day edition)
  @sp 1
  @author Joe Buck
  @page
--- 12,18 ----
  @titlepage
  @title G++ FAQ
  @subtitle Frequently asked questions about the GNU C++ compiler
! @subtitle March 5, 1996
  @sp 1
  @author Joe Buck
  @page
***************
*** 37,43 ****
  
  Please send updates and corrections to the FAQ to
  @code{jbuck@@synopsys.com}.  Please do @emph{not} use me as a resource
! to get your questions answered; that's what gnu.g++.help is for and I
  don't have the time to support the net's use of g++.
  
  Many FAQs, including this one, are available on the archive site
--- 37,43 ----
  
  Please send updates and corrections to the FAQ to
  @code{jbuck@@synopsys.com}.  Please do @emph{not} use me as a resource
! to get your questions answered; that's what @file{gnu.g++.help} is for and I
  don't have the time to support the net's use of g++.
  
  Many FAQs, including this one, are available on the archive site
***************
*** 50,56 ****
  @cindex C++ FAQ
  This FAQ is intended to supplement, not replace, Marshall Cline's
  excellent FAQ for the C++ language and for the newsgroup
! comp.lang.c++.  Especially if g++ is the first C++
  compiler you've ever used, the question ``How do I do <X> with g++?''
  is probably really ``How do I do <X> in C++?''.
  You can find this FAQ at
--- 50,56 ----
  @cindex C++ FAQ
  This FAQ is intended to supplement, not replace, Marshall Cline's
  excellent FAQ for the C++ language and for the newsgroup
! @file{comp.lang.c++}.  Especially if g++ is the first C++
  compiler you've ever used, the question ``How do I do <X> with g++?''
  is probably really ``How do I do <X> in C++?''.
  You can find this FAQ at
***************
*** 133,139 ****
  and such.  Some things in this section will eventually move elsewhere.
  
  @strong{News:} as I write this (late February 1996) the gateway
! connecting the bug-g++ mailing list and the gnu.g++.bug newsgroup
  is broken.  Please mail, do not post bug reports.
  
  @menu
--- 133,139 ----
  and such.  Some things in this section will eventually move elsewhere.
  
  @strong{News:} as I write this (late February 1996) the gateway
! connecting the bug-g++ mailing list and the @file{gnu.g++.bug} newsgroup
  is broken.  Please mail, do not post bug reports.
  
  @menu
***************
*** 284,291 ****
  in places in the code) is not libg++, though it is included in the
  libg++ distribution.  Rather, it contains classes and functions
  required by the ANSI/ISO standard.  The copyright conditions are the
! same as those for for the iostreams classes; the LGPL is not used.  See
! @xref{legalities}.
  
  This library, libstdc++, is in the libg++ distribution in versions 2.6.2
  and later.  It requires at least gcc 2.6.3 to build the libg++-2.6.2
--- 284,291 ----
  in places in the code) is not libg++, though it is included in the
  libg++ distribution.  Rather, it contains classes and functions
  required by the ANSI/ISO standard.  The copyright conditions are the
! same as those for for the iostreams classes; the LGPL is not used
! (@xref{legalities}).
  
  This library, libstdc++, is in the libg++ distribution in versions 2.6.2
  and later.  It requires at least gcc 2.6.3 to build the libg++-2.6.2
***************
*** 534,540 ****
  FSF sells floppies with DJGPP on them; see above for ordering software
  from the FSF.
  
! DJGPP has its own newsgroup: @file{news:comp.os.msdos.djgpp}.
  
  @cindex Amiga support
  For information on Amiga ports of gcc/g++, retrieve the file @*
--- 534,540 ----
  FSF sells floppies with DJGPP on them; see above for ordering software
  from the FSF.
  
! DJGPP has its own newsgroup: @file{comp.os.msdos.djgpp}.
  
  @cindex Amiga support
  For information on Amiga ports of gcc/g++, retrieve the file @*
***************
*** 549,555 ****
  along with many
  other GNU programs.  This version is usually the same as the latest FSF
  release.  See the ``Software FAQ'' for the Usenet group
! ``comp.sys.atari.st'' for more information.
  
  @cindex EMX port 
  @cindex gcc/2
--- 549,555 ----
  along with many
  other GNU programs.  This version is usually the same as the latest FSF
  release.  See the ``Software FAQ'' for the Usenet group
! @file{comp.sys.atari.st} for more information.
  
  @cindex EMX port 
  @cindex gcc/2
***************
*** 560,566 ****
  ``gcc/2''.  The latter port is no longer supported, since the EMX
  port includes all of its functionality.
  The EMX port's C library attempts to provide a Unix-like environment.
! For more information ask around on ``comp.os.os2.programmer.misc''.
  
  The EMX port is available by FTP from
  
--- 560,566 ----
  ``gcc/2''.  The latter port is no longer supported, since the EMX
  port includes all of its functionality.
  The EMX port's C library attempts to provide a Unix-like environment.
! For more information ask around on @file{comp.os.os2.programmer.misc}.
  
  The EMX port is available by FTP from
  
***************
*** 783,788 ****
--- 783,789 ----
  @node repository, repo bugs, Use GNU assembler?, installation
  @section How do I use the new repository code?
  
+ @cindex repo patch
  Because there is some disagreement about the details of the template
  repository mechanism, you'll need to obtain a patch from Cygnus Support
  to enable the 2.7.2 repository code.  You can obtain the patch by
***************
*** 791,796 ****
--- 792,802 ----
  There are patches for 2.7.0 and 2.7.1 in the same directory, though
  if you're going to rebuild the compiler you should use the latest one.
  
+ @cindex repo patch for BSD
+ If you're running NetBSD or BSDI, the Cygnus repo patch is not quite
+ correct.  Tim Liddelow has made an alternate version available at
+ @file{ftp://ftp.cst.com.au/pub/gcc-2.7.2-repo-bsd.gz}.
+ 
  After you've applied the patch, the @code{-frepo} flag will enable the
  repository mechanism.  The flag works much like the existing
  @code{-fno-implicit-templates} flag, except that auxiliary files, with
***************
*** 804,809 ****
--- 810,817 ----
  expanded.  No assumption is made that @file{foo.C} contains template
  definitions corresponding to template declarations in @file{foo.h}.
  
+ @cindex closure with repo
+ @cindex template closure
  Jason Merrill writes: ``To perform closure on a set of objects, just try
  to link them together.  It will fail, but as a side effect all needed
  instances will be generated in the objects.''
***************
*** 1274,1285 ****
  
  @cindex g++ bug report
  First, mail your bug report to "bug-g++@@prep.ai.mit.edu".  You may also
! post to gnu.g++.bug, but it's better to use mail, particularly if you
  have any doubt as to whether your news software generates correct reply
  addresses.  Don't mail C++ bugs to bug-gcc@@prep.ai.mit.edu.
  
  @strong{News:} as I write this (late February 1996) the gateway
! connecting the bug-g++ mailing list and the gnu.g++.bug newsgroup
  is (temporarily?) broken.  Please mail, do not post bug reports.
  
  @cindex libg++ bug report
--- 1282,1293 ----
  
  @cindex g++ bug report
  First, mail your bug report to "bug-g++@@prep.ai.mit.edu".  You may also
! post to @file{gnu.g++.bug}, but it's better to use mail, particularly if you
  have any doubt as to whether your news software generates correct reply
  addresses.  Don't mail C++ bugs to bug-gcc@@prep.ai.mit.edu.
  
  @strong{News:} as I write this (late February 1996) the gateway
! connecting the bug-g++ mailing list and the @file{gnu.g++.bug} newsgroup
  is (temporarily?) broken.  Please mail, do not post bug reports.
  
  @cindex libg++ bug report
***************
*** 1664,1670 ****
  hacked version of STL, based on work by Carsten Bormann, which permits
  g++ to compile at least the containers.  A full implementation is
  going to need improved template support, which will take a while yet
! (2.8.0 will compile the HP version successfully).
  
  Actually, the hacked STL and gcc-2.7.2 work quite well; I've succeeded
  in making significant use of it.
--- 1672,1679 ----
  hacked version of STL, based on work by Carsten Bormann, which permits
  g++ to compile at least the containers.  A full implementation is
  going to need improved template support, which will take a while yet
! (2.8.0 will compile the HP version successfully, except for a couple
! of easily fixed places where it violates the draft standard).
  
  Actually, the hacked STL and gcc-2.7.2 work quite well; I've succeeded
  in making significant use of it.
***************
*** 1917,1922 ****
--- 1926,1934 ----
  all the standard classes are in @file{-lstdc++}; you can do the link
  step with @code{c++} instead of @code{g++} to search only the
  @file{-lstdc++} library and avoid the LGPL'ed code in @file{-lg++}.
+ 
+ If you wish to discuss legal issues connected with GNU software on the
+ net, please use @file{gnu.misc.discuss}, not the technical newsgroups.
  
  @node index,  , legalities, Top
  @comment  node-name,  next,  previous,  up
-- 
-- Joe Buck 	<jbuck@synopsys.com>	(not speaking for Synopsys, Inc)

Work for something because it is good,
not just because it stands a chance to succeed.	   -- Vaclav Havel