Avoid mentioning "Linux", use "GNU/Linux", if appropriate.

* TODO: Don't use bare "Linux".
	* doc/libtool.texi: ditto.
	* doc/notes.texi: ditto.
	* libltdl/README: ditto.
	* libltdl/m4/libtool.m4: ditto.
This commit is contained in:
Cristophe Jarry 2011-09-25 17:39:04 -05:00 committed by Peter O'Gorman
parent dc28c2bfbc
commit 920da81be6
6 changed files with 29 additions and 20 deletions

View File

@ -1,3 +1,12 @@
2011-09-25 Cristophe Jarry <christophe.jarry@ouvaton.org>
Avoid mentioning "Linux", use "GNU/Linux", if appropriate.
* TODO: Don't use bare "Linux".
* doc/libtool.texi: ditto.
* doc/notes.texi: ditto.
* libltdl/README: ditto.
* libltdl/m4/libtool.m4: ditto.
2011-09-01 Peter O'Gorman <peter@pogma.com>
Add flag to inhibit warnings.

20
TODO
View File

@ -58,7 +58,7 @@ GNU Libtool
* Audit file listing in libtool.m4.
* Fix deplibs_check_method=pass_all (which is wrong!) on linux.
* Fix deplibs_check_method=pass_all (which is wrong!) on GNU/Linux.
* Fix -dlopen "self" on AIX. Reported by Gary Kumfert <kumfert@llnl.gov>.
@ -290,15 +290,15 @@ GNU Libtool
and central_unixish_to_mingw would still do all the work (with its guts
customized based on $build).
For more reasonable cross environments (e.g. linux->some_embedded) I think
you could probably work out a general M+N scheme, since most embedded $hosts
aren't as strange as the win32 variants -- even VxWorks and INTEGRITY have
basic, unix-like file systems (although INTEGRITY does have multiple roots).
Aggressive use of the m4 function_replace machinery WOULD be appropriate for
/these/ conversion functions. OTOH...(a) you can't run the $host apps on
$build anyway, in these embedded situations. At best you'd use $TARGETSHELL
and "run" them via a remote connection, and (b) they don't use the C
wrapper!
For more reasonable cross environments (e.g. linux-gnu->some_embedded) I
think you could probably work out a general M+N scheme, since most embedded
$hosts aren't as strange as the win32 variants -- even VxWorks and INTEGRITY
have basic, unix-like file systems (although INTEGRITY does have multiple
roots). Aggressive use of the m4 function_replace machinery WOULD be
appropriate for /these/ conversion functions. OTOH...(a) you can't run the
$host apps on $build anyway, in these embedded situations. At best you'd use
$TARGETSHELL and "run" them via a remote connection, and (b) they don't use
the C wrapper!
So...I don't think it makes much difference *right now* in the amount of
code required, or the number of functions implemented. At some point in the

View File

@ -3784,7 +3784,7 @@ libltdl supports currently the following dynamic linking mechanisms:
@itemize @bullet
@item
@code{dlopen} (Solaris, Linux and various BSD flavors)
@code{dlopen} (POSIX compliant systems, GNU/Linux, etc.)
@item
@code{shl_load} (HP-UX)
@item
@ -3823,7 +3823,7 @@ distribution terms that you use for the rest of that program.
@section How to use libltdl in your programs
@noindent
The libltdl API is similar to the dlopen interface of Solaris and Linux,
The libltdl API is similar to the POSIX dlopen interface,
which is very simple but powerful.
@noindent
@ -3945,7 +3945,7 @@ This search path is the value of the environment variable
@item system library search path:
The system dependent library search path
(e.g.@: on Linux it is @env{LD_LIBRARY_PATH}).
(e.g.@: on GNU/Linux it is @env{LD_LIBRARY_PATH}).
@end enumerate
Each search path must be a list of absolute directories separated by
@ -5372,7 +5372,7 @@ uninstalled correctly.
The @file{tests/mdemo} subdirectory contains a demonstration of a
package that uses libtool and the system independent dlopen wrapper
@file{libltdl} to load modules. The library @file{libltdl} provides a
dlopen wrapper for various platforms (Linux, Solaris, HP/UX etc.)
dlopen wrapper for various platforms (POSIX)
including support for dlpreopened modules (@pxref{Dlpreopening}).
The tests matching @file{mdemo-*make.test}, @file{mdemo-*exec.test},

View File

@ -68,7 +68,7 @@ to use autoconf-mode, which is distributed with GNU Emacs 21, Autoconf itself,
and all recent releases of XEmacs.
@item
When building on some linux systems for multilib targets
When building on some GNU/Linux systems for multilib targets
@command{libtool} sometimes guesses the wrong paths that the linker
and dynamic linker search by default. If this occurs, you may override
libtool's guesses at @command{configure} time by setting the

View File

@ -1,15 +1,15 @@
This is GNU libltdl, a system independent dlopen wrapper for GNU libtool.
It supports the following dlopen interfaces:
* dlopen (Solaris, Linux and various BSD flavors)
* dlopen (POSIX)
* shl_load (HP-UX)
* LoadLibrary (Win16 and Win32)
* load_add_on (BeOS)
* GNU DLD (emulates dynamic linking for static libraries)
* dyld (darwin/Mac OS X)
* libtool's dlpreopen
--
Copyright (C) 1999, 2003 Free Software Foundation, Inc.
--
Copyright (C) 1999, 2003, 2011 Free Software Foundation, Inc.
Written by Thomas Tanner, 1999
This file is part of GNU Libtool.

View File

@ -2638,7 +2638,7 @@ linux*oldld* | linux*aout* | linux*coff*)
dynamic_linker=no
;;
# This must be Linux ELF.
# This must be glibc/ELF.
linux* | k*bsd*-gnu | kopensolaris*-gnu)
version_type=linux
need_lib_prefix=no
@ -3284,7 +3284,7 @@ irix5* | irix6* | nonstopux*)
lt_cv_deplibs_check_method=pass_all
;;
# This must be Linux ELF.
# This must be glibc/ELF.
linux* | k*bsd*-gnu | kopensolaris*-gnu)
lt_cv_deplibs_check_method=pass_all
;;