public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "phi.debian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30003] New: GDB build broken since 2ff63a29b0b
Date: Sun, 15 Jan 2023 11:20:52 +0000	[thread overview]
Message-ID: <bug-30003-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30003

            Bug ID: 30003
           Summary: GDB build broken since 2ff63a29b0b
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: phi.debian at gmail dot com
  Target Milestone: ---

Hi All,

GDB build out of the box fail for me since 2ff63a29b0b, doing the build on
ubuntu LTS 22.04, latest compilers (gcc)... (compiler not a factor though).

What seems broken is that since 2ff63a29b0b bfd/ texinfo 'init' component has
removed the from the build, probably because it was empty for so long, yet a
dangling reference to init.texi remains in the file bfd/doc/bfd.texi

bfd/doc/bfd.texi::
...
@include  init.texi
...

I patched this as
@comment phi.debian@gmail.com init was removed at commit 2ff63a29b0b
@comment @include  init.texi


And build run like a champ.

I can't regsiter to the mailing lists, made some subscribe, but got no
feedbacks, so I can't cut a patch.

Cheers.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-01-15 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 11:20 phi.debian at gmail dot com [this message]
2023-01-15 17:10 ` [Bug build/30003] " tromey at sourceware dot org
2023-01-15 17:35 ` phi.debian at gmail dot com
2023-01-15 20:51 ` tromey at sourceware dot org
2023-01-15 22:38 ` tromey at sourceware dot org
2023-01-17  6:11 ` phi.debian at gmail 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-30003-4717@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: 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).