From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add configure.nat as a dependency of config.status
Date: Mon, 04 Jun 2018 14:36:00 -0000 [thread overview]
Message-ID: <19b3ed7b-172c-4763-8ebb-4faa26c224fa@redhat.com> (raw)
In-Reply-To: <1528122903-16122-1-git-send-email-simon.marchi@ericsson.com>
On 06/04/2018 03:35 PM, Simon Marchi wrote:
> After pulling Alan's change that added aarch64-sve-linux-ptrace.o to
> configure.nat, I got an undefined reference to aarch64_sve_get_vq when
> doing a "make clean && make". It turns out that re-running configure
> (./config.status --recheck) was needed to re-generate the Makefile with
> aarch64-sve-linux-ptrace.o included in the object list. Putting
> configure.nat in the dependencies of config.status would make sure that
> when we modify configure.nat, the configure script is re-ran. I think
> it also makes sense because configure.tgt and configure.host are also
> there.
>
> gdb/ChangeLog:
>
> * Makefile.in (config.status): Add configure.nat as a
> dependency.
Makes sense.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-06-04 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:35 Simon Marchi
2018-06-04 14:36 ` Pedro Alves [this message]
2018-06-04 14:41 ` Simon Marchi
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=19b3ed7b-172c-4763-8ebb-4faa26c224fa@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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).