* PORTING: Porting instructions are in the libtool manual already

diff --git a/ChangeLog b/ChangeLog
index 0379f951ca842f9663b2ef0d2d8d137c23d43f44..dbc866ad6e96d191e94e8fb856944867ef6c5e58 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 1998-11-12  Alexandre Oliva  <oliva@dcc.unicamp.br>
 
+       * PORTING: Porting instructions are in the libtool manual already
+
        * NEWS: Mention -export-symbols and new dlpreopen
 
 1998-11-11  Alexandre Oliva  <oliva@dcc.unicamp.br>

diff --git a/PORTING b/PORTING
index bdd089d41653677997577377ee6d2ee09b7efeed..06b35416b2ab20e8de977c6230bcf1a8ccb83d96 100644 (file)
--- a/PORTING
+++ b/PORTING
@@ -1,18 +1,11 @@
-This file is intended to contain hints on how to port libtool to new
-platforms.  It is currently waiting for your contributions :-)
+In order to port libtool to a new platform, start by reading the node
+`New ports' in the info document (i.e., the libtool manual).  Some
+additional information, that has not been converted to the .texi
+format yet, is available in this file.
 
-
-General Instructions
---------------------
-
-In order to port libtool to a new platform, start by searching for
-PORTME in ltconfig.in.  Look for the string `Libtool was configured as
-follows'; that's the beginning of the platform-dependent configuration
-portion that will be inserted in the libtool script.  Most of the
-documentation about the variables you may have to set in your port is
-there.  Feel free (and compelled :-) to submit patches for this
-(PORTING) file, so that it complements the documentation within the
-script.
+If you find that any porting documentation is missing, please
+complain! :-) Complaints with patches and improvements to the
+documentation, or to libtool itself, are more than welcome.  :-) :-)
 
 
 Inter-library Dependencies