From: Alan Modra <amodra@gmail.com>
To: Martin Sebor <msebor@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: error: unknown type name ‘ctf_archive_t
Date: Tue, 2 Jun 2020 10:00:29 +0930 [thread overview]
Message-ID: <20200602003029.GB5204@bubble.grove.modra.org> (raw)
In-Reply-To: <d48cbdcb-3844-948d-f575-cf2c5dfdc341@gmail.com>
On Mon, Jun 01, 2020 at 05:36:54PM -0600, Martin Sebor via Binutils wrote:
> I've been getting the error below building binutils the last few
> weeks:
>
> In file included from /src/binutils-gdb/ld/ldlex.l:31,
> from /src/binutils-gdb/ld/ldlex-wrapper.c:26:
> /src/binutils-gdb/ld/ldlang.h:304:3: error: unknown type name
> ‘ctf_archive_t’
> 304 | ctf_archive_t *the_ctf;
> | ^~~~~~~~~~~~~
>
> A discussion of it I found in bug 25064 suggests it's caused by
> an outdated copy of the generated ld/ldlex.c file in the source
> tree. The build succeeds after I remove the file but I'd like
> to know what other files I should remove (or more broadly, what
> else I should do when re-building from a local copy) to make
> sure I build what everyone else does. (I assume removing the whole
> source tree and pulling a fresh copy is not the right way to do it.)
I'm curious. What output from "make" do you see if you touch ldlex.l
and then run make? ldlex.c ought to be regenerated via a .l.c rule,
even without --enable-maintainer-mode during configure.
I get the following.
make[4]: Entering directory '/home/alan/build/gas/all/ld'
/bin/bash /home/alan/src/binutils-gdb/ld/../ylwrap /home/alan/src/binutils-gdb/ld/ldlex.l lex.yy.c /home/alan/src/binutils-gdb/ld/ldlex.c -- flex
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-06-02 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 23:36 Martin Sebor
2020-06-02 0:30 ` Alan Modra [this message]
2020-06-02 16:53 ` Martin Sebor
2020-06-03 0:15 ` Alan Modra
2020-06-19 18:53 ` Nick Alcock
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=20200602003029.GB5204@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=msebor@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).