From: Jim Wilson <jimw@sifive.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "Jose E. Marchesi" <jemarch@gnu.org>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/8] bpf: new GCC port
Date: Tue, 20 Aug 2019 07:42:00 -0000 [thread overview]
Message-ID: <CAFyWVaZCse3TpNYGGhOo2rV_sEYuJdy73G3D1-vraz+5Dz5kEA@mail.gmail.com> (raw)
In-Reply-To: <20190819120100.GD31406@gate.crashing.org>
On Mon, Aug 19, 2019 at 5:01 AM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> On Thu, Aug 15, 2019 at 12:22:46AM +0200, Jose E. Marchesi wrote:
> > --- a/configure
> > +++ b/configure
> > @@ -754,6 +754,7 @@ infodir
> > docdir
> > oldincludedir
> > includedir
> > +runstatedir
> > localstatedir
> > sharedstatedir
> > sysconfdir
>
> (etc.)
>
> You seem to have generated this with the wrong version of autoxxxx, or
> the wrong options, or the previous version was. Please check? Or, what
> else caused this change?
My experience is that this is a commonly added patch to the system
autoconf binary, e.g. /usr/bin/autoconf. So you need to build your
own autoconf from the FSF sources to get an exact match. Or maybe use
a different linux distro that doesn't modify autoconf. But personally
I just build my own autoconf binaries to avoid this problem.
Jim
next prev parent reply other threads:[~2019-08-19 23:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 21:37 [PATCH 0/8] eBPF support for GCC Jose E. Marchesi
2019-08-14 21:37 ` [PATCH 5/8] bpf: make target-supports.exp aware of eBPF Jose E. Marchesi
2019-08-14 21:37 ` [PATCH 7/8] bpf: manual updates for eBPF Jose E. Marchesi
2019-08-14 21:37 ` [PATCH 1/8] Update config.sub and config.guess Jose E. Marchesi
2019-08-14 21:37 ` [PATCH 8/8] bpf: add myself as the maintainer for the eBPF port Jose E. Marchesi
2019-08-14 21:37 ` [PATCH 3/8] bpf: new libgcc port Jose E. Marchesi
2019-08-14 21:59 ` [PATCH 4/8] bpf: gcc.target eBPF testsuite Jose E. Marchesi
2019-08-14 22:06 ` [PATCH 6/8] bpf: adjust GCC testsuite to eBPF limitations Jose E. Marchesi
2019-08-14 22:15 ` [PATCH 0/8] eBPF support for GCC David Malcolm
2019-08-14 23:06 ` Jose E. Marchesi
2019-08-14 22:28 ` [PATCH 2/8] bpf: new GCC port Jose E. Marchesi
2019-08-19 12:49 ` Segher Boessenkool
2019-08-20 7:42 ` Jim Wilson [this message]
2019-08-20 9:51 ` Jose E. Marchesi
2019-08-20 21:22 ` Hans-Peter Nilsson
2019-08-21 7:57 ` Segher Boessenkool
2019-08-22 11:01 ` Hans-Peter Nilsson
2019-08-22 11:44 ` Segher Boessenkool
2019-08-15 8:14 ` [PATCH 0/8] eBPF support for GCC Richard Sandiford
2019-08-15 23:53 ` Jose E. Marchesi
2019-08-15 18:07 ` [PATCH 2/8] bpf: new GCC port Jose E. Marchesi
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=CAFyWVaZCse3TpNYGGhOo2rV_sEYuJdy73G3D1-vraz+5Dz5kEA@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jemarch@gnu.org \
--cc=jose.marchesi@oracle.com \
--cc=segher@kernel.crashing.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).