public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pcarroll at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/25716] Generated doxygen docs cause problems for Windows due to case-insensitive filesystem Date: Fri, 19 Jun 2020 14:15:29 +0000 [thread overview] Message-ID: <bug-25716-4717-9CldKdRqn9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25716-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25716 Paul Carroll <pcarroll at codesourcery dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pcarroll at codesourcery dot com --- Comment #1 from Paul Carroll <pcarroll at codesourcery dot com> --- We ran into this same problem. I've identified the problem as being a new @anchor in the gdb.texinfo file. The solution is to remove the @anchor(frame apply) and then modify the 2 @xref's that refer to that anchor. When I do that, the 'frame-apply.html' file is not created (using texi2html). I will attach my proposed patch, which should solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-19 14:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 18:05 [Bug build/25716] New: " freddie_chopin at op dot pl 2020-06-19 14:15 ` pcarroll at codesourcery dot com [this message] 2020-06-19 14:18 ` [Bug build/25716] " pcarroll at codesourcery dot com 2020-06-19 15:03 ` simark at simark dot ca 2020-06-22 18:04 ` pcarroll at codesourcery dot com 2020-06-22 18:05 ` simark at simark dot ca 2020-07-08 14:22 ` pcarroll at codesourcery dot com 2020-07-08 19:11 ` pcarroll at codesourcery dot com 2020-07-13 19:36 ` cvs-commit at gcc dot gnu.org 2020-07-15 21:14 ` pcarroll at codesourcery dot com 2020-07-18 19:24 ` brobecker at gnat dot com 2020-07-18 19:24 ` brobecker at gnat dot com
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-25716-4717-9CldKdRqn9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).