diff options
| author | David Edelsohn <edelsohn@gnu.org> | 2000-11-23 05:51:07 +0000 |
|---|---|---|
| committer | David Edelsohn <dje@gcc.gnu.org> | 2000-11-23 00:51:07 -0500 |
| commit | 54214152bd83582233b1179ea9a6d924cd817499 (patch) | |
| tree | 27455c4b05b45eab026ae1374585b62c7098bf0e | |
| parent | abb32cf595ff0a80ad20a8cf30c4590fc3031857 (diff) | |
| download | gcc-54214152bd83582233b1179ea9a6d924cd817499.zip gcc-54214152bd83582233b1179ea9a6d924cd817499.tar.gz gcc-54214152bd83582233b1179ea9a6d924cd817499.tar.bz2 | |
* porting.texi: Expand libtool information.
From-SVN: r37688
| -rw-r--r-- | libstdc++-v3/ChangeLog | 4 | ||||
| -rw-r--r-- | libstdc++-v3/porting.texi | 23 |
2 files changed, 20 insertions, 7 deletions
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index caaf9fe..612c043 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,7 @@ +2000-11-23 David Edelsohn <edelsohn@gnu.org> + + * porting.texi: Expand libtool information. + 2000-11-23 Gabriel Dos Reis <gdr@codesourcery.com> * include/bits/ios_base.h (ios_base::failure::~failure, diff --git a/libstdc++-v3/porting.texi b/libstdc++-v3/porting.texi index d966578..b29315e 100644 --- a/libstdc++-v3/porting.texi +++ b/libstdc++-v3/porting.texi @@ -420,13 +420,22 @@ __atomic_add (_Atomic_word* __mem, int __val) @node Libtool @chapter Libtool -The C++ library is linked with libtool. Explaining the full workings of -libtool is beyond the scope of this document, but there is one -particular bit that should be explained here. The C++ run-time library -contains initialization code that needs to be run as the library is -loaded. Often, that requires linking in special object files when the -C++ library is built as a shared library, or taking other -system-specific actions. +The C++ library is compiled, archived and linked with libtool. +Explaining the full workings of libtool is beyond the scope of this +document, but there are a few, particular bits that are necessary for +porting. + +Some parts of the libstdc++-v3 library are compiled with the libtool +@code{--tags CXX} option (the C++ definitions for libtool). Therefore, +@file{ltcf-cxx.sh} in the top-level directory needs to have the correct +logic to compile and archive objects equivalent to the C version of libtool, +@file{ltcf-c.sh}. Some libtool targets have definitions for C but not +for C++, or C++ definitions which have not been kept up to date. + +The C++ run-time library contains initialization code that needs to be +run as the library is loaded. Often, that requires linking in special +object files when the C++ library is built as a shared library, or +taking other system-specific actions. The libstdc++-v3 library is linked with the C version of libtool, even though it is a C++ library. Therefore, the C version of libtool needs to ensure |