From: Pedro Alves <palves@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: spurious change regenerating gdb/config.in?
Date: Wed, 19 Oct 2016 00:10:00 -0000 [thread overview]
Message-ID: <b55b3020-252e-b73e-1cf7-e14e23758885@redhat.com> (raw)
If I run autoheader on the gdb/ dir, I see this spurious
change come out:
diff --git c/gdb/config.in w/gdb/config.in
index c82a5b4..3790d10 100644
--- c/gdb/config.in
+++ w/gdb/config.in
@@ -453,12 +453,12 @@
/* Define to 1 if your system has struct lwp. */
#undef HAVE_STRUCT_LWP
-/* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_tdname'. */
-#undef HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME
-
/* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_syscall_code'. */
#undef HAVE_STRUCT_PTRACE_LWPINFO_PL_SYSCALL_CODE
+/* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_tdname'. */
+#undef HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME
+
/* Define to 1 if your system has struct reg in <machine/reg.h>. */
#undef HAVE_STRUCT_REG
This is with pristine FSF autoconf 2.64. I suspect this is
just because the config.in in master was generated by some
other autoconf version. To confirm, does anyone else
see this?
Thanks,
Pedro Alves
next reply other threads:[~2016-10-19 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 0:10 Pedro Alves [this message]
2016-10-19 3:23 ` John Baldwin
2016-10-19 13:09 ` Pedro Alves
2016-10-19 15:55 ` Maciej W. Rozycki
2016-10-19 8:01 ` Yao Qi
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=b55b3020-252e-b73e-1cf7-e14e23758885@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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