From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5A4453858D32; Sun, 15 Jan 2023 17:35:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5A4453858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673804159; bh=g9JYaCgLhBkZw7dv92IzOiSLPzgG7t2VdmHmpMqYq4Q=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eoEbEwsGKiN5uO2EjorUIdD+C5i7scWYww4LL83N5jMJwviyPwgQwq1/l22PtMMvV rnsKZo98S3zb2tB5IBbNT4o2vPiVQVI0WBHCO7dqnGpYqkVffMp8s6DbV3B9NMEGtN 5Jzn4/47P5h/WqMUsrUwIeum/q9FCCiingzXCNkY= From: "phi.debian at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug build/30003] GDB build broken since 2ff63a29b0b Date: Sun, 15 Jan 2023 17:35:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: phi.debian at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30003 --- Comment #2 from Phi --- In my latest git pull it looks like the reference bfd/doc/bfd.texi:: ... @include init.texi ... is not there anymore, so may be this is cured, yet I got some more build er= ror, this time it was failing in gprofng build dir, I got to remove this with=20 config --enable-gprofng=3Dno So may be my previous posting about init.text was an false alarm. -- --=20 You are receiving this mail because: You are on the CC list for the bug.=