public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/32859] New: [4.3 Regression] "make info" fails in libiberty Date: Mon, 23 Jul 2007 06:04:00 -0000 [thread overview] Message-ID: <bug-32859-10391@http.gcc.gnu.org/bugzilla/> (raw) "make info" currently fails on trunk: Doing info in i686-pc-linux-gnu/libiberty make[2]: Entering directory `/home/ig25/gcc-bin/trunk/i686-pc-linux-gnu/libiberty' perl ../../../../gcc/trunk/libiberty/gather-docs ../../../../gcc/trunk/libiberty ../../../../gcc/trunk/libiberty/functions.texi alloca.c argv.c asprintf.c atexit.c basename.c bcmp.c bcopy.c bsearch.c bzero.c calloc.c choose-temp.c clock.c concat.c cp-demangle.c cp-demint.c cplus-dem.c dyn-string.c fdmatch.c ffs.c fibheap.c filename_cmp.c floatformat.c fnmatch.c fopen_unlocked.c getcwd.c getopt.c getopt1.c getpagesize.c getpwd.c getruntime.c gettimeofday.c hashtab.c hex.c index.c insque.c lbasename.c lrealpath.c make-relative-prefix.c make-temp-file.c md5.c memchr.c memcmp.c memcpy.c memmove.c mempcpy.c memset.c mkstemps.c objalloc.c obstack.c partition.c pexecute.c pex-common.c pex-djgpp.c pex-msdos.c pex-one.c pex-unix.c pex-win32.c physmem.c putenv.c random.c regex.c rename.c rindex.c safe-ctype.c setenv.c sigsetmask.c snprintf.c sort.c spaces.c splay-tree.c stpcpy.c stpncpy.c strcasecmp.c strchr.c strdup.c strerror.c strncasecmp.c strncmp.c strrchr.c strsignal.c strstr.c strtod.c strtol.c strtoul.c strndup.c strverscmp.c ternary.c tmpnam.c unlink-if-ordinary.c vasprintf.c vfork.c vfprintf.c vprintf.c vsnprintf.c vsprintf.c waitpid.c xatexit.c xexit.c xmalloc.c xmemdup.c xstrdup.c xstrerror.c xstrndup.c fnmatch.txh pexecute.txh echo stamp > stamp-functions makeinfo --split-size=5000000 --split-size=5000000 -I../../../../gcc/trunk/libiberty ../../../../gcc/trunk/libiberty/libiberty.texi ../../../../gcc/trunk/libiberty//functions.texi:1477: Unmatched }. makeinfo: Removing output file `/home/ig25/gcc-bin/trunk/i686-pc-linux-gnu/libiberty/libiberty.info' due to errors; use --force to preserve. make[2]: *** [libiberty.info] Error 1 make[2]: Leaving directory `/home/ig25/gcc-bin/trunk/i686-pc-linux-gnu/libiberty' make[1]: *** [info-target-libiberty] Error 1 make[1]: Leaving directory `/home/ig25/gcc-bin/trunk' make: *** [do-info] Error 2 gcc was configured with ../../gcc/trunk/configure --enable-languages=c,fortran --prefix=$HOME --enable-maintainer-mode --disable-multilib (Shouldn't there be a libiberty component?) This is a bit of a nuisance because I can't test other documentation patches. I have a dded dj to the CC because he was last to touch that directory. I've added dj to the CC list because he was the last one to touch that directory. After the "make info", I get $ svn diff Index: functions.texi =================================================================== --- functions.texi (revision 126829) +++ functions.texi (working copy) @@ -214,7 +214,7 @@ symbolic name or message. @end deftypefn -@c argv.c:293 +@c argv.c:348 @deftypefn Extension void expandargv (int *@var{argcp}, char ***@var{argvp}) The @var{argcp} and @code{argvp} arguments are pointers to the usual @@ -268,15 +268,16 @@ value 1). If @var{valu} is zero, zero i @end deftypefn -@c filename_cmp.c:28 +@c filename_cmp.c:32 @deftypefn Extension int filename_cmp (const char *@var{s1}, const char *@var{s2}) -Return zero if the two paths @var{s1} and @var{s2} are equivalent. -If not equivalent, the returned value is similar to what strcmp would -return. In other words, it returns a negative value if @var{s1} is less -than @var{s2}, or a positive value if @var{s2} is greater than @var{s2}. +Return zero if the two file names @var{s1} and @var{s2} are equivalent. +If not equivalent, the returned value is similar to what @code{strcmp} +would return. In other words, it returns a negative value if @var{s1} +is less than @var{s2}, or a positive value if @var{s2} is greater than +@var{s2}. -This function does not normalize path names. As a result, this function +This function does not normalize file names. As a result, this function will treat filenames that are spelled differently as different even in the case when the two filenames point to the same underlying file. However, it does handle the fact that on DOS-like file systems, forward @@ -1471,6 +1472,15 @@ does the return value. The third argume @end deftypefn +@c argv.c:293 +@deftypefn Extension int writeargv (const char **@var{argv}, FILE *@{file}) + +Write each member of ARGV, handling all necessary quoting, to the file +named by FILE, separated by whitespace. Return 0 on success, non-zero +if an error occurred while writing to FILE. + +@end deftypefn + @c xatexit.c:11 @deftypefun int xatexit (void (*@var{fn}) (void)) -- Summary: [4.3 Regression] "make info" fails in libiberty Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tkoenig at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32859
next reply other threads:[~2007-07-23 6:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-23 6:04 tkoenig at gcc dot gnu dot org [this message] 2007-07-23 6:05 ` [Bug other/32859] " tkoenig at gcc dot gnu dot org 2007-07-23 9:23 ` pinskia at gcc dot gnu dot org 2007-07-23 17:17 ` tkoenig at gcc dot gnu dot org 2007-07-23 17:29 ` dj at redhat dot com 2007-07-23 19:47 ` tkoenig at gcc dot gnu dot org 2007-07-24 0:32 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-32859-10391@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).