summaryrefslogtreecommitdiff
path: root/patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2007-02-24 11:00:05 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2007-02-24 11:00:05 (GMT)
commit1906cf93f86d8d66f45f90380a8d3da25c087ee5 (patch)
tree90916c99abe1f1ec26709ee420e6c349eda4670a /patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch
parent2609573aede4ce198b3462976725b25eb1637d2e (diff)
Add the full crosstool-NG sources to the new repository of its own.
You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
Diffstat (limited to 'patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch')
-rw-r--r--patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch26
1 files changed, 26 insertions, 0 deletions
diff --git a/patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch b/patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch
new file mode 100644
index 0000000..1ed6480
--- /dev/null
+++ b/patches/glibc/2.1.3/glibc-manual-stdin.texi-1.127.patch
@@ -0,0 +1,26 @@
+Fixes
+./stdio.texi:2491: First argument to cross-reference may not be empty.
+./stdio.texi:2492: First argument to cross-reference may not be empty.
+makeinfo: Removing output file `/home/dank/crosstool-0.25/build/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.1.3/glibc-2.1.3/manual/libc.info' due to errors; use --force to preserve.
+make[2]: *** [libc.info] Error 2
+
+Patch from glib-2.2; Line numbers adjusted.
+
+===================================================================
+RCS file: /cvs/glibc/libc/manual/stdio.texi,v
+retrieving revision 1.126
+retrieving revision 1.127
+diff -u -r1.126 -r1.127
+--- libc/manual/stdio.texi 2001/06/06 07:11:00
++++ libc/manual/stdio.texi 2001/07/31 18:57:00
+@@ -2487,8 +2487,8 @@
+ If you are trying to read input that doesn't match a single, fixed
+ pattern, you may be better off using a tool such as Flex to generate a
+ lexical scanner, or Bison to generate a parser, rather than using
+-@code{scanf}. For more information about these tools, see @ref{, , ,
+-flex.info, Flex: The Lexical Scanner Generator}, and @ref{, , ,
++@code{scanf}. For more information about these tools, see @ref{Top, , ,
++flex.info, Flex: The Lexical Scanner Generator}, and @ref{Top, , ,
+ bison.info, The Bison Reference Manual}.
+
+ @node Input Conversion Syntax