[pushed] libiberty: Remove a reference to the Glibc manual

Message ID 20230331185041.8F5FC33E63@hamza.pair.com
State Committed
Commit 83d2b1ccd17d394d546a38562815ef83daa05e85
Headers
Series [pushed] libiberty: Remove a reference to the Glibc manual |

Commit Message

Gerald Pfeifer March 31, 2023, 6:50 p.m. UTC
  With this we have a sole 404 on all of gcc.gnu.org (at least with
documentation from trunk included). :-)

Gerald


---

longjmp is not specific to Glibc, and GCC supports lots of systems
that do not use Glibc. Plus this link has been broken in the web
version for ages without a good way to fix.

libiberty/ChangeLog:

	* obstacks.texi (Preparing for Obstacks): Remove a (broken)
	reference to the Glibc manual.
---
 libiberty/obstacks.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
  

Patch

diff --git a/libiberty/obstacks.texi b/libiberty/obstacks.texi
index b2d2403210b..37d26c90f1b 100644
--- a/libiberty/obstacks.texi
+++ b/libiberty/obstacks.texi
@@ -172,8 +172,8 @@  The value of this variable is a pointer to a function that
 @code{obstack} uses when @code{obstack_chunk_alloc} fails to allocate
 memory.  The default action is to print a message and abort.
 You should supply a function that either calls @code{exit}
-(@pxref{Program Termination, , , libc, The GNU C Library Reference Manual}) or @code{longjmp} (@pxref{Non-Local
-Exits, , , libc, The GNU C Library Reference Manual}) and doesn't return.
+(@pxref{Program Termination, , , libc, The GNU C Library Reference Manual}) 
+or @code{longjmp} and doesn't return.
 
 @smallexample
 void my_obstack_alloc_failed (void)