From: Thomas Tanner Date: Sat, 27 Mar 1999 16:58:10 +0000 (+0000) Subject: * NEWS: updated X-Git-Tag: release-1-3b~175 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=96dc12316e93a896c3abb59865feafadbcaaa716;p=thirdparty%2Flibtool.git * NEWS: updated * README: updated (BeOS support, no longer shared libraries support for AmigaOS), cleanups, we have now two mailing lists * REAMDE-alpha: autogen -> bootstrap, we have now two mailing lists * THANKS: added Xavier Pianet * doc/PLATFORMS: BeOS works * doc/libtool.texi: we have now to two mailing lists, updated -dlopen self documentation, documented libltdl's license, put each author in a separate line, inter-library dependencies on uninstalled libtool libraries are now supported, cleanups and minor corrections * libltdl/COPYING.LIB: new file * libltdl/ltdl.[ch]: added special exception to the LGPL license * libtool.spec: removed, it was outdated * Makefile.am: removed libtool.spec * ltmain.in: use TMPDIR when possible, create a subdirectory in the temporary directory, added -export-symbols-regex to the help, --- diff --git a/ChangeLog b/ChangeLog index fa16faa35..0cc91ec2d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,23 @@ +1999-03-27 Thomas Tanner + + * NEWS: updated + * README: updated (BeOS support, no longer shared libraries + support for AmigaOS), cleanups, we have now two mailing lists + * REAMDE-alpha: autogen -> bootstrap, we have now two mailing lists + * THANKS: added Xavier Pianet + * doc/PLATFORMS: BeOS works + * doc/libtool.texi: we have now to two mailing lists, + updated -dlopen self documentation, documented libltdl's license, + put each author in a separate line, + inter-library dependencies on uninstalled libtool libraries are + now supported, cleanups and minor corrections + * libltdl/COPYING.LIB: new file + * libltdl/ltdl.[ch]: added special exception to the LGPL license + * libtool.spec: removed, it was outdated + * Makefile.am: removed libtool.spec + * ltmain.in: use TMPDIR when possible, create a subdirectory + in the temporary directory, added -export-symbols-regex to the help, + 1999-03-25 Alexandre Oliva * demo/Makefile.am: create a static library, link two libtool diff --git a/Makefile.am b/Makefile.am index a43a37cfe..45cb47f25 100644 --- a/Makefile.am +++ b/Makefile.am @@ -13,7 +13,7 @@ CPPLAGS = @CPPFLAGS@ aclocal_macros = libtool.m4 EXTRA_DIST = $(aclocal_macros) libtoolize.in ltconfig.in ltmain.in \ - libtool.spec mkstamp ChangeLog.0 + mkstamp ChangeLog.0 CLEANFILES = libtool libtoolize ltconfig.T ltmain.shT # These are required by libtoolize. diff --git a/NEWS b/NEWS index 674c25f2f..e68a743dc 100644 --- a/NEWS +++ b/NEWS @@ -1,6 +1,6 @@ NEWS - list of user-visible changes between releases of GNU Libtool -New in 1.3a: CVS version, Libtool team: +New in 1.3b: 1999-??-??; CVS version 1.3a, Libtool team: * Complete inter-library dependencies support. It's now possible to link libtool libraries against other libtool libraries. * Already-installed libtool libraries will be found. @@ -8,11 +8,13 @@ New in 1.3a: CVS version, Libtool team: * New demos and tests * Various bugfixes -New in 1.2g: CVS version, Libtool team: +New in 1.3: 1999-03-??; CVS version 1.2g, Libtool team: * dlopen support for BeOS * Improved support for BeOS and Cygwin +* Documentation updates +* Bugfixes -New in 1.2e: CVS version; 1.2f: 1999-03-15, Libtool team: +New in 1.2f: 1999-03-15; CVS version 1.2e, Libtool team: * libtool will correctly link uninstalled libraries into programs and prefer uninstalled libraries to installed ones * Library paths that are in the system default run-time search path @@ -54,7 +56,7 @@ New in 1.2e: CVS version; 1.2f: 1999-03-15, Libtool team: * New demos and tests * Various bugfixes -New in 1.2c: CVS version; 1.2d: 1998-12-16, Libtool team: +New in 1.2d: 1998-12-16; CVS version 1.2c, Libtool team: * libtool will correctly link already-installed libraries into programs. * New -module flag, to create loadable modules. * New libltdl, a small library for portable dlopening of modules. diff --git a/README b/README index 02754c1f1..975405a4d 100644 --- a/README +++ b/README @@ -9,13 +9,12 @@ details. Libtool supports building static libraries on all platforms. Shared library support has been implemented for these platforms: - AIX 3.x (*-*-aix3*) - AIX 4.x (*-*-aix4*) - AmigaOS (*-*-amigaos*) - BSD/OS 4.x (*-*-bsdi4*) + AIX 3.x, 4.x (*-*-aix3*, *-*-aix4*) + BeOS (*-*-beos*) + BSD/OS 2.1, 3.x, 4.x (*-*-bsdi2.1, *-*-bsdi3*, *-*-bsdi4*) Digital/UNIX 3.x, 4.x, a.k.a. OSF/1 (*-*-osf3*, *-*-osf4*) DG/UX R4.11, R4.12, R4.20 (*-*-dguxR411*, *-*-dguxR412*, *-*-dguxR420*) - FreeBSD 2.x, 3.x (*-*-freebsd2*, *-*-freebsd3*) + FreeBSD 2.x, 3.x, 4.x (*-*-freebsd2*, *-*-freebsd3*, *-*-freebsd4*) GNU/Linux ELF (*-*-linux-gnu*, except aout, coff, and oldld) HP-UX 9.x, 10.x, 11.x (*-*-hpux9*, *-*-hpux10*, *-*-hpux11*) [see note] IRIX 5.x, 6.x (*-*-irix5*, *-*-irix6*) @@ -58,6 +57,6 @@ support was tested on. If you have any suggestions or bug reports, or you wish to port libtool to a new platform, please send electronic mail to the libtool -mailing list . Don't forget to mention the -version of libtool that you are currently using (by typing `ltconfig ---version'). +mailing list or bug reports to . +Don't forget to mention the version of libtool that you are currently +using (by typing `ltconfig --version'). diff --git a/README-alpha b/README-alpha index d42355598..ea4e8b84e 100644 --- a/README-alpha +++ b/README-alpha @@ -5,15 +5,17 @@ CVS version of this package, do: [Hit return when prompted for the password] cvs -d :pserver:anoncvs@anoncvs.gnu.org:/gd/gnu/anoncvsroot checkout libtool cd libtool - ./autogen + ./bootstrap -The `autogen' script sets up the source directory for you to hack. To +The `bootstrap' script sets up the source directory for you to hack. To use it, you need a recent (maybe yet to be released) version of both Autoconf and Automake. -Please do not send any bug reports or questions about this snapshot to -public forums (such as GNU newsgroups), send them directly to the -libtool mailing list, . +If you have any suggestions or bug reports, or you wish to port +libtool to a new platform, please send electronic mail to the libtool +mailing list or bug reports to . +Don't forget to mention the version of libtool that you are currently +using (by typing `ltconfig --version'). ================================================================ = Administrivia diff --git a/THANKS b/THANKS index 242b00961..742d4cdf1 100644 --- a/THANKS +++ b/THANKS @@ -34,3 +34,4 @@ Steven M. Schultz Todd Vierling Tom Tromey Ulrich Drepper +Xavier Pianet diff --git a/doc/PLATFORMS b/doc/PLATFORMS index fbbc145ec..a5b9522e4 100644 --- a/doc/PLATFORMS +++ b/doc/PLATFORMS @@ -20,6 +20,7 @@ hppa1.1-hp-hpux9.07 gcc 1.2f ok hppa1.1-hp-hpux9.07 cc 1.0f ok hppa1.1-hp-hpux9.05 gcc 1.2f ok hppa1.1-hp-hpux9.01 gcc 1.2f ok +i*86-*-beos gcc 1.2f ok i*86-*-bsdi4.0 gcc 1.2f ok i*86-*-bsdi4.0.1 gcc 1.2f ok i*86-*-bsdi3.1 gcc 1.2e NS diff --git a/doc/libtool.texi b/doc/libtool.texi index 5f6a95e2a..be2d1992a 100644 --- a/doc/libtool.texi +++ b/doc/libtool.texi @@ -7,7 +7,8 @@ @c %**end of header @include version.texi -@set BUGADDR the libtool mailing list @email{bug-libtool@@gnu.org} +@set BUGADDR the libtool bug reporting address @email{bug-libtool@@gnu.org} +@set MAILLIST the libtool mailing list @email{libtool@@gnu.org} @set objdir .libs @dircategory GNU programming tools @@ -51,7 +52,10 @@ approved by the Foundation. @titlepage @title GNU Libtool @subtitle For version @value{VERSION}, @value{UPDATED} -@author Gordon Matzigkeit, Alexandre Oliva, Thomas Tanner, Gary V. Vaughan +@author Gordon Matzigkeit +@author Alexandre Oliva +@author Thomas Tanner +@author Gary V. Vaughan @page @vskip 0pt plus 1filll @@ -1172,12 +1176,11 @@ If the platform requires versioning, this option has no effect. @item -dlopen @var{file} Same as @samp{-dlpreopen @var{file}}, if native dlopening is not -supported on the host platform (@pxref{Dlopened modules}) or, if -@var{file} is @code{self} and @var{dlopen_self} is set to @samp{no}. -Otherwise, no effect. If the program is linked with @samp{-static} or -@samp{-all-static}, the variable tested is @var{dlopen_self_static}, not -@var{dlopen_self}, as long as the @samp{-dlopen self} switch appears -@emph{after} the static-linking switch. +supported on the host platform (@pxref{Dlopened modules}) or if +the program is linked with @samp{-static} or @samp{-all-static}. +Otherwise, no effect. If @var{file} is @code{self} libtool will make +sure that the program can @code{dlopen} itself, either by enabling +@code{-export-dynamic} or by falling back to @samp{-dlpreopen self}. @item -dlpreopen @var{file} Link @var{file} into the output program, and add its symbols to @@ -1696,8 +1699,8 @@ on @file{libtool}. @defmac AC_LIBTOOL_DLOPEN Enable checking for dlopen support. This macro should be used if -the package makes use of the -dlopen and -dlpreopen flags, otherwise -libtool will assume that the system does not support dlopening. +the package makes use of the @samp{-dlopen} and @samp{-dlpreopen} flags, +otherwise libtool will assume that the system does not support dlopening. The macro must be called *before* @code{AM_PROG_LIBTOOL}. @end defmac @@ -2323,9 +2326,7 @@ In any event, libtool provides a simple mechanism for you to declare inter-library dependencies: for every library @file{lib@var{name}} that your own library depends on, simply add a corresponding @code{-l@var{name}} option to the link line when you create your -library.@footnote{Unfortunately, as of libtool version @value{VERSION}, -there is no way to specify inter-library dependencies on libtool -libraries that have not yet been installed.} To make an example of our +library. To make an example of our @file{libhello} that depends on @file{libm}: @example @@ -2589,23 +2590,34 @@ implementation of @file{libltdl} services, it requires GNU DLD, or it will only emulate dynamic linking with libtool's dlpreopening mechanism. @noindent -Libltdl supports currently the following dynamic linking mechanims: +libltdl supports currently the following dynamic linking mechanims: @itemize @bullet @item -dlopen (Solaris, Linux and various BSD flavors) +@code{dlopen} (Solaris, Linux and various BSD flavors) @item -shl_load (HP-UX) +@code{shl_load} (HP-UX) @item -LoadLibrary (Win16 and Win32) +@code{LoadLibrary} (Win16 and Win32) @item -load_add_on (BeOS) +@code{load_add_on} (BeOS) @item GNU DLD (emulates dynamic linking for static libraries) @item libtool's dlpreopen (see @pxref{Dlpreopening}) @end itemize +@noindent +libltdl is licensed under the terms of the GNU Library General Public License, +with the following exception: + +@quotation +As a special exception to the GNU Library General Public License, +if you distribute this file as part of a program that uses GNU libtool +to create libraries and programs, you may include it under the same +distribution terms that you use for the rest of that program. +@end quotation + @menu * Libltdl interface:: How to use libltdl in your programs. * Modules for libltdl:: Creating modules that can be @code{dlopen}ed. @@ -2620,7 +2632,7 @@ The libltdl API is similar to the dlopen interface of Solaris and Linux, which is very simple but powerful. @noindent -To use libltdl in your program you have include the header file @file{ltdl.h}: +To use libltdl in your program you have to include the header file @file{ltdl.h}: @example #include @@ -2652,8 +2664,9 @@ Every dlopened module has a handle associated with it. This structure is described in @pxref{Dlpreopening}. @end table +@page @noindent -Libltdl provides the following functions: +libltdl provides the following functions: @deftypefun int lt_dlinit (void) Initialize libltdl. @@ -2682,7 +2695,7 @@ flag, then the global symbols in the executable will also be used to resolve references in the module. If @var{filename} is NULL and the program was linked with -@code{-export-dynamic} and @code{-dlopen self}, @code{lt_dlopen} will +@code{-export-dynamic} or @code{-dlopen self}, @code{lt_dlopen} will return a handle for the program itself, which can be used to access its symbols. @@ -2790,7 +2803,8 @@ search path. Return 0 on success. @deftypefun int lt_dlsetsearchpath (const char *@var{search_path}) Replace the current user-defined library search path with -@var{search_path}. Return 0 on success. +@var{search_path}, which must be a colon-separated list of absolute +directories. Return 0 on success. @end deftypefun @deftypefun const char *lt_dlgetsearchpath (void) @@ -2823,7 +2837,7 @@ Note that libtool modules don't need to have a "lib" prefix. However, automake 1.4 or higher is required to build such modules. Usually a set of modules provide the same interface, i.e, exports the same -symbols, so that a program can dlopen them without having to know more +symbols, so that a program can dlopen them without having to know more about their internals. In order to avoid symbol conflicts all exported symbols must be prefixed with "modulename_LTX_" (@samp{modulename} is the name of the module). @@ -3301,7 +3315,7 @@ porting libtool to new systems, or writing your own libtool. @section Porting libtool to new systems Before you embark on porting libtool to an unsupported system, it is -worthwhile to send e-mail to @value{BUGADDR}, to make sure that you are +worthwhile to send e-mail to @value{MAILLIST}, to make sure that you are not duplicating existing work. If you find that any porting documentation is missing, please complain! @@ -3379,10 +3393,9 @@ Kuratomi @email{badger@@prtr-13.ucsc.edu}. Here's a shortened version of the message that contained his patch: The basic architecture is this: in @file{ltconfig.in}, the person who -writes libtool makes sure @samp{$deplibs}, or @samp{$compile_dependencylibs} -are included in @samp{$archive_cmds} somewhere and also sets the -@samp{$deplibs_check_method}, and maybe @samp{$file_magic_cmd} when -@samp{deplibs_check_method} is file_magic. +writes libtool makes sure @samp{$deplibs} is included in @samp{$archive_cmds} +somewhere and also sets the @samp{$deplibs_check_method}, and maybe +@samp{$file_magic_cmd} when @samp{deplibs_check_method} is file_magic. @samp{deplibs_check_method} can be one of five things: @table @samp @@ -3458,7 +3471,7 @@ when run @code{configure} with @kbd{CC='cc -Hnocopyr'}. @node Platform quirks @section Platform quirks -This section is dedicated to the sanity of the libtool maintainer. It +This section is dedicated to the sanity of the libtool maintainers. It describes the programs that libtool uses, how they vary from system to system, and how to test for them. diff --git a/libltdl/COPYING.LIB b/libltdl/COPYING.LIB new file mode 100644 index 000000000..eb685a5ec --- /dev/null +++ b/libltdl/COPYING.LIB @@ -0,0 +1,481 @@ + GNU LIBRARY GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the library GPL. It is + numbered 2 because it goes with version 2 of the ordinary GPL.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Library General Public License, applies to some +specially designated Free Software Foundation software, and to any +other libraries whose authors decide to use it. You can use it for +your libraries, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if +you distribute copies of the library, or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link a program with the library, you must provide +complete object files to the recipients so that they can relink them +with the library, after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + Our method of protecting your rights has two steps: (1) copyright +the library, and (2) offer you this license which gives you legal +permission to copy, distribute and/or modify the library. + + Also, for each distributor's protection, we want to make certain +that everyone understands that there is no warranty for this free +library. If the library is modified by someone else and passed on, we +want its recipients to know that what they have is not the original +version, so that any problems introduced by others will not reflect on +the original authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that companies distributing free +software will individually obtain patent licenses, thus in effect +transforming the program into proprietary software. To prevent this, +we have made it clear that any patent must be licensed for everyone's +free use or not licensed at all. + + Most GNU software, including some libraries, is covered by the ordinary +GNU General Public License, which was designed for utility programs. This +license, the GNU Library General Public License, applies to certain +designated libraries. This license is quite different from the ordinary +one; be sure to read it in full, and don't assume that anything in it is +the same as in the ordinary license. + + The reason we have a separate public license for some libraries is that +they blur the distinction we usually make between modifying or adding to a +program and simply using it. Linking a program with a library, without +changing the library, is in some sense simply using the library, and is +analogous to running a utility program or application program. However, in +a textual and legal sense, the linked executable is a combined work, a +derivative of the original library, and the ordinary General Public License +treats it as such. + + Because of this blurred distinction, using the ordinary General +Public License for libraries did not effectively promote software +sharing, because most developers did not use the libraries. We +concluded that weaker conditions might promote sharing better. + + However, unrestricted linking of non-free programs would deprive the +users of those programs of all benefit from the free status of the +libraries themselves. This Library General Public License is intended to +permit developers of non-free programs to use free libraries, while +preserving your freedom as a user of such programs to change the free +libraries that are incorporated in them. (We have not seen how to achieve +this as regards changes in header files, but we have achieved it as regards +changes in the actual functions of the Library.) The hope is that this +will lead to faster development of free libraries. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, while the latter only +works together with the library. + + Note that it is possible for a library to be covered by the ordinary +General Public License rather than by this special one. + + GNU LIBRARY GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library which +contains a notice placed by the copyright holder or other authorized +party saying it may be distributed under the terms of this Library +General Public License (also called "this License"). Each licensee is +addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also compile or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + c) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + d) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the source code distributed need not include anything that is normally +distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Library General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Library General Public + License as published by the Free Software Foundation; either + version 2 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Library General Public License for more details. + + You should have received a copy of the GNU Library General Public + License along with this library; if not, write to the Free + Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! diff --git a/libltdl/ltdl.c b/libltdl/ltdl.c index df93ce077..734476206 100644 --- a/libltdl/ltdl.c +++ b/libltdl/ltdl.c @@ -8,6 +8,11 @@ modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. +As a special exception to the GNU Library General Public License, +if you distribute this file as part of a program that uses GNU libtool +to create libraries and programs, you may include it under the same +distribution terms that you use for the rest of that program. + This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU diff --git a/libltdl/ltdl.h b/libltdl/ltdl.h index 2f58da355..035e1adbd 100644 --- a/libltdl/ltdl.h +++ b/libltdl/ltdl.h @@ -8,6 +8,11 @@ modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. +As a special exception to the GNU Library General Public License, +if you distribute this file as part of a program that uses GNU libtool +to create libraries and programs, you may include it under the same +distribution terms that you use for the rest of that program. + This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU diff --git a/libtool.m4 b/libtool.m4 index 7b3dd4615..68ac62403 100644 --- a/libtool.m4 +++ b/libtool.m4 @@ -1,6 +1,6 @@ ## libtool.m4 - Configure libtool for the target system. -*-Shell-script-*- ## Copyright (C) 1996-1999 Free Software Foundation, Inc. -## Gordon Matzigkeit , 1996 +## Originally by Gordon Matzigkeit , 1996 ## ## This program is free software; you can redistribute it and/or modify ## it under the terms of the GNU General Public License as published by diff --git a/libtool.spec b/libtool.spec deleted file mode 100644 index 09b2335eb..000000000 --- a/libtool.spec +++ /dev/null @@ -1,46 +0,0 @@ -Summary: GNU Libtool - shared library support for source packages -Name: libtool -Version: 1.3a -Release: 1 -Copyright: GPL -Group: Development/Build -Source: ftp://ftp.gnu.org/pub/gnu/libtool-%{PACKAGE_VERSION}.tar.gz -URL: http://www.gnu.org/software/libtool/libtool.html -BuildRoot: /tmp/libtool.root - -%description -This is GNU Libtool, a generic library support script. Libtool hides -the complexity of using shared libraries behind a consistent, portable -interface. - -To use libtool, add the new generic library building commands to your -Makefile, Makefile.in, or Makefile.am. See the documentation for -details. - -%prep -%setup - -%build -./configure --prefix=/usr -make - -%install -rm -rf $RPM_BUILD_ROOT -make install prefix=$RPM_BUILD_ROOT/usr -gzip -9nf $RPM_BUILD_ROOT/usr/info/libtool.info* - -%clean -rm -rf $RPM_BUILD_ROOT - -%files -%attr(0644, root, root) %doc AUTHORS COPYING ChangeLog NEWS README -%attr(0644, root, root) %doc THANKS TODO doc/PLATFORMS - -%attr(0755, root, root) /usr/bin/libtool -%attr(0755, root, root) /usr/bin/libtoolize -%attr(0644, root, root) /usr/info/libtool.info* -%attr(0755, root, root) /usr/share/libtool/config.guess -%attr(0755, root, root) /usr/share/libtool/config.sub -%attr(0755, root, root) /usr/share/libtool/ltconfig -%attr(0644, root, root) /usr/share/libtool/ltmain.sh -%attr(0644, root, root) /usr/share/aclocal/libtool.m4 diff --git a/libtoolize.in b/libtoolize.in index 83876d8f6..342ba6988 100644 --- a/libtoolize.in +++ b/libtoolize.in @@ -2,7 +2,7 @@ # libtoolize - Prepare a package to use libtool. # @configure_input@ # Copyright (C) 1996-1999 Free Software Foundation, Inc. -# Gordon Matzigkeit , 1996 +# Originally by Gordon Matzigkeit , 1996 # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff --git a/ltconfig.in b/ltconfig.in index 8c11444af..5e0a33705 100755 --- a/ltconfig.in +++ b/ltconfig.in @@ -2,7 +2,7 @@ # ltconfig - Create a system-specific libtool. # Copyright (C) 1996-1999 Free Software Foundation, Inc. -# Gordon Matzigkeit , 1996 +# Originally by Gordon Matzigkeit , 1996 # # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by diff --git a/ltmain.in b/ltmain.in index 8b3729bbb..d19497523 100644 --- a/ltmain.in +++ b/ltmain.in @@ -2,7 +2,7 @@ # NOTE: Changing this file will not affect anything until you rerun ltconfig. # # Copyright (C) 1996-1999 Free Software Foundation, Inc. -# Gordon Matzigkeit , 1996 +# Originally by Gordon Matzigkeit , 1996 # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -3979,8 +3979,16 @@ relink_command=\"$relink_command\"" outputname= if test "$fast_install" = no && test -n "$relink_command"; then - if test "$finalize" = yes; then - outputname="/tmp/$$-$file" + if test "$finalize" = yes && test -z "$run"; then + tmpdir="/tmp" + test -n "$TMPDIR" && tmpdir="$TMPDIR" + tmpdir="$tmpdir/libtool-$$" + if $mkdir -p "$tmpdir" && chmod 700 "$tmpdir"; then : + else + $echo "$modename: error: cannot create temporary directory \`$tmpdir'" 1>&2 + continue + fi + outputname="$tmpdir/$file" # Replace the output file specification. relink_command=`$echo "X$relink_command" | $Xsed -e 's%@OUTPUT@%'"$outputname"'%g'` @@ -3988,6 +3996,7 @@ relink_command=\"$relink_command\"" if $run eval "$relink_command"; then : else $echo "$modename: error: relink \`$file' with the above command before installing it" 1>&2 + ${rm}r "$tmpdir" continue fi file="$outputname" @@ -4002,7 +4011,7 @@ relink_command=\"$relink_command\"" $show "$install_prog$stripme $file $destfile" $run eval "$install_prog\$stripme \$file \$destfile" || exit $? - test -n "$outputname" && $rm $outputname + test -n "$outputname" && ${rm}r "$tmpdir" ;; esac done @@ -4470,6 +4479,8 @@ The following components of LINK-COMMAND are treated specially: -export-dynamic allow symbols from OUTPUT-FILE to be resolved with dlsym(3) -export-symbols SYMFILE try to export only the symbols listed in SYMFILE + -export-symbols-regex REGEX + try to export only the symbols matching REGEX -LLIBDIR search LIBDIR for required installed libraries -lNAME OUTPUT-FILE requires the installed library libNAME -module build a library that can dlopened