Changes for libstdc++ version 2.8.1 to version 2.8.1.1. Before applying these diffs, rename the directory into which you unpacked libstdc++ 2.8.1 to libstdc++-2.8.1.1. Then go into that directory and execute the following command: patch -p1 -E feeding it the following diffs as input. diff -r -c2 -p -N libstdc++-2.8.1/ChangeLog libstdc++-2.8.1.1/ChangeLog *** libstdc++-2.8.1/ChangeLog Sat Feb 28 11:18:36 1998 --- libstdc++-2.8.1.1/ChangeLog Thu Mar 19 09:51:02 1998 *************** *** 1,2 **** --- 1,19 ---- + Thu Mar 19 08:08:43 1998 Manfred Hollstein + + * libstdc++-2.8.1.1 minor release. + + Thu Mar 19 07:42:09 1998 Manfred Hollstein + + * INSTALL: Add a section about how to report bugs. + + * Makefile.in (install-gcc): Don't specify LANGUAGES here. + (install-gcc-cross): Instead, override LANGUAGES here. + + Thu Mar 12 16:01:14 1998 Manfred Hollstein + + * config-ml.in: After building symlink tree call make distclean + if a Makefile got linked into ${ml_dir}/${ml_libdir}; this happens + to be the case for libiberty. + Sat Feb 28 11:18:26 1998 Manfred Hollstein diff -r -c2 -p -N libstdc++-2.8.1/INSTALL libstdc++-2.8.1.1/INSTALL *** libstdc++-2.8.1/INSTALL Tue Feb 24 15:08:43 1998 --- libstdc++-2.8.1.1/INSTALL Mon Mar 23 15:27:25 1998 *************** *** 1,3 **** ! Configuring libstdc++-2.8.1 Like most GNU software, libstdc++ must be configured before it can be built. --- 1,3 ---- ! Configuring libstdc++-2.8.1.1 Like most GNU software, libstdc++ must be configured before it can be built. *************** that each --with option has a correspond *** 97,105 **** ! Building libstdc++-2.8.1 Now that libstdc++ is configured, you are ready to build the compiler (if you unpacked the compiler sources as recommended above) and ! runtime libraries. We highly recommend that libstdc++ be built using gnu-make; other --- 97,108 ---- ! Building libstdc++-2.8.1.1 Now that libstdc++ is configured, you are ready to build the compiler (if you unpacked the compiler sources as recommended above) and ! runtime libraries. If you've arranged your compiler and library sources ! in the `one tree' proposal, you should call `make bootstrap'; this will ! bootstrap the compiler and the runtime libraries in one shot. If you don't ! want to build the compiler, simply call `make all'. We highly recommend that libstdc++ be built using gnu-make; other *************** versions may work, then again they might *** 108,112 **** ! Testing libstdc++-2.8.1 To see if the built compiler (optionally) and runtime libraries actually --- 111,115 ---- ! Testing libstdc++-2.8.1.1 To see if the built compiler (optionally) and runtime libraries actually *************** work, you can check them with `cd objdir *** 115,119 **** ! Final install libstdc++-2.8.1 Now that libstdc++ has been built and tested, you can install it with --- 118,122 ---- ! Final install libstdc++-2.8.1.1 Now that libstdc++ has been built and tested, you can install it with *************** That step completes the installation of *** 123,126 **** --- 126,227 ---- be found in prefix/bin where prefix is the value you specified with the --prefix to configure (or /usr/local by default). + + + + Found a bug? + + If you think you've found a bug, you should send a bug report to + . + + The fundamental principle of reporting bugs usefully is this: + + *report all the facts*. If you are not sure whether to state a fact or + leave it out, state it! + + Often people omit facts because they think they know what causes the + problem and they conclude that some details don't matter. Thus, you + might assume that the name of the variable you use in an example does + not matter. Well, probably it doesn't, but one cannot be sure. + Perhaps the bug is a stray memory reference which happens to fetch from + the location where that name is stored in memory; perhaps, if the name + were different, the contents of that location would fool the compiler + into doing the right thing despite the bug. Play it safe and give a + specific, complete example. That is the easiest thing for you to do, + and the most helpful. + + Keep in mind that the purpose of a bug report is to enable someone to + fix the bug if it is not known. It isn't very important what happens if + the bug is already known. Therefore, always write your bug reports on + the assumption that the bug is not known. + + Sometimes people give a few sketchy facts and ask, "Does this ring a + bell?" This cannot help us fix a bug, so it is basically useless. We + respond by asking for enough details to enable us to investigate. You + might as well expedite matters by sending them to begin with. + + Try to make your bug report self-contained. If we have to ask you + for more information, it is best if you include all the previous + information in your response, as well as the information that was + missing. + + Please report each bug in a separate message. This makes it easier + for us to track which bugs have been fixed and to forward your bugs + reports to the appropriate maintainer. + + Do not compress and encode any part of your bug report using programs + such as `uuencode'. If you do so it will slow down the processing of + your bug. If you must submit multiple large files, use `shar', which + allows us to read your message without having to run any decompression + programs. + + To enable someone to investigate the bug, you should include all + these things: + + * The version of GNU CC. You can get this by running it with the + `-v' option. + + Without this, we won't know whether there is any point in looking + for the bug in the current version of GNU CC. + + * A complete input file that will reproduce the bug. A single statement + is not enough of an example. In order to compile it, it must be + embedded in a complete file of compiler input; and the bug might + depend on the details of how this is done. + + * The command arguments you gave GNU CC or GNU C++ to compile that + example and observe the bug. For example, did you use `-O'? To + guarantee you won't omit something important, list all the options. + + If we were to try to guess the arguments, we would probably guess + wrong and then we would not encounter the bug. + + * The type of machine you are using, and the operating system name + and version number. + + * The operands you gave to the `configure' command when you installed + the compiler and libstdc++. + + * A complete list of any modifications you have made to the library + source. (We don't promise to investigate the bug unless it + happens with unmodified sources. But if you've made + modifications and don't tell us, then you are sending us on a wild + goose chase.) + + Be precise about these changes. A description in English is not + enough--send a context diff for them. + + Adding files of your own (such as a machine description for a + machine we don't support) is a modification of the library source. + + * Details of any other deviations from the standard procedure for + installing GNU libstdc++. + + * A description of what behavior you observe that you believe is + incorrect. For example, "The compiler gets a fatal signal," or, + "The assembler instruction at line 208 in the output is incorrect." + + Never send core dump files! We have no way of examining a core dump + for your type of machine unless we have an identical system--and if + we do have one, we should be able to reproduce the crash ourselves. diff -r -c2 -p -N libstdc++-2.8.1/Makefile.in libstdc++-2.8.1.1/Makefile.in *** libstdc++-2.8.1/Makefile.in Tue Feb 24 15:08:43 1998 --- libstdc++-2.8.1.1/Makefile.in Thu Mar 19 07:41:57 1998 *************** install-gcc: *** 1339,1343 **** s=`cd $(srcdir); pwd`; export s; \ $(SET_LIB_PATH) \ ! (cd gcc; $(MAKE) $(GCC_FLAGS_TO_PASS) LANGUAGES="c c++" install); \ else \ true; \ --- 1339,1343 ---- s=`cd $(srcdir); pwd`; export s; \ $(SET_LIB_PATH) \ ! (cd gcc; $(MAKE) $(GCC_FLAGS_TO_PASS) install); \ else \ true; \ *************** install-gcc-cross: *** 1350,1354 **** s=`cd $(srcdir); pwd`; export s; \ $(SET_LIB_PATH) \ ! (cd gcc; $(MAKE) $(GCC_FLAGS_TO_PASS) install); \ else \ true; \ --- 1350,1354 ---- s=`cd $(srcdir); pwd`; export s; \ $(SET_LIB_PATH) \ ! (cd gcc; $(MAKE) $(GCC_FLAGS_TO_PASS) LANGUAGES="c c++" install); \ else \ true; \ diff -r -c2 -p -N libstdc++-2.8.1/README libstdc++-2.8.1.1/README *** libstdc++-2.8.1/README Fri Aug 22 00:57:37 1997 --- libstdc++-2.8.1.1/README Mon Mar 23 15:24:53 1998 *************** *** 1,41 **** ! README for GNU development tools ! This directory contains various GNU compilers, assemblers, linkers, ! debuggers, etc., plus their support routines, definitions, and documentation. ! ! If you are receiving this as part of a GDB release, see the file gdb/README. ! If with a binutils release, see binutils/README; if with a libg++ release, ! see libg++/README, etc. That'll give you info about this ! package -- supported targets, how to use it, how to report bugs, etc. ! ! It is now possible to automatically configure and build a variety of ! tools with one command. To build all of the tools contained herein, ! run the ``configure'' script here, e.g.: ! ! ./configure ! make ! ! To install them (by default in /usr/local/bin, /usr/local/lib, etc), ! then do: ! make install ! ! (If the configure script can't determine your type of computer, give it ! the name as an argument, for instance ``./configure sun4''. You can ! use the script ``config.sub'' to test whether a name is recognized; if ! it is, config.sub translates it to a triplet specifying CPU, vendor, ! and OS.) ! ! If you have more than one compiler on your system, it is often best to ! explicitly set CC in the environment before running configure, and to ! also set CC when running make. For example (assuming sh/bash/ksh): ! ! CC=gcc ./configure ! make ! ! A similar example using csh: ! ! setenv CC gcc ! ./configure ! make Much of the code and documentation enclosed is copyright by --- 1,6 ---- ! README for GNU libstdc++ ! Look at INSTALL for instructions how to build this package, and how ! to report bugs. Much of the code and documentation enclosed is copyright by *************** the Free Software Foundation, Inc. See *** 43,47 **** COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. - - REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info - on where and how to report problems. --- 8,9 ---- diff -r -c2 -p -N libstdc++-2.8.1/config-ml.in libstdc++-2.8.1.1/config-ml.in *** libstdc++-2.8.1/config-ml.in Fri Aug 22 00:57:38 1997 --- libstdc++-2.8.1.1/config-ml.in Thu Mar 19 07:31:58 1998 *************** if [ -n "${multidirs}" ] && [ -z "${ml_n *** 564,567 **** --- 564,574 ---- (cd ${ml_dir}/${ml_libdir}; ../${dotdot}${ml_unsubdir}symlink-tree ../${dotdot}${ml_unsubdir}${ml_libdir} "") + if [ -f ${ml_dir}/${ml_libdir}/Makefile ]; then + if [ x"${MAKE}" = x ]; then + (cd ${ml_dir}/${ml_libdir}; make distclean) + else + (cd ${ml_dir}/${ml_libdir}; ${MAKE} distclean) + fi + fi ml_newsrcdir="." ml_srcdiroption= diff -r -c2 -p -N libstdc++-2.8.1/libiberty/ChangeLog libstdc++-2.8.1.1/libiberty/ChangeLog *** libstdc++-2.8.1/libiberty/ChangeLog Sat Feb 28 11:19:21 1998 --- libstdc++-2.8.1.1/libiberty/ChangeLog Thu Mar 19 07:31:58 1998 *************** *** 1,2 **** --- 1,7 ---- + Tue Mar 3 08:26:10 1998 Manfred Hollstein + + * config.table: Make locating frag files failsafe even for the + special case if configuring and building in srcdir. + Thu Feb 26 17:53:19 1998 Manfred Hollstein diff -r -c2 -p -N libstdc++-2.8.1/libiberty/config.table libstdc++-2.8.1.1/libiberty/config.table *** libstdc++-2.8.1/libiberty/config.table Sat Feb 28 11:20:18 1998 --- libstdc++-2.8.1.1/libiberty/config.table Thu Mar 19 07:31:58 1998 *************** echo "# Warning: this fragment is automa *** 60,67 **** for frag in ${frags}; do ! case "${frag}" in ! ../../config/* ) ! if [ -n "${with_target_subdir}" ] && [ "${srcdir}" = "." ] && [ "${with_target_subdir}" != "." ] ; then ! frag=../${frag} fi ;; --- 60,68 ---- for frag in ${frags}; do ! case ${frag} in ! ../* ) ! if [ ${srcdir} = . ]; then ! [ -n "${with_target_subdir}" ] && frag=../${frag} ! [ -n "${with_multisrctop}" ] && frag=${with_multisrctop}${frag} fi ;; diff -r -c2 -p -N libstdc++-2.8.1/libio/ChangeLog libstdc++-2.8.1.1/libio/ChangeLog *** libstdc++-2.8.1/libio/ChangeLog Sat Feb 28 11:19:40 1998 --- libstdc++-2.8.1.1/libio/ChangeLog Thu Mar 19 12:51:37 1998 *************** *** 1,2 **** --- 1,11 ---- + Thu Mar 19 12:51:23 1998 Manfred Hollstein + + * Makefile.in (VERSION): Bump to 2.8.1.1. + + Tue Mar 3 08:26:10 1998 Manfred Hollstein + + * configure.in: Make locating frag files failsafe even for the + special case if configuring and building in srcdir. + Thu Feb 26 17:53:19 1998 Manfred Hollstein diff -r -c2 -p -N libstdc++-2.8.1/libio/Makefile.in libstdc++-2.8.1.1/libio/Makefile.in *** libstdc++-2.8.1/libio/Makefile.in Tue Feb 24 15:08:44 1998 --- libstdc++-2.8.1.1/libio/Makefile.in Thu Mar 19 12:51:56 1998 *************** *** 18,22 **** srcdir = . ! VERSION = 2.8.1 # The config file (overriden by Linux). _G_CONFIG_H=_G_config.h --- 18,22 ---- srcdir = . ! VERSION = 2.8.1.1 # The config file (overriden by Linux). _G_CONFIG_H=_G_config.h diff -r -c2 -p -N libstdc++-2.8.1/libio/README libstdc++-2.8.1.1/libio/README *** libstdc++-2.8.1/libio/README Fri Aug 22 00:58:14 1997 --- libstdc++-2.8.1.1/libio/README Thu Mar 19 07:52:47 1998 *************** The library can be configured to build t *** 7,11 **** that is part of a C run-time library. ! This library is distributed with libg++; see ../libg++/README for installation instructions, and where to send bug reports and questions. --- 7,11 ---- that is part of a C run-time library. ! This library is distributed with libstdc++; see ../INSTALL for installation instructions, and where to send bug reports and questions. diff -r -c2 -p -N libstdc++-2.8.1/libio/configure.in libstdc++-2.8.1.1/libio/configure.in *** libstdc++-2.8.1/libio/configure.in Sat Feb 28 11:20:18 1998 --- libstdc++-2.8.1.1/libio/configure.in Thu Mar 19 07:31:58 1998 *************** esac *** 94,101 **** for frag in ${frags}; do ! case "${frag}" in ! ../../config/* ) ! if [ -n "${with_target_subdir}" ] && [ "${srcdir}" = "." ] && [ "${with_target_subdir}" != "." ] ; then ! frag=../${frag} fi ;; --- 94,102 ---- for frag in ${frags}; do ! case ${frag} in ! ../* ) ! if [ ${srcdir} = . ]; then ! [ -n "${with_target_subdir}" ] && frag=../${frag} ! [ -n "${with_multisrctop}" ] && frag=${with_multisrctop}${frag} fi ;; diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/ChangeLog libstdc++-2.8.1.1/libstdc++/ChangeLog *** libstdc++-2.8.1/libstdc++/ChangeLog Sat Feb 28 11:19:57 1998 --- libstdc++-2.8.1.1/libstdc++/ChangeLog Thu Mar 19 12:53:14 1998 *************** *** 1,2 **** --- 1,11 ---- + Thu Mar 19 12:51:23 1998 Manfred Hollstein + + * Makefile.in (VERSION): Bump to 2.8.1.1. + + Tue Mar 3 08:26:10 1998 Manfred Hollstein + + * configure.in: Make locating frag files failsafe even for the + special case if configuring and building in srcdir. + Thu Feb 26 17:53:19 1998 Manfred Hollstein diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/Makefile.in libstdc++-2.8.1.1/libstdc++/Makefile.in *** libstdc++-2.8.1/libstdc++/Makefile.in Tue Feb 24 15:08:44 1998 --- libstdc++-2.8.1.1/libstdc++/Makefile.in Thu Mar 19 12:53:23 1998 *************** *** 15,19 **** # Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ! VERSION = 2.8.1 OBJS = cstringi.o stdexcepti.o cstdlibi.o cmathi.o stlinst.o --- 15,19 ---- # Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ! VERSION = 2.8.1.1 OBJS = cstringi.o stdexcepti.o cstdlibi.o cmathi.o stlinst.o diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/configure.in libstdc++-2.8.1.1/libstdc++/configure.in *** libstdc++-2.8.1/libstdc++/configure.in Sat Feb 28 11:20:18 1998 --- libstdc++-2.8.1.1/libstdc++/configure.in Thu Mar 19 07:31:58 1998 *************** esac *** 66,73 **** for frag in ${frags}; do ! case "${frag}" in ! ../../config/* ) ! if [ -n "${with_target_subdir}" ] && [ "${srcdir}" = "." ] && [ "${with_target_subdir}" != "." ] ; then ! frag=../${frag} fi ;; --- 66,74 ---- for frag in ${frags}; do ! case ${frag} in ! ../* ) ! if [ ${srcdir} = . ]; then ! [ -n "${with_target_subdir}" ] && frag=../${frag} ! [ -n "${with_multisrctop}" ] && frag=${with_multisrctop}${frag} fi ;; diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/stl/ChangeLog libstdc++-2.8.1.1/libstdc++/stl/ChangeLog *** libstdc++-2.8.1/libstdc++/stl/ChangeLog Sat Feb 28 11:17:28 1998 --- libstdc++-2.8.1.1/libstdc++/stl/ChangeLog Thu Mar 19 07:31:58 1998 *************** *** 1,2 **** --- 1,7 ---- + Fri Mar 6 00:12:28 1998 H.J. Lu (hjl@gnu.org) + + * stl_config.h (__STL_PTHREADS): Don't define for glibc 2 if + _G_USING_THUNKS is not defined. + 1998-02-25 Jason Merrill diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/stl/stl_config.h libstdc++-2.8.1.1/libstdc++/stl/stl_config.h *** libstdc++-2.8.1/libstdc++/stl/stl_config.h Sat Feb 28 11:17:28 1998 --- libstdc++-2.8.1.1/libstdc++/stl/stl_config.h Thu Mar 19 07:31:58 1998 *************** *** 115,119 **** # define __STL_MEMBER_TEMPLATES # endif ! # if !defined(_NOTHREADS) && __GLIBC__ >= 2 # define __STL_PTHREADS # ifdef __STRICT_ANSI__ --- 115,121 ---- # define __STL_MEMBER_TEMPLATES # endif ! /* glibc pre 2.0 is very buggy. We have to disable thread for it. ! It should be upgraded to glibc 2.0 or later. */ ! # if !defined(_NOTHREADS) && __GLIBC__ >= 2 && defined(_G_USING_THUNKS) # define __STL_PTHREADS # ifdef __STRICT_ANSI__ diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/tests/ChangeLog libstdc++-2.8.1.1/libstdc++/tests/ChangeLog *** libstdc++-2.8.1/libstdc++/tests/ChangeLog Tue Feb 24 15:08:44 1998 --- libstdc++-2.8.1.1/libstdc++/tests/ChangeLog Thu Mar 19 12:54:05 1998 *************** *** 1,2 **** --- 1,6 ---- + Thu Mar 19 12:51:23 1998 Manfred Hollstein + + * Makefile.in (VERSION): Bump to 2.8.1.1. + Fri Feb 20 12:00:30 1998 Manfred Hollstein diff -r -c2 -p -N libstdc++-2.8.1/libstdc++/tests/Makefile.in libstdc++-2.8.1.1/libstdc++/tests/Makefile.in *** libstdc++-2.8.1/libstdc++/tests/Makefile.in Tue Feb 24 15:08:44 1998 --- libstdc++-2.8.1.1/libstdc++/tests/Makefile.in Thu Mar 19 12:54:10 1998 *************** *** 15,19 **** # Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ! VERSION = 2.8.1 SHLIB = libstdc++.so.$(VERSION) --- 15,19 ---- # Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ! VERSION = 2.8.1.1 SHLIB = libstdc++.so.$(VERSION)