mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-01-18 10:45:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix documentation problems reported by Russ Boylan in

Browse Source 
<http://lists.gnu.org/archive/html/bug-autoconf/2004-11/msg00056.html>,
along with some nearby cruft.
* doc/autoconf.texi (Libtool): Libtool can be used without
Automake (not without Autoconf).
(Introduction): Mention lists.gnu.org.
* BUGS: Don't mention bugs.gnu.org.
Remove mention of ancient libtool compatibility problem.
* NEWS: Mention that bugs.gnu.org is kaput.
* README: Likewise.  Mention where mailing list archives can be found.
This commit is contained in:
Paul Eggert 2004-11-29 04:29:08 +00:00
parent a547bb54a8
commit f72fc4eb29
5 changed files with 25 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
BUGS
View File

@ -26,24 +26,10 @@ file before using Autoconf, and especially CVS versions of Autoconf.
Autoconf must not be used in production if there are ``Serious'' bugs,
and use with caution an Autoconf with ``Important bugs''.
Many other bugs are registered on the GNATS server:
http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf
Please, don't register bugs listed below: we already know we have to
address them.
* Status
/*--------------------------.
| Sane for full scale use. |
`--------------------------*/
* Interoperability bugs
** libtool 1.4.2, configure.ac, and AC_CONFIG_AUX_DIR
configure.ac files that use AC_CONFIG_AUX_DIR do not work with libtool
1.4.2. To work around the problem, you can rename configure.ac to
configure.in. Or you can apply Roger Leigh's patch to libtool; see
<http://mail.gnu.org/pipermail/libtool-patches/2002-January/001659.html>.
* No known serious or important bugs.

13
ChangeLog
View File

@ -1,3 +1,16 @@
2004-11-28 Paul Eggert <eggert@cs.ucla.edu>
Fix documentation problems reported by Russ Boylan in
<http://lists.gnu.org/archive/html/bug-autoconf/2004-11/msg00056.html>,
along with some nearby cruft.
* doc/autoconf.texi (Libtool): Libtool can be used without
Automake (not without Autoconf).
(Introduction): Mention lists.gnu.org.
* BUGS: Don't mention bugs.gnu.org.
Remove mention of ancient libtool compatibility problem.
* NEWS: Mention that bugs.gnu.org is kaput.
* README: Likewise. Mention where mailing list archives can be found.
2004-11-26 Paul Eggert <eggert@cs.ucla.edu>
* doc/autoconf.texi (Pretty Help Strings): Go back to

3
NEWS
View File

@ -348,8 +348,9 @@ Release tips:
More of them.
- GNATS
The GNATS base has moved to
The GNATS base moved to
http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf
(It is no longer available, though.)
** Misc.

7
README
View File

@ -34,11 +34,12 @@ to maintain many similar sets of installation instructions.
Be sure to read BUGS (especially if this version is not an official
release) and INSTALL.
Mail suggestions to autoconf@gnu.org, report bugs on
http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf or to
Mail suggestions to autoconf@gnu.org, report bugs to
bug-autoconf@gnu.org, and submit patches to autoconf-patches@gnu.org.
Always include the Autoconf version number, which you can get by
running `autoconf --version'.
running `autoconf --version'. Archives of bug-autoconf@gnu.org can be
found in <http://lists.gnu.org/archive/html/bug-autoconf/>, and
similarly for the other mailing lists.
-----

6
doc/autoconf.texi
View File

@ -667,6 +667,10 @@ Summary} for details. Patches relative to the
current @acronym{CVS} version can be sent for review to the
@email{autoconf-patches@@gnu.org, Autoconf Patches mailing list}.
Archives of @email{bug-autoconf@@gnu.org} can be
found in @uref{http://lists.gnu.org/archive/html/bug-autoconf/}, and
similarly for the other mailing lists.
Because of its mission, Autoconf includes only a set of often-used
macros that have already demonstrated their usefulness. Nevertheless,
if you wish to share your macros, or find existing ones, see the
@ -761,7 +765,7 @@ shared libraries, linking reliably with shared libraries before they are
installed by the superuser, and supplying a consistent versioning system
(so that different versions of a library can be installed or upgraded
without breaking binary compatibility). Although Libtool, like
Autoconf, can be used on its own, it is most simply utilized in
Autoconf, can be used without Automake, it is most simply utilized in
conjunction with Automake---there, Libtool is used automatically
whenever shared libraries are needed, and you need not know its syntax.