public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-8068] libstdc++: Improve error reporting if PDF generation fails
Date: Thu,  8 Apr 2021 20:43:19 +0000 (GMT)	[thread overview]
Message-ID: <20210408204319.865F83857033@sourceware.org> (raw)

https://gcc.gnu.org/g:be8d5f99f50cf282c21632e60fe1d8857bb5a554

commit r11-8068-gbe8d5f99f50cf282c21632e60fe1d8857bb5a554
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Apr 8 18:37:59 2021 +0100

    libstdc++: Improve error reporting if PDF generation fails
    
    If pdflatex runs out of memory the build fails with no hint what's
    wrong. This adds another grep command to the makefile so that an
    out-of-memory error will result in more information being shown.
    
    As suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1841056
    using lualatex can be used as a workaround.
    
    libstdc++-v3/ChangeLog:
    
            * doc/Makefile.am (stamp-pdf-doxygen): Also grep for
            out-of-memory error in log file.
            * doc/Makefile.in: Regenerate.

Diff:
---
 libstdc++-v3/doc/Makefile.am | 1 +
 libstdc++-v3/doc/Makefile.in | 1 +
 2 files changed, 2 insertions(+)

diff --git a/libstdc++-v3/doc/Makefile.am b/libstdc++-v3/doc/Makefile.am
index 2e0eb187f91..cb9b68ffaea 100644
--- a/libstdc++-v3/doc/Makefile.am
+++ b/libstdc++-v3/doc/Makefile.am
@@ -267,6 +267,7 @@ stamp-pdf-doxygen: stamp-latex-doxygen ${doxygen_outdir}/pdf
 	else \
 	  echo "... error"; \
 	  grep -F 'LaTeX Error' ${doxygen_outdir}/latex/refman.log; \
+	  grep -F 'TeX capacity exceeded, sorry' ${doxygen_outdir}/latex/refman.log; \
 	  exit 12; \
 	fi
 	$(STAMP) stamp-pdf-doxygen
diff --git a/libstdc++-v3/doc/Makefile.in b/libstdc++-v3/doc/Makefile.in
index 7681908103a..956b641c1aa 100644
--- a/libstdc++-v3/doc/Makefile.in
+++ b/libstdc++-v3/doc/Makefile.in
@@ -958,6 +958,7 @@ stamp-pdf-doxygen: stamp-latex-doxygen ${doxygen_outdir}/pdf
 	else \
 	  echo "... error"; \
 	  grep -F 'LaTeX Error' ${doxygen_outdir}/latex/refman.log; \
+	  grep -F 'TeX capacity exceeded, sorry' ${doxygen_outdir}/latex/refman.log; \
 	  exit 12; \
 	fi
 	$(STAMP) stamp-pdf-doxygen


                 reply	other threads:[~2021-04-08 20:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210408204319.865F83857033@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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: link
Be 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).