diff options
| author | Cristophe Jarry <christophe.jarry@ouvaton.org> | 2011-09-25 17:39:04 -0500 |
|---|---|---|
| committer | Peter O'Gorman <peter@pogma.com> | 2011-09-25 17:49:43 -0500 |
| commit | 920da81be698974faa50bd36a60248e2c18c4fd5 (patch) | |
| tree | c9965033163e70aec4f45c4548319252de7ddf5e /TODO | |
| parent | dc28c2bfbcb4879bc04a73186d72ec0e7ef2ad4c (diff) | |
| download | libtool-920da81be698974faa50bd36a60248e2c18c4fd5.tar.gz | |
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.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 20 |
1 files changed, 10 insertions, 10 deletions
@@ -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 |