Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Doug Evans <xdje42@gmail.com>, Phil Muldoon <pmuldoon@redhat.com>,
	gdb@sourceware.org
Subject: Re: Documentation build regressions
Date: Wed, 30 May 2018 20:56:00 -0000	[thread overview]
Message-ID: <20180530205613.GA3060354@host1.jankratochvil.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk>

On Wed, 30 May 2018 19:59:01 +0200, Maciej W. Rozycki wrote:
> commit 824cc835aa9a4d585d955db4ab2a5dd4c17cc22c
> Author: Phil Muldoon <pmuldoon@redhat.com>
> Date:   Thu Dec 7 16:47:33 2017 +0000
> 
>     Implement explicit locations for Python breakpoints.
> 
> for a failure in `python.texi':
> 
> .../gdb/doc/python.texi:4881: Unbalanced square braces in @def.
...
> ?

Fedora GDB builds always PDF and I have never seen such problem:
	https://kojipkgs.fedoraproject.org//packages/gdb/8.1/15.fc28/data/logs/x86_64/build.log


> This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)

This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdfetex)
texlive-pdftex-20170520-29.fc28.x86_64


Jan


  parent reply	other threads:[~2018-05-30 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 17:59 Maciej W. Rozycki
2018-05-30 20:12 ` Tom Tromey
2018-05-30 20:56 ` Jan Kratochvil [this message]
2018-05-31 17:23 ` Joseph Myers
2018-06-01 14:01   ` Jan Kratochvil
2018-06-01 19:38     ` Joseph Myers
2018-06-04 20:27       ` Maciej W. Rozycki
2018-06-05  9:49         ` variable displayed twice when using GDB/MI Xavier Roirand
2018-06-07 11:33           ` Pedro Alves
2018-05-31 17:51 ` Documentation build regressions Pedro Alves

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=20180530205613.GA3060354@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=macro@mips.com \
    --cc=pmuldoon@redhat.com \
    --cc=xdje42@gmail.com \
    /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